Flows you can run
The six ready-made flows in RowCall's library, the moment each one is for, and how they compare.
Each page here is one flow from the library (Flows → Library in the app). A library flow comes complete: its call type, the inputs it needs, every line in Hindi and English, the questions it asks, how it can end and the actions it may take. Copy one with Use this flow and it becomes your own draft to change, simulate and publish.
Every page follows the same order: when to use it, what the shopper hears, its inputs, questions, outcomes and actions, how to start it, what to measure, and how to set it up step by step.
Which one to start with
Start with the moment where a delay costs you the most and the shopper already expects to hear from you.
| If your problem is | Flow | Library key | Call type | Starts when |
|---|---|---|---|---|
| Cash-on-delivery orders that come back undelivered | Order verification | order_verification | Transactional | A cash-on-delivery order is placed |
| Payments that fail at checkout | Live checkout help | live_checkout_help | Service | A payment fails, within a minute |
| Carts left before payment | Checkout recovery | abandoned_checkout | Promotional (copy as service to go live) | A checkout is left unpaid for an hour |
| Large items that need someone home | Delivery scheduling | delivery_slot | Service | An order needing installation is packed |
| Parcels coming back after a failed attempt | Failed delivery rescue | failed_delivery | Service | A courier marks a delivery as failed |
| Returns that could have been an exchange | Return-intent save | return_intent_save | Service | A shopper asks to return an item |
Most stores start with order verification: the shopper has just ordered, so the call is expected, the questions are short, and an unconfirmed order is easy to hold back.
How they compare
| Flow | Questions | Outcomes | Actions | Tries |
|---|---|---|---|---|
| Order verification | 4 | confirmed, address_changed, cancelled, needs_team | get_order, confirm_order, cancel_order, update_delivery_address | 2 |
| Live checkout help | 4 | link_sent, not_interested, needs_team | get_checkout, send_payment_link | 1 |
| Checkout recovery | 4 | link_sent, not_interested, needs_team | restore_checkout_link | 2 |
| Delivery scheduling | 2 and a read-back | booked, callback_requested, needs_team | get_delivery_slots, book_delivery_slot | 3 |
| Failed delivery rescue | 5 | rescheduled, cancelled, needs_team | update_delivery_address, book_delivery_slot, cancel_order | 2 |
| Return-intent save | 4 | exchanged, return_kept, needs_team | create_exchange | 2 |
Every flow opens with the disclosure line, asks if now is a good time, and ends with needs_team when an action is refused or doesn't answer, so your team follows up instead of the call guessing.
Order verification
Confirm cash-on-delivery orders and the address before dispatch.
Live checkout help
Send a payment link within a minute of a failed payment.
Checkout recovery
Bring shoppers back to a cart they left.
Delivery scheduling
Book a delivery and installation slot.
Failed delivery rescue
Rebook before the parcel goes back.
Return-intent save
Offer an exchange when a return is about the size.
The flow most stores launch first.