Intro / Context: This article explains why sequential SMS messages within a Dazos workflow may be marked as "Unsent" or "Blocked" by Call Tracking Metrics (CTM). The failure is typically due to carrier restrictions on sending multiple texts simultaneously to the same phone number.
Q: Why are some SMS messages in my workflow being marked as "Unsent" by CTM, even though Dazos triggered them?
A: The Dazos CRM successfully triggers the text message action, but the subsequent delivery is blocked by the messaging carrier (enforced via CTM) because of rate limit restrictions.
The carrier interprets multiple text messages sent to the same number within the same second as potential spam, blocking subsequent messages in the burst (e.g., messages #3 or #4).
Q: My workflow also duplicates messages. Is this related to the "Unsent" error?
A: Yes, the message duplication and the "Unsent" status are often symptoms of the same problem: triggers firing simultaneously.
When your workflow has multiple actions attempting to send messages at the exact same moment, the system often attempts to send the full set of messages twice (duplication), and then the carrier blocks the subsequent attempts (unsent status).
Q: How do I prevent rate limit errors, duplication, and successfully send all messages in my multi-step SMS workflow?
A: The definitive solution is to add a short delay between each sequential SMS message action within your Dazos workflow.
Identify Sequential Messages: In your workflow, identify the SMS actions that follow each other immediately.
Insert a Delay: Between the first SMS action and the next, insert a "Wait" or "Delay" step.
Set Time: Set the delay for at least 1 to 2 seconds. This slight pause is enough to prevent the carrier from flagging the texts as spam and ensures reliable delivery for all messages in the sequence.
Pro Tips / Extra Help:
Audit Your Triggers: If you are still seeing duplication, check your Dazos workflow settings to ensure you do not have multiple triggers set up that could fire the entire workflow simultaneously (e.g., one trigger for "Status Change" and another for "Lead Created").
Carrier Specific Error: The specific error message CTM reports is typically: "To number Rate limit exceeded. Please wait 20 seconds..." This is confirmation that the workflow needs a delay implemented.