User
Write something
Monday Build Hour is happening in 6 days
Find the Workflows Left in Draft
Command note: A draft workflow looks finished in the builder and does nothing in the account. Drafts pile up quietly. Someone builds a follow-up, gets pulled away, and the client assumes it has been running for months. The fix starts with a list, not a rebuild. Paste this into Claude with GHL Command connected: "List every workflow in this sub-account using get_workflows. Group them by status: draft and published. For each draft, show the name, when it was created and when it was last updated. Flag drafts that have not been touched in 30+ days, and drafts whose name suggests something the client expects to be live (follow-up, reminder, nurture, review request). Read only. Do not publish, edit or delete anything." What you get back: • A clean count of live versus parked automations • The stale drafts nobody remembers starting • The ones that look like a promise the account is not keeping What to do with the list: 1) Ask the client which automations they believe are running, then compare against the list 2) Finish and test the drafts that matter, then publish them by hand 3) Rename parked drafts with a PARKED prefix and a one-line reason 4) Clear out the true leftovers once you have a copy Publishing stays a human step. Read the trigger and the first message one more time before anything goes live. If it is not published, it is not working. Know which ones those are.
0
0
Find the Workflows Left in Draft
Give Every Field One Format
Command note: An automation is only as reliable as the messiest record it reads. When "AZ", "Ariz." and "Arizona" all live in the same field, every filter, branch and AI summary has to guess. Guessing is where leads fall through. Where mixed formats hide: • Phone numbers with and without country codes • Dates typed as text instead of stored in date fields • States and cities spelled three different ways • Yes/No fields that also hold "y", "maybe" and blanks • Lead source values that drift every time someone adds a form Do it now: 1) Pick the five fields your workflows and reports lean on most. 2) Write one allowed format for each, with an example, in the account notes. 3) Where a field drives a branch or filter, use a dropdown, date or number field instead of free text. Build the new field; don't rename a live one. 4) Point every form and import at those same fields and options. 5) Pull 50 recent contacts and fix the outliers by hand. 6) Recheck the same five fields next month. A filter can only find what was written the same way twice.
0
0
Give Every Field One Format
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
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
1-30 of 191
powered by
GHL Command
skool.com/ghl-command-5986
The AI operator's room for GoHighLevel agencies.
Build your own community
Bring people together around your passion and get paid.
Powered by