Content is written and ready. The BUILDS are GHL workflow-builder / settings tasks (not doable via the MCP) — walk through with Rio ~20 min when fresh. Order = highest leverage first. All copy is Rio voice: capitalized sentences, no em dashes, STOP compliance on any cold SMS.
1. 🔁 Missed-call / no-answer text-back ← build FIRST
Why: turns every unanswered dial into a live text thread. Most of your dials won't answer; this catches them.
Recommended trigger = TAG-based, not auto-on-every-miss. Auto-texting every no-answer risks the A2P line (spam flags) and hits contacts you don't want to nurture. Instead: when a call doesn't connect, you tap a txt-back tag on that contact → the workflow fires the SMS. You stay in control of which misses get texted.
The SMS (two versions — the workflow picks by which dial-tag the contact has):
Wrap shops (wrap-dial-0724):
Hey, this is Rio with Uprise, just tried giving you a call. I help wrap and tint shops around Miami book more jobs through paid ads, not a website pitch. Worth a quick look? Reply here or I'll try you back. Reply STOP to opt out.
Logistics (trucking-0724):
Hey, this is Rio with Uprise, just tried giving you a call. I help logistics and freight companies bring in more direct shippers through paid ads. Worth a quick look? Reply here or I'll try you back. Reply STOP to opt out.
Build steps (GHL → Automation → Workflows → + Create Workflow → Start from scratch):
- Trigger: Contact Tag → "Contact Tag is
txt-back" - (Optional split) Add an If/Else: if tag
wrap-dial-0724→ wrap SMS; else iftrucking-0724→ logistics SMS. (Or skip the split and start with one niche.) - Action: Send SMS → paste the copy above. From = the (954) A2P line.
- Action: Remove Tag
txt-back(so it can re-fire later if needed). - Publish. Test: tag one of your own test contacts
txt-back, confirm the text sends.
2. 💬 "Send the breakdown" SMS snippet ← build SECOND (2 min)
Why: the reply you'll send 50x/day when someone bites. Snippet = type / in any SMS box and it drops in.
The snippet (GHL uses {{contact.first_name}} for the name merge):
Appreciate you {{contact.first_name}}. Send me the best email and I'll put together a quick breakdown of what I'd run for your shop and have it over in a day or two. No obligation, if it's useful we talk.
Logistics variant (swap "shop" for "company"):
Appreciate you {{contact.first_name}}. Send me the best email and I'll put together a quick breakdown of what I'd run for your company and have it over in a day or two. No obligation, if it's useful we talk.
Build steps: Settings → Snippets → + Add Snippet → name it "Breakdown Follow-up" → paste → Save. (Now type /breakdown in any conversation to insert it.)
3. 🎁 Referral tracking pipeline ← build THIRD
Why: the $250-per-close referral program is live but has no way to track who referred whom or what's owed. (_resurface open item.)
Structure = a dedicated Opportunities pipeline. Each REFERRED business = one opportunity.
Pipeline name: Referrals Stages:
- Referred — a partner sent you this lead (log partner name in a custom field)
- Contacted — you reached the referred business
- In talks — real conversation happening
- Closed – won — they became a client → $250 owed to referrer
- Paid out — the $250 has been sent
Custom field to add: Referred By (text) on the opportunity, so every referred lead carries who gets the $250.
Build steps: Opportunities → Pipelines → + Add Pipeline → name "Referrals" → add the 5 stages above → Save. Then Settings → Custom Fields → add Referred By (Opportunity, text).
Referrer list to seed later: Katelyne, Lee, Lucia, Dylan + family (per 7/23 session).
4. 📢 Ringless voicemail ← SEPARATE DAY (not paste-and-go)
Needs a third-party RVM provider (Slybroadcast / Drop Cowboy / similar) connected to GHL, likely a paid add-on. Scope it as its own build once the dial + text-back rail is proven. Don't bundle with the above.
Status
- Missed-call text-back workflow (tag
txt-back) - Breakdown snippet saved
- Referrals pipeline +
Referred Byfield - RVM — later, needs provider