GOHIGHLEVEL ANSWERS & PROMPTS: PLAYBOOK T07 · WORKFLOWS & AUTOMATION
AUTHOR: DANIEL HALLMAN
KEYWORD: SMS
PLAYBOOK T07 · Workflows & Automation KEYWORD: SMS

How do you trace duplicate SMS sends in GoHighLevel?

Answer: Follow the Workflow link on each outgoing text to see which workflow run produced it.

STEP-BY-STEP INSTRUCTIONS + ANNOTATED GHL SCREENSHOTS

Steps in GoHighLevel

  1. STEP 1
    Open the thread with both outgoing texts in Conversations.
    REAL GHL SCREEN · CONVERSATIONS > TEAM INBOX ANNOTATED GHL SCREENSHOT
    Annotated GoHighLevel Conversations Team Inbox screenshot showing Conversations menu, Unread/All/Recent filters, and Manual Actions, Snippets, and Trigger Links tabs
    1Click Conversations in Left Menu 2Filter Unread, All, or Recent Threads 3Open Manual Actions, Snippets & Links
  2. STEP 2
    Select Workflow in each text’s message details. Each link opens Execution Details for that contact and run.
    REAL GHL SCREEN · WORKFLOW > EXECUTION LOGS ANNOTATED GHL SCREENSHOT
    Annotated GoHighLevel Workflow Execution Logs screenshot showing Execution logs tab, All actions and All statuses filters, and populated contact run rows
    1Open Execution Logs Tab 2Filter by Action Type or Status 3Search Contact to Trace Runs
  3. STEP 3
    Compare the contact, workflow, and run shown for both texts. Use Executed On to line up each Send SMS entry with its text.
    REAL GHL SCREEN · WORKFLOW > SETTINGS (RE-ENTRY & STOP ON RESPONSE) ANNOTATED GHL SCREENSHOT
    Annotated GoHighLevel Workflow Settings screenshot showing Settings tab, Allow re-entry toggle, and Stop on response toggle
    1Open Workflow Settings Tab 2Toggle Allow Re-entry Rules 3Enable Stop on Response
MODE: AGENT PROMPT
PASTE INTO CLAUDE CODE, CURSOR, CHATGPT, OR GOHIGHLEVEL ASK AI AGENT PROMPT
Compare the two HighLevel workflow runs I provide. For each one, list the contact, workflow, enrollment, and Send SMS action time. Point out which fields match and which differ. Mark any missing fields as unknown.
Possible Causes
  • Two matching texts can come from two actions in one run, separate runs of a workflow, or different workflows.
  • The text itself won’t tell you which happened.
Reading the Results
  • If both texts point to the same contact and run, look for two Send SMS entries in that run.
  • If the workflow and contact match but the runs differ, compare the enrollments in Enrollment History.
  • If the workflows differ, compare their triggers.
  • If the contacts differ, check which contact each run used.
  • A text without a Workflow link still needs a separate source check.
MENU PATH REFERENCE

GoHighLevel Menu Paths

Step Menu Path in GHL Action
Step 1 Conversations Open the thread with both outgoing texts in Conversations.
Step 2 Conversations > Message details > Workflow Select Workflow in each text’s message details.
Step 3 Execution Logs > Execution Details Compare the contact, workflow, and run shown for both texts.
Two outgoing text messages lead to workflow execution details for comparison by contact, workflow, and run.
VISUAL PLAYBOOK · PLAYBOOK T07 (WORKFLOWS & AUTOMATION) Back to Annotated GHL Screenshots ↑

HighLevel guide to Execution Logs and Enrollment History

Related Questions

BUILD FASTER IN GOHIGHLEVEL · FREE TRIAL BONUSES + MCP SERVER

Build this directly inside your GoHighLevel sub-account

Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI to build workflows, forms, and funnels from your editor, or start your GoHighLevel plan through our partner link to unlock $612+ in ready-to-import kits (including GHL Workflow Architect Pack) and weekly live clinics.