Delivery scheduling
Call a shopper when a large item is packed, offer the open delivery and installation slots, read the chosen one back and book it.
Delivery scheduling calls a shopper when a large item, such as a TV or a washing machine, is ready to go. It looks up the open slots, offers them, reads the chosen one back and books it. A shopper for whom none work gets a call back from your team.
| Library key | delivery_slot |
| Call type | Service. See Call types and consent |
| Languages | Starts in Hindi, or in the language input; English too, and it follows the shopper if they switch |
| Longest call | 4 minutes |
| Tries per shopper | 3, two hours apart |
When to use it
Start it when an order that needs delivery and installation is packed. A large item that arrives when nobody is home costs a second trip, and installation needs someone there. Booking the slot by phone before the van leaves avoids both.
What the shopper hears
Agent: Hi Arjun, this is Halden's automated assistant, calling to book delivery and installation for your 55-inch TV. This call is recorded. Is now a good time?
Shopper: Yes.
Agent: One moment, let me check the open slots. We can come on Saturday morning, Saturday evening or Monday morning. Which suits you?
Shopper: Saturday morning.
Agent: So that's Saturday morning for your 55-inch TV. Shall I book it?
Shopper: Yes.
Agent: Booked. You'll get a message the day before. Thank you, goodbye.
Inputs it needs
| Input | Label | Type | Required | Sample |
|---|---|---|---|---|
customer_name | Name | text | Yes | Arjun |
phone | Phone | phone | Yes | +919812345603 |
order_id | Order | text | Yes | 6610 |
product | Product | text | Yes | a 55-inch TV |
language | Language | text | No | en-IN to start in English |
Questions it asks
| Key | Question | Answer |
|---|---|---|
good_time | Is now a good time? | Yes or no. A "no" ends the call politely |
pick_slot | We can come on Saturday morning, Saturday evening or Monday morning. Which suits you? | A choice: the slots, or None of these |
confirm_slot | So that's {pick_slot} for your {product}. Shall I book it? | A read-back the shopper confirms before anything is booked |
Outcomes
| Outcome | Label | When |
|---|---|---|
booked | Slot booked | The shopper picked a slot and it was booked |
callback_requested | Call back | None of the slots suit them; your team calls to find a time |
needs_team | Needs the team | The slots couldn't be read or the booking was refused |
Actions it may take
| Action | Kind | What it does |
|---|---|---|
get_delivery_slots | Read | Lists the delivery or installation slots open for the order |
book_delivery_slot | Write | Books the slot the shopper chose |
How to start it
- From your store, by API:
POST /v1/runswith"flowKey": "delivery_slot", when the order is packed. - From the dashboard: select the shoppers in Contacts and choose Call N contacts to book a day's deliveries at once.
What to measure
In Results, for the flow:
- How the calls ended:
bookedagainstcallback_requested. - Summary → the
pick_slotquestion: which slots shoppers choose, to plan your teams. - First-attempt deliveries: in your logistics data, how many booked orders were delivered on the booked slot.
Set it up, step by step
Copy it from the library
Flows → Library → Delivery and installation slot → Use this flow.Set your slots
On the Diagram tab, open
pick_slotand change the question and its choices to your real slots. Keep None of these.Simulate it
Simulate → Talk as the shopper. Pick a slot, then run it again and say none of them suit you.
Publish and connect the actions
Publish, then connect
get_delivery_slotsandbook_delivery_slotin Developers → Actions.Start it when orders are packed
Send one run per packed order that needs installation.
Rebook before the parcel goes back.