A client reports that an outbound message was never delivered even though the provider returned a "status": "success" response and "test_mode": false, indicating the message was queued on their system.
We need the provider to trace the message and explain why it was not delivered.
Message Details
Our Switch Message ID: e3024a2d-b068-44ce-b10e-9ebc8e994345
StackVerify Message ID: 121846fa-d51e-4aaa-80bf-6f3ff261a65b
Destination: +256767249760
Provider Response:
JSON
{
"status": "success",
"test_mode": false
}
Expected Behavior
Message should be delivered to the handset or return an appropriate error indicating failure.
Actual Behavior
Message remains undelivered despite provider indicating successful queueing.
Request
Please trace message ID 121846fa-d51e-4aaa-80bf-6f3ff261a65b and provide:
Delivery logs
Operator response/error
Explanation for nondelivery
A client reports that an outbound message was never delivered even though the provider returned a "status": "success" response and "test_mode": false, indicating the message was queued on their system.
We need the provider to trace the message and explain why it was not delivered.
Message Details
Our Switch Message ID: e3024a2d-b068-44ce-b10e-9ebc8e994345
StackVerify Message ID: 121846fa-d51e-4aaa-80bf-6f3ff261a65b
Destination: +256767249760
Provider Response:
JSON
{
"status": "success",
"test_mode": false
}
Expected Behavior
Message should be delivered to the handset or return an appropriate error indicating failure.
Actual Behavior
Message remains undelivered despite provider indicating successful queueing.
Request
Please trace message ID 121846fa-d51e-4aaa-80bf-6f3ff261a65b and provide:
Delivery logs
Operator response/error
Explanation for nondelivery