How to Stop Outgoing Messages in Case of an Accidental Campaign
Purpose
This SOP explains how to immediately stop outgoing messages if a large campaign is accidentally sent and messages are still showing as Pending or Queued in the myCRMSIM dashboard.
This SOP explains how to immediately stop outgoing messages if a large campaign is accidentally sent and messages are still showing as Pending or Queued in the myCRMSIM dashboard.
When to Use This SOP
- A bulk or campaign message was sent by mistake
- Messages are still pending / queued in myCRMSIM
- Your device was turned off and queued messages are now sending quickly when the device has been turned on
- You want to prevent further messages from being delivered
Step-by-Step Procedure
- Open the Android gateway phone
- Log out from the gateway app
- Turn OFF internet (Wi-Fi + Mobile Data)
- Go to Settings → Apps → Gateway App
- Tap:
- Clear Cache
- Clear Data
- Clear Cache
- DO NOT reconnect the phone to the internet yet
- Open myCRMSIM Dashboard on your browser
- Go to Messages tab
- Apply filters:
- Status = Pending
- Status = Queued
- Status = Pending
- Select all pending and queued messages
- Delete all of them
- Confirm deletion
- Verify that:
- No new pending/queued messages are appearing
- No new pending/queued messages are appearing
- Pause or disable automations/campaigns in GHL
- Ensure no workflows, triggers, or retries are sending new messages
Step 4: Reconnect the Android Gateway
⚠️ This step is critical. If GHL keeps sending messages, the queue will refill.
- Once the dashboard shows:
- ZERO Pending messages
- ZERO Queued messages
- ZERO Pending messages
- Turn internet ON (Wi-Fi or Mobile Data) on the Android phone
- Open or reinstall the gateway app
- Scan the QR code to log in again
- Wait for successful connection
Step 5: Resume Normal Usage
- Monitor the Messages tab for a few minutes
- Confirm that:
- No old messages are sent
- Only new intentional messages are being delivered
- No old messages are sent
- Resume normal operations
- Always test campaigns with 1–2 messages first
- Pause GHL workflows before large sends
- Avoid reconnecting the gateway while queues are uncleared
