Template Automation is the Sendocki mechanism that: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.
- Sends a WhatsApp message automatically when an order arrives at a specific stage of your pipeline
- Reacts to customer response (button click, message) to move the order forward in the pipeline
The idea in one sentence
When an order arrives at stage X, send template Y. If the customer clicks a button, move the order to the corresponding stage. If no answer after N hours, switch to the fallback stage.That’s the entire mental model. Nothing more.
Why it’s useful
Save time
No more manually sending every confirmation, every follow-up, every reminder
Reduce oversights
An order that moves to “Shipped” → the customer is notified automatically, every time
Move the order forward automatically
The customer clicks “Confirm” in the WhatsApp → the order moves to “Confirmed” on its own
Recover silent customers
No reply after 24h → automatic switch to “Unreachable” stage
Concrete examples
| Situation | What the automation does |
|---|---|
| Order moves to “To confirm by call” | Sends “Order confirmation” template with Confirm / Cancel buttons |
| Customer clicks “Confirm” | The order automatically moves to “Confirmed” stage |
| Customer clicks “Cancel” | The order moves to “Cancelled” stage |
| No response after 24h | The order switches to “Unreachable” stage |
| Order moves to “Shipped” | Sends “Your order is on the way” template with tracking number |
Why our approach is different
Most automation tools ask you to build a complex workflow: connected nodes, nested branches, multiple conditions. Result: only a technical admin can create or modify them. Sendocki made the opposite choice: one automation = one template send at a pipeline stage. The rest (buttons, response wait, fallback) is integrated in the same screen, as simple choices.| Classic workflow builder | Sendocki Template Automation |
|---|---|
| Build a workflow with nodes | 1 template + 1 pipeline stage + a few options |
| Learn a condition syntax | Choose from lists |
| Several actions to chain | The template and its buttons do everything |
| Reserved for technical admins | Accessible to all managers |
| Hard to debug | Clear history: sent / read / replied / expired |
How it fits with other modules
| Module | Role |
|---|---|
| Pipeline | Defines the stages your orders go through |
| Message templates | The Meta-approved WhatsApp messages you send |
| Template Automation | The bridge between the two: “when the order arrives here, send this template” |
| Send history | See what happened: sent, read, replied, expired, failed |
What you’ll learn
How it works
The trigger, delay, buttons and timeout
Create an automation
The form in a few fields
Ready-to-use examples
Typical Morocco COD cases, ready to apply
Track sends
See history, understand failures