What to type

List today's new GHL messages across all sub-accounts. Summarize each thread in one line. Mark the ones that look like a sales-ready reply and draft a follow-up SMS in my voice.

What happens

  1. Ambrose routes to Jordan (CRO) for sales-ready triage, with Taylor (CCO) on standby.
  2. Jordan calls ghl_conversations_list for the last 24h. If you have multiple sub-accounts the spoke federates across them.
  3. For each thread Jordan calls ghl_conversation_messages for the inbound payload.
  4. Jordan classifies each thread — sales_ready, needs_info, complaint, spam.
  5. For the sales-ready ones, reply-bot drafts an SMS in your brand voice. Drafts go to your inbox for approval — nothing sends without you clicking Approve.

Sample output

Sub-account: Big Bot Account
  • Maria Lopez (lead, ICHRA inquiry) — "When can we schedule a call?"
    [sales_ready] Draft: "Hi Maria — happy to talk this week. Are you open Tue 10am or Wed 2pm CT?"
  • John Park (existing client) — "I lost my card."
    [needs_info] Forward to Taylor (client success).

Sub-account: Demo Account
  • Marcus King — "Stop texting me."
    [opt_out] Add tag opted_out + suppress.

One-click actions

  • Approve all drafts — channel-bridge sends each as an SMS via the GHL conversation.
  • Add tags — bulk-applies the suggested tags via ghl_contact_add_tags.
  • Create tasks — one task per actionable item via ghl_task_create.

Wiring

GHL integration with a PIT that has Conversations + Contacts + Tasks scope.