Troubleshooting
Texts to drivers are not being delivered
Symptom: a check-in or status text was sent and the driver never got it, or the app refused to send it at all.
First: was it refused, or was it dropped?
These are different problems.
Refused — the app told you it would not send, with a reason. Good: the reason is the answer. Read on to the matching section below.
Sent but never arrived — the app accepted it and the driver's phone never showed it. Usually a carrier-level rejection. Check the message's status on the check-in or the driver's page; failed deliveries carry a reason.
Refusal reasons and what to do
"Not registered for A2P 10DLC" / "awaiting carrier approval"
US mobile carriers will not deliver business texts from an unregistered number. The app blocks the send rather than burning a message that would be silently dropped on the way to the handset.
Settings shows your registration status. If it says pending, wait — the page updates itself when approval lands. If it says not registered or shows a refusal reason, see Get your number approved for texting.
"Quiet hours"
Nothing is sent before 8am or after 9pm in your company's timezone. If that window looks wrong, check Settings → Timezone — an account left on the default timezone will hold messages at the wrong hours.
"Consent missing"
The recipient has not signed an SMS consent, or they replied STOP. Send them a consent invitation from the driver's page. If they opted out, they have to text START themselves — you cannot re-subscribe them from your side.
"SMS is disabled in tenant settings"
Settings → Operations → SMS enabled.
"Driver has no phone number on file"
Add a mobile number on the driver's page. Mobile, not a landline.
"New account cooldown"
For the first week, large or repeating batches are held back. One-to-one operational texts still work.
Delivery failures after sending
If the message went out and came back failed, the reason shown maps to a carrier response:
| Reason | What it means | What to do |
|---|---|---|
| Handset unreachable | Phone off or out of coverage. | Retry later. |
| Blocked by handset | The driver's phone or carrier blocked it. | Call them. |
| Unknown number / landline / not a mobile | The number cannot receive texts. | Get their mobile number. |
| Carrier filtered the message | Spam filtering, usually content-related. | Contact support with the message text. |
| Registration required | Your number is not approved yet. | See above. |
| Daily cap exceeded | Your approved volume for the day is used up. | Contact support. |
| Toll-free number not verified | Verification is not complete. | Contact support. |
| Recipient replied STOP | They opted out. | Only they can opt back in. |
| Time-of-day or opt-out restriction | Blocked at the carrier. | Check the time and their consent. |
A failed delivery also raises a notification, so you are not relying on noticing it.
The driver replied and nothing happened
See A driver replied but the check-in still shows late.
When to contact support
Send the driver's mobile number, the approximate time of the send, and the exact refusal or failure text shown in the app.
Related
Still stuck?
Email support@dynamanic.io with your company name, what you did, what happened — quoting any message on screen — and when, with your timezone.