Delivery reports
SMS delivery reports you can act on
At a glance
- Status for every message
- Filters: date, campaign, sender, status
- Campaign summaries with counts
- Costs per message and campaign
What each status means
Each message moves through a small number of statuses. Understanding them helps you decide when to wait, when to fix something and when to contact the recipient another way.
- Queued / Scheduled — saved and waiting to be processed (or waiting for its scheduled time).
- Processing / Retry pending — being submitted to the SMS provider, or waiting to retry after a temporary problem.
- Submitted / Sent — accepted by the provider and on its way through the mobile network.
- Delivered — the network reported delivery to the handset.
- Failed / Rejected — could not be delivered or was refused; these messages are not charged.
- Cancelled — stopped before it was sent.
- Unknown — the provider’s response was unclear (for example a timeout). We check with the provider rather than resending, so the recipient never gets a duplicate.
Find any message quickly
Filter reports by date range, campaign, sender and status. Looking for every failed message in last week’s campaign? Two filters and you have the list, with the recipient numbers and any error information.
Campaign reports
Each campaign has its own summary: number of recipients, total SMS parts, estimated and actual cost, and counts by status. Campaigns end as completed, partially completed, failed or cancelled, so you can see at a glance whether everything went as planned.
Costs you can reconcile
Reports show the cost of each message based on its parts and your price per part. Because charges are applied only when the provider accepts a message, failed and rejected messages show no charge. Your wallet’s transactions and invoices let you match spending to campaigns.
Reports for your own dashboards
Developers can read the same information through the API: the status of each message, campaign counts, and a summary endpoint with totals by status, delivery rate and cost for a date range. For real-time updates, configure a webhook and receive a signed message.status event whenever a message changes status.
Use cases
How businesses use it
Check a campaign
See how many messages were delivered and follow up on failures.Answer a customer
Confirm whether and when an order update was delivered to a specific number.Clean your list
Find numbers that repeatedly fail and review them in your contacts.Monthly reporting
Share message volumes and costs with management or a client.
FAQ
Frequently asked questions
Why does a message show “unknown”?
It means the result of the submission was unclear, for example because the provider did not answer in time. SMSGELY checks with the provider instead of sending again, so the recipient does not get a duplicate. You are only charged if the provider confirms it accepted the message.
Is a “sent” message the same as delivered?
Not quite. Sent means the message was accepted and passed on through the network. Delivered means the network reported that it reached the handset. Some messages stay at sent if the network does not return a delivery report.
Am I charged for failed messages?
No. Failed and rejected messages are not charged, and any reserved funds are released to your available balance.
Can I get delivery updates in my own system?
Yes. Use the API to check message and campaign status, or configure a webhook to receive signed message.status and campaign.completed events.
Start sending with SMSGELY
Create an account, top up your prepaid wallet and send your first message from the dashboard or the API.