Kliovo Shop
8 Triggers. 20 Conditions. Your Entire Post-Purchase WhatsApp Stack, Automated.
WhatsApp ecommerce automation software in Kliovo Shop lets you build multi-step WhatsApp sequences for every order lifecycle moment — from COD confirmation to post-delivery CSAT, return handling to win-back. Set once, runs forever, retries on failure, cancels if the order is returned.
How Automation Flows works
Choose a trigger
Select from 8 order lifecycle events: Created, Confirmed, Booked, Dispatched, Out for Delivery, Delivered, Returned, or Cancelled.
Add conditions
Filter which orders this flow applies to: COD only, first-time customers, specific cities, minimum order value, specific couriers, and 15+ more conditions.
Configure stages
Add actions with delays: send a WhatsApp message, update order status, add a note, assign a team member. Multiple stages with configurable delays.
Flow runs
BullMQ executes the schedule. If a message fails, it retries with exponential backoff. If the order is returned or cancelled, pending stages auto-cancel.
Everything included
From triggers to conditions to retry logic — enterprise-grade automation without the enterprise price tag.
8 lifecycle triggers
Every meaningful order lifecycle event is a trigger — Created, Confirmed, Booked, Dispatched, Out for Delivery, Delivered, Returned, Cancelled.
20+ filter conditions
COD/prepaid, city, order value, platform (WooCommerce/Shopify), courier, first-time vs. repeat, and 15+ more — filter precisely to the orders that need a specific flow.
3 action types
Message (send WhatsApp), Workflow (update data), Hybrid (both). Combine them across stages to build complete automated post-purchase sequences.
9 workflow actions
Confirm, cancel, set status, add note, set flags, assign user, log event, escalate team, cancel pending automations — all configurable per stage.
Time-of-day scheduling
Send at 6 PM same day, never before 9 AM. Avoids sending dispatch messages at 2 AM when CN is created — customers get useful notifications at sensible hours.
BullMQ retry with exponential backoff
Failed message delivery retries at 2min → 10min → 30min → 120min. Dead-letter alerts via email if all retries exhausted. Nothing silently fails.
8 Trigger Events
9 Workflow Actions
Built for teams that...
The brand running COD confirmation manually
The pain: Our CS team was sending confirmation messages manually to 300 customers a day. One flow in Automation Flows replaced that entirely — they now handle maybe 20 exceptions instead.
The fix: Order Created → COD only → Send confirmation template → 30-minute reminder if no reply. CS team now handles maybe 20 exceptions a day instead of 300 confirmations.
The brand building a post-purchase experience
The pain: We knew we needed to follow up after delivery but no one was doing it consistently — too much manual work for a team of 5 handling 200+ orders a day.
The fix: 4-stage post-delivery flow: Day 1 thank you + review ask, Day 7 tip, Day 21 cross-sell, Day 45 re-engagement. LTV on customers in that flow is 2.4× those who are not.
The ops team handling exceptions
The pain: Orders would slip through unconfirmed for hours because no one was watching. By the time someone noticed, the customer had already moved on — and the order was going to return.
The fix: Exception Review flow: unconfirmed 2 hours after creation → internal alert to ops, note on order, flag Critical. No more slipped orders.
The numbers
8
Trigger events in the automation engine
Every meaningful order lifecycle moment is covered — nothing manual needed.
20+
Available filter conditions per flow
COD, city, courier, value, platform, first-time — precise targeting per flow.
4
Default templates ready to activate in under 5 minutes
COD Confirmation, Post-Delivery Follow-up, Dispatch Notice, Exception Review.
Common use cases
The complete COD confirmation flow
Trigger: Order Created. Condition: COD only. Stage 1 (immediate): Send confirmation template with Confirm/Cancel buttons. Stage 2 (30 minutes): If still unconfirmed, send reminder. Stage 3 (2 hours): If still unconfirmed, set Critical flag and alert ops. Three stages, set once, handles itself forever.
Dispatch notification with time-of-day scheduling
Trigger: Order Dispatched. Stage 1: Schedule for 6 PM same day. Message: dispatch notification with tracking link. Avoids sending messages at 2 AM when CN is created after a late packing session — customers get a useful notification at a sensible hour instead.
Return prevention re-engagement
Trigger: Order Delivered. Condition: First-time customer + COD + city in high-RTO zone. Stage 1 (Day 1): 'Please check your package and let us know if everything is correct' with feedback button. Early check reduces return rate by catching issues before the customer decides to refuse re-delivery.
Frequently asked questions
Can the same order trigger multiple flows?
Yes. An order can match multiple flows simultaneously — for example, it might trigger both a COD Confirmation flow and an Exception Review flow. Both run independently with their own stage schedules and retry queues.
What is the difference between Message, Workflow, and Hybrid action types?
Message sends a WhatsApp message only. Workflow takes a data action (update status, add note, assign user) only. Hybrid does both in the same stage — for example, send a confirmation message and simultaneously set the order status to confirmed.
What happens to a flow if the order is cancelled mid-sequence?
Pending stages auto-cancel if the order reaches a terminal status such as returned or cancelled. You can also configure this explicitly per stage with skip conditions — for example, skip Stage 2 if the order is already delivered.
How do retry failures get reported?
Dead-letter alerts are sent via email when all retry attempts (2min → 10min → 30min → 120min) are exhausted. The execution history viewer shows each stage's status — queued, sent, failed, or cancelled — per flow run.
Are the 4 default templates ready to use or do I need to customize them?
They are pre-built with standard content and timing. You customize the WhatsApp template variables (customer name, order total, tracking link) and activate them. They are designed to work out of the box for most Pakistani ecommerce operations.
Is there a limit on how many flows I can create?
Flow limits are plan-based. Starter allows 3 active flows. Growth allows 10. Pro allows unlimited. Enterprise allows unlimited with priority BullMQ execution. See the pricing page for full plan comparison.