Your first week with GHL Command

What you'll get

• A running order for your first week, so you are not picking guides at random.
• The two questions worth asking about any tool you pay for, answered by the tool itself: is all of this still working, and am I using all of it?
• The habit that turns this from a tool you bought into one you keep using.

Say this

Run a checkup on my GHL Command.

Open the user guide.

What version of GHL Command am I running?

The five, in order

1. Restart Claude before anything else. GHL Command updates often, and the newest features do not exist in the copy you are running until you restart. Quit Claude completely, which is Cmd+Q on a Mac or closing it from the system tray on Windows. Closing the window alone leaves the old version running. Open it again and it pulls the update by itself. Nothing to download, nothing to reinstall. Then ask "what version of GHL Command am I running?" to confirm.

2. Run a checkup on your busiest client account. One sentence, three answers: whether your connection is healthy, which capabilities still read correctly, and what your account contains that you are not using yet. Everything it does is a read, so it is safe on a live client account. Act on the top item it flags and only the top item. See the "Give your setup a checkup" guide for what each verdict means.

3. Audit your workflows on every account you manage. This is the one that finds money already leaking. The usual find is a workflow built before somebody deleted a pipeline stage or a custom field. It looks perfectly healthy inside GoHighLevel, which is exactly the problem, because contacts hit it and stop. See "Audit your workflows".

4. Open the guide library and read the three cards closest to your own week. Not the first three in the list, the three nearest to what you did yesterday. Every guide is a job rather than a feature, and they all share the same five parts, so you learn the shape once and then read fast.

5. Build one nurture sequence and its exit workflow end to end. Pick a single client and do the full loop once, so you have seen a build go in and come back out cleanly before you do it under time pressure. See "Build a nurture sequence" and "Add an exit workflow".

Good to know

• Steps 2 and 3 only read your account. Nothing is written and nothing is changed, so there is no reason to practise on a test account first.
• A clean read that finds nothing means the capability works and you simply do not own any of those yet. It does not mean something is broken. The checkup keeps those two separate on purpose, because from the outside they look identical and mean opposite things.
• The library ships inside your install. It works with no internet connection, and it updates with the product, so it is always describing the version you actually have.
• Search the library by what you want, not by what it is called. Typing "nothing happens" lands you on the workflow audit. Typing "spreadsheet" gets you the contact export.
• If a guide card says it is coming in an update, that is honest rather than broken. It is not written yet, and your install picks it up automatically when it is.

The one habit

Run the checkup monthly, and any time GoHighLevel feels off after one of their updates. It takes a minute, and it is the difference between finding out from the tool and finding out from a client. If anything ever comes back BROKEN, send the whole report to support@ghlcommand.com. That report is exactly what is needed to fix it.

Where people go wrong

Related guides

• Install GHL Command
• Give your setup a checkup
• Audit your workflows
• Switch between client accounts