Skip to main content

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.

Here are standard configurations of automations covering the most common Morocco COD cases. For each, you see exactly what to fill in the creation form.
Before applying an example: first create the corresponding Meta templates in Message templates — otherwise you won’t be able to select them.

1. Confirmation request on arrival

An order arrives → WhatsApp message with Confirm / Cancel.
FieldValue
Trigger stageTo confirm by call
Meta template”Confirmation request” (with Confirm / Cancel buttons)
Delay before send0 second
”Confirm” buttonConfirmed stage
”Cancel” buttonCancelled stage
Timeout24h (from delivery) → Unreachable stage
Re-triggerForbidden
Benefit: 60-80% of confirmations happen without human call.

2. COD payment reminder day before delivery

23h after shipping → remind the customer to prepare the amount.
FieldValue
Trigger stageShipped
Meta template”Prepare your payment”
Delay before send23 hours
Mapped buttonsNone (informational message)
TimeoutNone
Re-triggerForbidden
Benefit: fewer “I don’t have the amount” refusals at delivery.
The parcel is gone → the customer receives their tracking number immediately.
FieldValue
Trigger stageShipped
Meta template”Your order is on the way” (with link button to tracking)
Delay before send0 second
Mapped buttonsNone (external link button)
TimeoutNone
Re-triggerForbidden
Benefit: fewer support calls “where is my parcel?“.

4. Post-delivery thank you message

The order is delivered → thank the customer + invite to leave a review.
FieldValue
Trigger stageDelivered
Meta template”Thank you for your purchase” (with Leave a review button)
Delay before send2 hours (time for the customer to test the product)
“Leave a review” buttonTo convert to loyal stage (or leave empty if you don’t have a dedicated stage)
TimeoutNone
Re-triggerForbidden
Benefit: collect reviews and tag your satisfied customers.

5. Re-engage unconfirmed after 24h

An order stayed 24h without confirmation → automatic re-engagement with new buttons.
FieldValue
Trigger stageTo call back (specific second re-engagement stage)
Meta template”Little reminder — do you confirm?” (Confirm / Cancel buttons)
Delay before send0 second
”Confirm” buttonConfirmed
”Cancel” buttonCancelled
Timeout48h → Definitive unreachable
Re-triggerForbidden
Benefit: second chance for orders we would have lost.

6. Quick confirmation on order creation

As soon as an order arrives (Shopify, YouCan, manual) → instant first contact.
FieldValue
Trigger stageNew (the first stage of your pipeline)
Meta template”Hello, we have received your order”
Delay before send0 second
Mapped buttonsNone
TimeoutNone
Re-triggerForbidden
Benefit: the customer feels taken care of immediately, lowers purchase anxiety.

How to copy an example

1

Create the corresponding Meta template

Go to Message templates and create the template with the right text and the right buttons. Wait for Meta approval.
2

Create the mentioned pipeline stages

If the example mentions a stage you don’t have (e.g. “To call back”, “To convert to loyal”), add it in Pipeline.
3

Create the automation

Go to Automations → New automation and copy the table values. See Create an automation.
4

Test on a real order

Move a test order through the trigger stage and verify that the WhatsApp goes out correctly.
5

Activate

All good → toggle to Active.

Suggested “starter” path

If you’re getting started, activate in this order:
  1. ✅ Confirmation request on arrival (example 1)
  2. ✅ Shipping notification (example 3)
  3. ✅ Day-before payment reminder (example 2)
  4. ✅ Post-delivery thank you message (example 4)
These 4 automations cover 70% of daily use of a Morocco COD store.

What’s next?

Create your own automation

Build from the form

Track sends

Verify your automations are running well