Skip to main content
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.

​
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

List of automation sends

​
The 7 statuses of a send

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:
1

Trigger context

Which order, when it arrived at the trigger stage, who made the move (agent or another automation).
2

Detail of the template sent

The exact text that went out, resolved variables (customer name, amount…), buttons offered.
3

Status evolution

Timestamp of each transition: Scheduled at 14:02 → Sent at 14:02 → Delivered at 14:03 → Replied at 14:11 (“Confirm”).
4

Action triggered by response

If the customer clicked a button, see the target pipeline stage and confirm the order indeed moved.
5

Error (if applicable)

In case of failure, clear error message and number of attempts made.
Detail of a send

​
Understanding failures

If a send is Failed, Sendocki displays a plain-language explanation:
Sendocki automatically retries failed sends up to 3 times before definitively marking as “Failed”. You only see this status for real blockages.

​
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
That’s what lets you spot an automation that underperforms (reply rate dropping for example).

​
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