Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Owned by Jerry

Your #1 Go-To Resource for Starting, Building, & Growing Your Contour Business!

The AI operator's room for GoHighLevel agencies.

180 contributions to GHL Command
Find the Reviews Nobody Answered
Command note: A review with no reply is a conversation you walked away from in public. Most accounts ask for reviews on autopilot and then never look at what came back. The request is automated. The answer usually is not, so it waits on whoever remembers. Here is the prompt we run to see the gap: "List every review this account received in the last 90 days. Group them by star rating. For each one show the source, the date, the first line of the review and whether it has a reply. Put unanswered reviews under 4 stars at the top, oldest first. Read only. Do not reply to anything." What it surfaces: • Low-star reviews sitting unanswered for weeks • Five-star reviews nobody thanked • One platform getting replies while another is ignored • The same complaint showing up more than once Run it today: 1) Pick one account and run the prompt as written 2) Reply to the oldest unanswered low-star review first, yourself 3) Thank the five-star reviews in one sitting 4) Write down any complaint that appears twice and fix the cause 5) Decide who owns review replies and how fast they answer 6) Put the prompt on the calendar for the same day every week The replies stay human. The prompt only makes sure nothing sits unseen. People read the reply before they read the rating.
Find the Reviews Nobody Answered
Click Every Link Before It Goes Out
Command note: A link that works for you is not a link that works for the lead. The classic miss: the message reads well, the workflow fires on time, and the button goes to a preview URL, an old page, or a login screen. You were signed in when you tested it, so it opened fine. Nobody else was. Where links quietly break: • Preview or editor URLs pasted in place of the published one • Pages renamed, moved, or unpublished after the message was written • Booking links for a calendar that has since been turned off • Links copied from one client's template into another's • Trigger links still pointed at last quarter's offer Do this before any message with a link goes live: 1) Send it to yourself. The real message, not the preview pane 2) Open it on a phone, in a private window, signed out of everything 3) Click every link, including the footer and the unsubscribe 4) Finish what the link asks for. Book the slot, submit the form 5) Confirm the record lands in the account where you expect it 6) Repeat whenever a page, calendar, or domain changes The message is not the deliverable. The click is.
0
0
Click Every Link Before It Goes Out
Command OS opens November 19. Your $97 stays $97.
I told you I would give you a 7-day notice before Command OS opened. This is it. https://ghlcommand.com/upgrade Your $97 membership is about to become a $497 product. Your price doesn't move. Command OS opens Thursday, November 19. If you're paying $97 for GHL Command when it opens, you move to Command OS at $97 for as long as you stay subscribed. Same key, same login. Nothing to buy. New members pay $497 a month. The first 20 get Founders pricing at $297. What changes in your week: Today, finding out who needs you means opening one sub-account after another. On the 19th you open one screen with every client account you register, and a morning brief tells you where you're needed before you open GoHighLevel. Today, a new client build is your night shift, and your VA waits on you because checking their work takes as long as doing it. On the 19th the build is thirteen numbered steps a team member can run under their own login (up to 9 of them). It shows what it will create before it writes anything. A check reads the account back. You sign off a build that has already been checked. Today, a prospect has heard "we do AI and automation" from every agency that called this month. On the 19th you can open with a report on their own website under your agency's name, a demo chat bot they can text, and the Assessment, which turns their answers into findings with a monthly figure. Today, a workflow can send a booking invite to a lead who booked yesterday. On the 19th a brain on each client drafts replies for a person to approve and holds the message that doesn't fit the lead's record. Sending is off at launch: it drafts and holds, a person approves and sends. You also get a live group call each month. The first one is Thursday, December 10, 2026, at 8:00 AM Central (7:00 AM Arizona). You'll find the link in your Members Hub. The straight part: I have no customer results from Command OS to quote yet, so I'm not quoting any. What I can show you is the product. I put it on one page: real screens from the cockpit with example clients, a 1:49 narrated walkthrough (the voice is AI, the screens are real), a calculator for your own numbers, and a list of what's proven and what isn't yet.
1
0
Command OS opens November 19. Your $97 stays $97.
Read Every Message on a Phone First
Command note: Nobody reads your automation in the builder. They read it on a lock screen. Every message looks fine inside GHL. Wide editor, merge fields labeled, the whole context in your head. Your lead sees two lines of preview on a small screen, stacked between other notifications. What breaks on a phone that looked fine in the builder: • An empty merge field, so the text opens with "Hi ," • The real ask buried below the preview cut-off • A long link that eats half the screen • An email subject that truncates mid-word • A sender name the lead doesn't recognize Do this before any message goes live: 1) Send it to your own phone from the real workflow, not the preview pane 2) Read only the lock-screen preview. Is the point clear from that alone? 3) Test once with a contact missing a first name and see what renders 4) Open the email in your phone's mail app, in light and dark mode 5) Check the sender name reads like a person or business they know 6) Fix it, resend, and read it again cold When Claude drafts the copy, add one more pass: ask it to rewrite the first line so the message makes sense from the preview alone. That single edit fixes most of what the phone exposes. The builder shows what you wrote. The phone shows what they got.
0
0
Read Every Message on a Phone First
Set Sending Hours Before You Switch On
Command note: An automation with no sending hours will text a new lead at 2 a.m. the moment one arrives. Most builds never set the hours. Until you turn on a Time window on each automation that sends, texts and emails can go out at any hour, including the middle of the night. What we shipped: the current GHL Command release adds a job to step 12 of Build a client account: Set the hours texts may go out. The build itself sets no sending hours, so the job tells you where to set them, and that Specific time starts at Monday to Friday, 8 to 5. Where it bites: • Form leads that land overnight • Quote follow-ups that fire on a weekend • Re-engagement sends kicked off from a late-night import • Any workflow cloned from a template that never had hours set Do it now: 1) List every workflow in the account that sends a text or email 2) Open each one and turn on its Time window 3) Pick the hours on purpose. Which hours apply to your clients is a question for your own lawyer, not a default 4) Re-check after every new build or re-plan, since a new sending workflow starts with no window 5) Write the hours on the client's handoff so they know when messages go out Speed to lead wins deals. Speed at 2 a.m. wins complaints.
0
0
Set Sending Hours Before You Switch On
1-10 of 180
Jerry Relth
3
22 points to level up
@jerry-relth-2483
Helping clinics help more people!

Active 52m ago
Joined Jun 2, 2026
Peoria, AZ