Once your automations are in service, you want to know: “Are the WhatsApps really going out? Are customers replying? What failed?” The send history answers all these questions, line by line.Documentation Index
Fetch the complete documentation index at: https://help.sendocki.io/llms.txt
Use this file to discover all available pages before exploring further.
Where to find it
From the navigation: Automations → History tab (or “Sends”). Complete list, from most recent to oldest.What you see for each send
| Info | Detail |
|---|---|
| Date / time | When the send was scheduled |
| Automation | Which one triggered the send |
| Order / customer | Who it’s for |
| Template sent | Which Meta template was used |
| Status | Scheduled / Sent / Delivered / Replied / Expired / Cancelled / Failed |
| Order stage | Where the order is now |
The 7 statuses of a send
- ⏳ Scheduled
- 📤 Sent
- 📬 Delivered
- 💬 Replied
- ⏱ Expired
- 🚫 Cancelled
- ❌ Failed
The send was planned but hasn’t gone out yet.Typical case: you configured a delay (e.g. 23h after arrival at “Shipped”) → the send waits for the planned time.
Filter the history
Quick filters available:- By automation: see only sends from a specific automation
- By status: for example, see only failures or expirations
- By period: today, this week, this month
- By order: all sends linked to a specific order
See the detail of a send
Clicking any line opens a detailed card:Trigger context
Which order, when it arrived at the trigger stage, who made the move (agent or another automation).
Detail of the template sent
The exact text that went out, resolved variables (customer name, amount…), buttons offered.
Status evolution
Timestamp of each transition: Scheduled at 14:02 → Sent at 14:02 → Delivered at 14:03 → Replied at 14:11 (“Confirm”).
Action triggered by response
If the customer clicked a button, see the target pipeline stage and confirm the order indeed moved.
Understanding failures
If a send is Failed, Sendocki displays a plain-language explanation:| Error message | What it means | How to correct |
|---|---|---|
| ”Template not approved” | The template lost its Meta approval (modified or rejected) | Check status in Message templates |
| ”Invalid WhatsApp number” | The customer doesn’t have WhatsApp on this number | Check / update customer card |
| ”24h window closed” | Meta’s 24h rule blocks the send (rare for templates) | The template used must be authorized out of window |
| ”WhatsApp account suspended” | Your WABA is temporarily blocked by Meta | Contact Sendocki support |
| ”Connection error” | Temporary network issue | Sendocki automatically retries |
Analytics at the automation level
On a specific automation’s page, you see additional aggregated stats:- Total number of sends since its creation
- Delivery rate (sent → delivered to customer)
- Reply rate (delivered → button click or text)
- Expiration rate (delivered → timeout without response)
- Evolution over the last 30 days
Practical tips
- ✅ Check history weekly at start — you quickly spot what works
- ✅ Filter by “Failed” to handle real issues in priority
- ✅ Look at reply rate: it’s the best indicator of your template’s quality
- ✅ Compare automations: if one has a 5% reply rate and another 40%, rework the template of the first
- ❌ Don’t panic on a few occasional failures — it’s normal (customers without WhatsApp, templates being re-approved, etc.)
What’s next?
Modify an automation
Reopen the form to adjust
Ready-to-use examples
Solid templates for inspiration