Confirmation before dispatch
The customer presses “1” if they will be home or “2” to reschedule.
“1” home, “2” reschedule
Order confirmation calls: couriers go where customers are waiting
The bot calls through the day's order list before dispatch, customers confirm or reschedule with one keypress, and the dispatcher sees the result before the courier gets in the van.
Already a customer? Log in
Updated
- Voicemail detection
- Campaigns from order lists
- Order status in chat
How does a bot confirm orders and deliveries?
Before the courier leaves, the bot calls the customer, names the order and delivery window and asks them to press “1” if they will be home or “2” to reschedule. If voicemail answers, the call is retried on schedule. The outcome for each order goes to your systems through an integration or webhook.
Calling the order list before dispatch
In the morning the dispatcher uploads the day's orders: phone, name, order number, delivery window and amount due. The bot calls customers within the set window, and campaign progress updates live in the console.
- Any file column becomes a script variable
- Numbers are checked and normalised before dialing
- Retries and pauses between attempts per campaign
- Status per call: waiting, dialing, done, failed
“Where is my order?” in chat, not on the phone line
Status, timing and address questions land in a shared inbox from the website widget, Telegram, Viber and Max. The bot answers the first message under your rules, and the agent gets an AI-suggested answer from the knowledge base and sends it.
- One inbox for every channel
- Canned replies for frequent questions
- Handoff to a person on keywords
- The customer's call history next to the chat
What a delivery service gets
Cash-on-delivery orders
The bot confirms the order, amount and address in advance.
Voicemail
The bot tells voicemail from a person and calls back.
Peak days
Call through the list without temporary staff. Volume is limited by your PBX lines and quota.
Outcomes to your systems
Each call outcome goes to your CRM or order system by integration or webhook.
Recording and transcript
Every call is recorded, so disputed cases are easy to check.
Delivery scenarios
Wasted trips
Problem. The courier arrives, nobody is home and the order goes back to the warehouse.
What the AI does. A pre-dispatch call with confirm or reschedule in one keypress.
Outcome. Routes are built from confirmed orders and reschedules are known in advance.
Cash-on-delivery orders
Problem. The customer changed their mind and the courier finds out at the door.
What the AI does. The bot confirms the order and amount ahead of time and logs a refusal.
Outcome. Refusals are known before the order is packed and shipped.
Friday peak
Problem. Agents cannot call every customer for evening deliveries.
What the AI does. A campaign on the order list with retries and voicemail detection.
Outcome. Agents focus on reschedules and problem orders.
How a pilot runs
We start with one route or one warehouse.
Describe the order list
Which fields you need: phone, name, order number, delivery window, amount.
Write the call script
Call text, key meanings, rescheduling and agent handoff rules.
Connect the PBX and export
Calls through your PBX or SIP trunk; outcomes come back by webhook.
Pilot on one route
Compare wasted trips with the period before the pilot.
Connects to your telephony and CRM
- A1 VATS
- Asterisk · pilot
- FreeSWITCH
- SIP trunk
- Bitrix24
- amoCRM
- 1C · pilot
- Webhooks and n8n
- A1 VATS
- Calls, recordings and transcripts from your PBX.
- Asterisk
- Connects to your existing PBX over SIP without a number change. Ready-made config, validated in a pilot.
- FreeSWITCH
- Outbound campaigns and inbound calls.
- SIP trunk
- Runs on your number and your carrier.
- Bitrix24
- Call outcome and summary land in the record timeline.
- amoCRM
- Call results written to amoCRM.
- 1C
- A “Phone call” document in 1C. Pilot on a test database.
- Webhooks and n8n
- Call and chat events flow into your systems.
Delivery service FAQ
How do we cut wasted courier trips?
Confirm the delivery before dispatch. The bot calls the customer, they press “1” or “2”, and the dispatcher sees who is waiting and who wants another time.
What if the customer is not home or does not answer?
Pressing “2” logs a reschedule. If the customer does not answer or voicemail picks up, the call is retried on the campaign schedule.
Where does the call outcome go?
To your CRM or order system through an integration or webhook. In the console you see the outcome per order.
Can the bot tell voicemail from a person?
Yes, from the first seconds of the call. If detection is uncertain, the call counts as unanswered and is retried.
How many calls can the bot make at once?
It depends on the number of lines on your PBX or SIP trunk and the quota agreed for the pilot. We size the volume to your order flow.
Do we need a separate PBX?
No. The bot calls through your PBX or SIP trunk from your number.
Start a pilot for your delivery service
We will demo delivery confirmation on your scenario.