Solutions · Orders
Order and Delivery Support Agents
Arabic voice agents that answer “where is my order?” from your own order system. They look the order up during the call, make the changes your API allows, and pass the rest to your team.
- Order lookup through your API
- Order numbers by voice or keypad
- Outbound delivery updates
- Transfer to your team
- Phone, web and your app
Use cases
What an AI order status agent handles
Order lookup
The agent takes the order number by voice or keypad and asks your order system for its status through a tool. The answer comes from your data, not from the prompt.
Delivery status
Read back where the order is and when it is expected, from the fields your delivery system returns.
Delivery updates
Run an outbound campaign to customers whose delivery has changed, with each order number and new date on the call.
Corrections
Where your API allows a change, such as a new address or delivery slot, a tool makes it during the call and the agent confirms it to the customer.
Cancellations and returns
You set the boundaries. The agent explains your returns policy from the knowledge base and takes only the actions you have given it tools for.
Escalation
Damaged items, missing refunds and anything outside your policy can be routed to your team’s number by a flow agent.
Integration
Delivery support automation connected to your order system
How an order agent is wired to your backend, in the order you set it up.
- 01
Connect your order API
Add a function tool for each endpoint, such as order lookup or delivery update, and map the response fields to variables the agent can speak.
- 02
Keep credentials safe
API keys for your order and delivery systems are stored as encrypted project secrets and referenced by name, never written into a prompt.
- 03
Decide how customers identify
Ask for the order number, plus any detail your system needs to match it, such as a phone number. The check runs in your API.
- 04
Add your policies
Upload delivery areas, timings and your returns policy to the knowledge base, so answers follow your rules.
- 05
Design the exceptions
Branch the flow on the order’s status, and add transfer steps for the cases your team should handle.
- 06
Test and go live
Talk to the agent in the browser or by phone, then follow live calls with their transcript once customers start calling.
Example call
A “where is my order?” call, start to finish
An illustrative inbound call in Egyptian Arabic. The agent finds the order through a tool connected to the store’s order system, then moves the delivery through a second tool.
Example · order tracking
Examplehamsa agentأهلًا بيك في خدمة عملاء متجر النيل. أقدر أساعدك في إيه؟
callerطلبت أوردر من يومين ولسه موصلش
hamsa agentتحت أمرك. ممكن تقولّي رقم الطلب، أو تدخّله على لوحة الأرقام؟
dtmf: 6 digits captured · tool: orders.lookup · status: out_for_delivery
hamsa agentطلبك خرج مع المندوب النهارده الصبح، ومتوقع يوصل قبل الساعة ٦ المسا.
callerبس أنا مش هكون في البيت النهارده. ينفع يجي بكرة؟
hamsa agentينفع بكرة من ١٢ الضهر لحد ٤ العصر. يناسبك؟
callerأيوه، تمام
tool: deliveries.reschedule · outcome: delivery_rescheduled
hamsa agentتمام، غيّرت ميعاد التوصيل لبكرة من ١٢ لحد ٤. محتاج حاجة تانية؟
Specifications
Order support building blocks at a glance
Keypad capture, branching and transfers are flow agent features. Single prompt agents do not transfer calls.
| Setting | Detail |
|---|---|
| Order lookup | Function tools to your HTTP APIs, or MCP tools; response fields mapped to variables |
| Waiting on a tool | Hold music, or a spoken message when the request starts and completes |
| Order numbers | Spoken, or keypad capture of 1 to 20 digits with a termination key |
| Policies | Knowledge base from PDF, DOCX, DOC, TXT, HTML or EPUB files, up to 21MB each |
| Outbound updates | Campaigns from a CSV with per-recipient variables, inside the daily hours you set |
| Hand-off | Cold or warm transfer to a phone number; transfer to another Hamsa agent with full history |
| Outcomes | Your own JSON schema, such as order number, issue type and resolution, sent by webhook |
| Channels | Phone (Twilio or SIP trunk), a web link or embedded voice widget, the Voice Agents SDK in your app |
Measurement
Metrics for automated order tracking calls
Resolution and escalation
The satisfaction tab of the agent dashboard tracks first-call resolution and escalation rate, alongside CSAT and NPS.
Calls forwarded to people
The overview shows how many calls were forwarded to a human agent, next to call volume and duration.
Outcomes per call
Each call’s order number, issue type and resolution arrive in your systems as structured data, ready for your own reporting.
Exports
Download the dashboard as an Excel file, export call history as CSV, or pull the same figures through the analytics API.
FAQ
Questions about order and delivery support agents
How does the agent connect to our ecommerce platform or courier?
+
Through the APIs your systems already expose. A function tool calls any HTTP endpoint during the call, and MCP tools connect to MCP servers. Credentials are stored as encrypted project secrets and referenced by name.
How does the agent find the customer’s order?
+
It asks for the order number, which the customer can say or enter on the keypad, and passes it to your order API through a tool. The fields your API returns, such as status and expected delivery time, become variables the agent uses in its answer.
Can the agent change or cancel an order?
+
It can take the actions you give it tools for. If your API supports a change, such as a new delivery slot or address, the agent can make it during the call. For cancellations and returns, you can add the tool, or have the agent explain your policy and transfer the customer to your team.
Can we call customers about delayed deliveries?
+
Yes. Upload the affected customers as a CSV, with columns such as order number and new delivery date, and run an outbound campaign. Calls go out inside the daily hours and days you set, and you can pause, resume or retry recipients who did not answer.
What happens when the agent cannot solve the problem?
+
A flow agent can transfer the call to your team’s number, straight away or after telling the customer. A transfer to a phone number starts a new call, so the conversation history does not travel with it. The transcript, recording and outcomes stay in call history for your team.
Can customers reach the agent from our website or app?
+
Yes. You can publish the agent as a public link or embed it on your site as a voice widget. To build voice or text chat into your own app, use the Voice Agents SDK; there is no hosted chat widget.
Which Arabic dialects can order agents speak?
+
Agent voices are available in Egyptian, Saudi, Emirati, Jordanian, Lebanese, Syrian, Palestinian, Iraqi and Bahraini Arabic, as well as English. Speech recognition detects Arabic dialects automatically and handles customers who mix Arabic and English.
Keep reading
Solutions · Customer service
Customer Service AI Agents
Arabic support agents that answer from your documents, act through your APIs and transfer to your team, with resolution and escalation tracked.
Read →Hamsa Agents · Phone
AI Phone Agents
Inbound and outbound Arabic voice agents on your Twilio numbers or SIP trunk, with keypad input, transfers and campaigns.
Read →Hamsa Agents · Chat
Arabic Chat Agents
The same Hamsa agent over text, in a chat interface you build in your own website or app with the Web SDK.
Read →


