Launch creation
From the navigation: Automations → New automation.Section 1 — Identity
1
Short name
Something descriptive in business terms. Examples:
- “COD confirmation request”
- “Payment reminder day before”
- “Shipping notification”
2
Description (optional)
A sentence to explain to the team what the automation is for. Useful when several of you will be managing them.
3
WhatsApp number (if you have several)
If several numbers are connected to Sendocki, choose which one will be used for this send.
Section 2 — The trigger
1
Choose the pipeline stage
Select from the list the stage that will trigger the message send.Example: “To confirm by call”.
2
Choose the Meta template to send
Select from your approved templates.
Only Meta-approved templates appear in the list. If you don’t see yours, check its status in Message templates.
3
Delay before send (optional)
How long to wait between the order arriving at the stage and the send.Common choices: 0 second (immediate send), 5 minutes (time for an agent to verify), 23 hours (reminder the day before delivery).
Section 3 — Map buttons to pipeline stages
If the chosen Meta template contains quick reply buttons, you see them listed here. For each button, you can choose which pipeline stage the order should move to when the customer clicks it.1
Read the list of template buttons
Sendocki automatically detects the buttons defined in the Meta template (e.g. “Confirm”, “Cancel”, “Later”).
2
Choose the target stage for each button
For each button, select the destination pipeline stage.Example:
- “Confirm” → Confirmed
- “Cancel” → Cancelled
3
Leave a button without a stage
If a button doesn’t need to move the order forward (just a text response), leave the field empty.
Section 4 — The timeout (optional)
If you want to handle the “customer doesn’t respond” case, configure the timeout:1
Enable the timeout
Toggle “Enable a fallback in case of non-response”.
2
Duration
How long to wait for a response (e.g. 24h, 48h, 7 days).
3
Starting point
From when to count:
- From message send (since Meta accepted)
- From message delivery (since the customer’s phone received it)
4
Fallback stage
Where to switch the order if no response after the timeout.Example: “Unreachable”.
Section 5 — Re-trigger
A last simple choice:Re-trigger forbidden (default)
If the same order goes through the same stage again, no new message is sent. Avoids spam.
Re-trigger allowed
Each pass through the stage resends the message. Useful for reminders.
Activate
1
Check the summary
Sendocki displays a summary in plain language:
“When an order arrives at ‘To confirm by call’, send the ‘Confirmation request’ template immediately. If the customer clicks ‘Confirm’, move the order to ‘Confirmed’. If no response after 24h, move to ‘Unreachable’.”
2
Activate
Toggle “Active” → the automation runs for all future orders.
Modify or disable later
All your automations are listed in Automations. For each one:- Disable (On/Off toggle) — keep it configured but paused
- Modify — reopen the form
- Delete — definitive
- See send history — see Send history
Best practices
- ✅ Start simple: 1 template + 1 stage, without timeout at first
- ✅ Test on a real order before letting it run on the whole pipeline
- ✅ Enable the timeout for stages that can stagnate (confirmation by call)
- ✅ Map all useful buttons — that’s what makes automation truly powerful
- ❌ Avoid very long delays (> 24h) except scheduled reminders: the order may have evolved in between
- ❌ Avoid enabling re-trigger by default — it generates spam
What’s next?
Ready-to-use examples
Typical COD cases to apply
Send history
See what happened