Friday, July 31 · about 45 minutes of hands-on work, in order of impact.
The business in one paragraph: stpierre.ai (Akash’s company) runs Facebook ads that get homeowners to ask for concrete-repair estimates. An automated chat assistant collects each homeowner’s details and phone number. Those ready-to-call homeowners (“leads”) are handed to Dan, a concrete-leveling contractor in Dallas — the paying customer. More good leads flowing to Dan = more revenue. Everything on this page either gets money moving, keeps leads flowing, or fixes something in that pipeline.
The cast:
Why: three real people asked for concrete-repair estimates this week, but the chat assistant asked for their ZIP code before their phone number, so none of them left a number. Messenger is the only way to reach them now. Each one becomes a sellable lead for Dan the moment we get a phone number. (The bot’s question order is already being fixed by the agents — this task is just recovering these three people.)
Why: Dan’s booking link is the last missing piece before qualified leads can book straight onto his calendar automatically. The same message also asks him to check and delete some test cards, and nudges him about one lead we never heard back on. It’s one text; it’s fully written below.
Text this to Dan’s phone (his number is in Akash’s phone / the CRM under Dan):
Why: a charge failed on the Mastercard ending 3716. Facebook stops showing ads when a balance goes unpaid — and this is the account the Dallas ads run on. $40.01 is all it takes.
Why: the company wants to send introduction emails to prospective contractor clients (“cold email”), but you should never do that from your main domain — if emails get marked as spam it damages the main website’s reputation. So we need a separate, cheap domain. New email domains also need 2–3 weeks of “warm-up” before real sending, so every day this isn’t bought pushes the first emails further past mid-August. The moment it’s bought, the agents set up everything else automatically within about 10 minutes.
Two apps — GoHighLevel and Facebook’s business settings — block automation on certain screens. Everything below has exact click paths and pre-written text. Zero decisions to make; it’s all been approved already.
Why: these five jobs finish setting up Jean (the contractor-side text assistant) and fix a check that’s inflating our lead numbers. If you only have 5 minutes, do Job B — it switches off a set of 12 unapproved automatic emails that will otherwise fire at the next person who books a call.
What this is: when a contractor applies to work with stpierre.ai, Jean should text them a short series of follow-ups until they reply. The five texts are written and approved below — this job is building the automation that sends them.
The five messages (use exactly as written — the lowercase style is intentional):
Text 1 · sends 5 minutes after they apply:
Text 2 · 1 hour after they apply:
Text 3 · 5 hours after they apply:
Text 4 · 24 hours after they apply:
Text 5 · 3 days after they apply:
Text 1 fallback — use this instead of Text 1 only if the preview shows the “niche” field coming out blank:
{{contact.first_name}} is a fill-in-the-blank the software replaces with the person’s actual name. Paste them exactly as written — don’t edit inside the braces. If a preview ever shows literal braces instead of a name, use the fallback version and drop the niche word from Text 4 (“did you still want help adding more jobs?”).The wait times to type in — GoHighLevel counts each wait from the previous step, not from the application, so the numbers you enter are gaps:
| Step | Message should land at | Wait to actually type in |
|---|---|---|
| Wait before Text 1 | 5 min after applying | 5 minutes |
| Wait before Text 2 | 1 hour after applying | 55 minutes |
| Wait before Text 3 | 5 hours after applying | 4 hours |
| Wait before Text 4 | 24 hours after applying | 19 hours |
| Wait before Text 5 | 3 days after applying | 2 days |
Click path:
applied (this tag is stamped automatically on every applicant).test-lead (keeps our own test submissions out).launch-call-booked → Remove from workflow. (Another automation stamps that tag when they book, so booked people stop getting texts.)What this is: a workflow containing 12 automatic emails is currently live, and it fires at anyone who books a call. Problem: nobody has ever read or approved those 12 emails, and they mention a Zoom screen-share while the new call process is a plain phone call. It must be switched to Draft (off) before the next person books.
Nothing gets deleted — the emails stay saved for review later. Turning it back on is the same toggle.
What this is: the opposite problem. The workflow that receives conversations Jean escalates to a human (complaints, tricky questions) is sitting in Draft — so right now an escalation goes nowhere. One click turns it on.
What this is: when a contractor books a “launch call,” the calendar currently generates a Google Meet video link — but the texts they just received say Akash will call them. Two quick edits on one screen:
Already done automatically: Jean’s booking link is wired to this calendar and verified — no action needed on that part.
What this is: when a homeowner messages the Facebook page, a small AI check decides whether they’re a genuine prospect or spam/an accidental click. The check currently in place is too loose — it calls ~90% of conversations “qualified” when the real rate is ~69%, which inflates every number on the scoreboard. The strict version is below, recovered word-for-word from the approved original. Paste it exactly — do not reword anything.
Where to paste it — note this one lives in the Dallas sub-account (“Level King”), not stpierre.ai:
Already done automatically: the “services we do NOT offer” list this prompt refers to was missing and has been created (new concrete, foundation structural repair, asphalt, resurfacing, mobile homes, renters) — nothing will come out blank. The four wrongly-qualified leads since Jul 25 were also already un-tagged.
Why: two new Facebook pages (for expanding into Austin, Houston, San Antonio) can’t run ads until Akash’s logged-in profile formally claims them — Facebook has no way to automate this. Same visit: connecting Instagram lets the chat assistant answer Instagram DMs (right now those people bounce and get lost), and two 1-minute “tracking source” setups teach Facebook’s ad system which conversations turn into leads on the new pages.
What this is: Facebook learns who to show ads to from signals like “this conversation became a lead.” Only the Dallas page sends that signal today. Each new page needs a “messaging dataset” created once — about a minute each.
Why: the stored access key has stopped working (“unauthorized”), which leaves the agents blind to automation logs — that blindness is exactly how a broken automation once went unnoticed all weekend. Creating credentials is a humans-only rule.
Why: the system sent 7 test alerts to Akash’s phone from (626) 325-0175 and the software says “delivered.” If they’re not physically on the phone, the phone carrier is silently dropping our messages while the system reports success — we need to know that before trusting real lead alerts.
Why: Danny asked to be called. Sam and Spencer are homeowner leads whose details were delivered to a retired alert channel last week — meaning they may never have been contacted at all.
What’s deliberately NOT on this list — already decided and being executed by the AI agents in the background: the Dallas ad-budget change, a duplicate ad-set cleanup, tracking fixes, the chat assistant asking for phone number first, Jean’s configuration changes, all lead-pipeline bug fixes, dashboard corrections, and the outbound sales kit. Longer-dated housekeeping (subscription renewals due mid/late August) lives in the day’s master plan: Execution plan — July 31. The companion page Today’s Map explains every document created today.