Docs/Analytics
Understanding Sendify analytics
Your line dashboard is the fastest way to know whether things are healthy. Here is what each number is actually counting.
On this page
Volume and status metrics
| Metric | What it counts |
|---|---|
| Sends | Outbound messages your line sent in the period you are viewing |
| Replies | Inbound messages received back from leads |
| Queue | Messages waiting their turn to be sent, usually because the line is busy or has exceeded an hourly limit. |
| Pending | Messages handed to a line and awaiting a delivery result. Only a concern if they stay pending indefinitely, which usually means the line is down and cannot reach the gateway. |
| Deferred | Messages the AI is intentionally holding before sending, because of configured business hours or an initial wait time. This only happens when the AI is handling the message, not on manually sent messages. |
| Fails | Outbound messages that could not be delivered |
Response rates
| Metric | What it tells you |
|---|---|
| Initial message reply rate | How often your very first message earns a reply. This is a read on your list quality and your opener |
| Follow-up reply rate | How often a follow up rescues a silent thread. This is a read on your follow up copy and timing |
| Total response rate | Overall share of contacted leads who replied. This is the headline health number |
We recommend keeping total response rate above roughly 20%. Below that, risk of delivery restrictions rises. It is a benchmark, not a guaranteed cutoff, and it is explained in line health.
iMessage and SMS split
You can see how many recipients are receiving iMessage and how many are receiving normal carrier texts. A heavily Android audience is not a problem, it just means more of your conversation happens over SMS. Details in iMessage vs SMS.
Daily line usage
Usage shows how much of today's conversation capacity you have already spent on each line. If a line regularly finishes the day at its ceiling, you are sizing too tightly. See how many lines do I need.
Reading them together
No single number tells the story. Read response rate, line usage, current volume, and failure pattern as a set. A rising failure count with healthy response rate and heavy usage usually means volume and list quality, not a broken line.
Still need a hand?
If your volume is going to run past the daily or hourly limits, or something is not behaving the way these docs describe, talk to our team.