The Fastest Way To Get Unstuck

Everybody gets stuck. It is not a sign you picked the wrong software or that you are bad at this. Software has a shape, and until you know the shape you will occasionally look for something in the wrong room.

The expensive version is not being stuck. It is being stuck quietly. Somebody hits a wall on a Tuesday, decides they will work it out later, and later never arrives, so the feature sits unused for six months and the account gets cancelled for not doing a thing it does.

Two doors, and you want the first one most of the time

There are exactly two ways to get help, and the useful skill is knowing which one you are looking at.

The Help Center answers "how does this work". It is faster than a support ticket by roughly the time it takes somebody to read your email, which is usually the difference between two minutes and two hours.

A support ticket answers "this is not doing what the guide says it does". That is a genuinely different question and it needs a person.

Most people skip straight to the ticket because that is the habit other software has taught them, where the documentation was written once in 2021 and never touched again. Try the guide first here. It will surprise you.

What is in the Help Center

Click Help in the left sidebar. Every guide on the platform is there, grouped by what you are trying to do rather than by which menu the feature lives under, because you almost never know the menu when you are looking.

• Guides with a Watch pill have a video walkthrough at the top as well as written steps. Watch it if you learn better that way, skim the steps if you do not.
• Getting started shows the welcome video and your setup checklist with live progress, and it stays available even after the dashboard panel has hidden itself.
• None of it is behind a plan. Every guide is readable on every account, including during a trial.

The shortcut most people never notice

Every feature screen has a Guide button in its header. Not a generic help link. The guide for that exact screen.

So if you are standing on the Cleaning tab wondering how cleaner reminders get sent, you do not go to Help and hunt. You click Guide in the corner of the screen you are already on and land in the right article. It is the single fastest route from confusion to answer in the whole product, and it is the one people find last.

Raising a ticket that gets answered on the first reply

When a guide genuinely does not cover it, Contact support raises a ticket that goes straight to the team.

1. Click Help in the sidebar, then Contact support.
2. Your name, business and email are filled in from your profile already, so you only write the question.
3. Give it a subject and describe what you were doing and what happened instead.
4. Click Send. The ticket appears under Your tickets below the form.

Here is the part that decides whether you get an answer or a question back. Say what you expected as well as what happened.

"Invoices are broken" produces a reply asking which invoice, what you clicked and what you saw. That is a day gone. "I clicked Send on invoice 1042 and the page reloaded empty, no email arrived, the invoice still says draft" gets fixed in one reply, because everything needed to reproduce it is in the first message.

The page address helps enormously too. It tells us exactly which screen you were on, which is often half the diagnosis on its own.

What happens after you send it

Replies land in two places, and you can carry the conversation on from either.

• On the ticket thread under Your tickets, inside ClientBranch.
• By email, to the address on your profile.

Tickets show as Open while they are with us and unanswered, and Answered when there is a reply waiting on the thread. Reopening one is just adding another message to the same thread, so keep a running issue in one place rather than raising a fresh ticket each time. The history is what makes the second answer faster than the first.

The one setting worth checking today

Go to Settings, then My Account and look at the email address on your profile.

Ticket replies go there. If it is an address you set up years ago and never open, or one that forwards somewhere that quietly stopped forwarding, then every answer we send will look to you like an answer that never came. This is the single most common reason support "did not reply", and it takes ten seconds to rule out.

The three questions worth asking yourself first

Before you write anything, thirty seconds of triage saves a round trip.

• Am I on the right screen? A surprising share of "this feature is missing" turns out to be a sub tab one click away. The Guide button on the screen tells you what should be there.
• Is this a plan thing? Some features belong to a particular plan. If a screen exists but nothing is on it, check Settings, then Billing before assuming it is broken.
• Did it work before? "It used to do this and now it does not" is the single most useful sentence you can put in a ticket, because it narrows the search enormously.

When the answer is "that does not exist yet"

Sometimes the honest answer to a ticket is that the thing you want is not built. That is not a fobbing off, and it is worth sending the ticket anyway.

Feature requests that arrive through support are how the roadmap gets ordered. A request from one person is an opinion. The same request from six people in a month is a build. You have no way of knowing which one you are, so send it, describe what you were trying to do rather than the feature you imagine would fix it, and let the pattern do its work.

Describing the goal rather than the solution matters more than it sounds. "I want a checkbox here" gets one checkbox. "I need to know which of my clients have not booked since spring" sometimes turns out to be something the product already does through a smart list, and you get an answer today instead of a place in a queue.

Ask earlier than feels reasonable

There is a instinct, especially among people who run their own business and are used to solving everything themselves, to exhaust every option before asking. It is an admirable instinct and it costs a lot of time.

The honest rule: if you have been going in circles for fifteen minutes on something that should be simple, that is the moment. Not after an hour. The answer is usually one sentence, and the fifteen minutes was the whole price of not asking.

The video at the top runs through the Help Center, opening a guide, raising a ticket and reading the reply. The Getting help guide covers the same ground in writing.