AI for Logistics and Delivery.

Delivery is volume-driven, customer-experience-defining

A customer wakes up to a delivery notification, realises he is in meetings all day, and calls the courier hoping to redirect to the office. A grocery van arrives at noon to find the apartment empty. A new product launch shipment is stuck somewhere between warehouse and fulfilment, and the operations manager has called the carrier six times. Delivery is high volume, time-sensitive, and the call experience is the customer experience.

UAE e-commerce crossed 33 billion dirhams and is growing more than 20 percent year over year. Each failed attempt costs 30 to 50 dirhams. Peak periods like White Friday and Eid spike call volume five to ten times baseline.

Why traditional customer service hits a wall

Most calls are repetitive status checks. Reps burn human time on questions that should never reach a person.

What Edah does on every logistics call

Real-time status returned from a tracking number

Edah queries your warehouse and transport systems live, returns the current status, the next milestone, and the expected window. No hold music, no escalations for a status check.

Deliveries rescheduled before they fail

Edah calls customers 30 minutes before the window opens to confirm. If they cannot receive, the slot is rescheduled, redirected, or rerouted to a parcel locker in the same conversation.

Returns and pickups coordinated end to end

For return requests, Edah captures the order details, schedules a pickup slot, generates the return label, and sends an SMS with label and instructions.

Damaged and missing item complaints triaged

Issue, photo references, order details, and customer expectations captured. A structured ticket opens with the right SLA. Severe issues escalate immediately to a human with the full context.

Proactive notifications and driver-side calls

Out-for-delivery alerts, delay notifications, package-available-for-pickup messages, plus outbound calls to customers when a driver needs gate codes or parking instructions.

A real call, in 60 seconds

Caller: Hi, I have a refrigerator delivery scheduled today between 10 and 1. I will not be home. Can we reschedule?

Edah: Of course. I see the order, a Samsung 600-litre to Marina View Tower B. Next slots are tomorrow 2 to 5 PM, or Saturday 10 to 1. Which works?

Caller: Saturday morning.

Edah: Booked. Saturday 10 to 1 PM. The driver will call 30 minutes before arrival. SMS confirmation coming now. Anything else?

Caller: No, thank you.

What happened in the background

• Verified the customer by phone number against the order.

• Updated the slot in the warehouse and transport systems.

• Removed the original slot from today’s driver route.

• Booked the new Saturday slot and assigned a driver.

• Sent an SMS confirmation with the new window and contact instructions.

Built for the stack you already run

No WMS migration. No parallel ticketing. Your customer service team works the same systems, and the queue stops backing up at peak.

Compliance, built in

Customer addresses, contact details, order contents, and payment information are personal data under PDPL. For high-volume operators, daily flow is significant.

• Recording disclosure plays at the start of every call in the caller’s language.

• Consent captured with timestamped evidence and stored for seven years in a tamper-evident audit chain (SHA-256).

• All call data lives in Azure UAE North. Voice, transcripts, and PII never leave the country.

• PDPL data subject rights, including erasure, are first-class workflows in the dashboard.

• Outbound campaigns pass a synchronous TDRA pre-dial gate that validates calling windows, caller-ID ownership, and Do-Not-Call lists before every dial.

What changes after Edah

The tools running on this call

Six tool calls per shipment. Each logged, retried on failure, visible in your dashboard. No black boxes.

get_shipment_status(tracking_number)
verify_customer(phone, order_id)
check_availability(resource_type: "delivery_slot", filters: { region, vehicle_type })
update_booking(order_id, new_slot)
notify_team(channel: "dispatch", payload: { order_id, change: "reschedule" })
send_sms(to, template_id: "delivery_rescheduled", variables)

get_shipment_status(tracking_number)
verify_customer(phone, order_id)
check_availability(resource_type: "delivery_slot", filters: { region, vehicle_type })
update_booking(order_id, new_slot)
notify_team(channel: "dispatch", payload: { order_id, change: "reschedule" })
send_sms(to, template_id: "delivery_rescheduled", variables)

get_shipment_status(tracking_number)
verify_customer(phone, order_id)
check_availability(resource_type: "delivery_slot", filters: { region, vehicle_type })
update_booking(order_id, new_slot)
notify_team(channel: "dispatch", payload: { order_id, change: "reschedule" })
send_sms(to, template_id: "delivery_rescheduled", variables)

Going live

1. Share your tracking system, delivery slot rules, service catalogue, and return policy.

2. Edah drafts your tracking, reschedule, and return scenarios.

3. Connect WMS, TMS, OMS, and customer-service platforms. Pilot on one delivery region.

4. Go live in 24 to 72 hours. Add proactive pre-delivery confirmation and CSAT surveys in week two.

Customer experience is increasingly the difference between competing carriers. The operator that picks up instantly, in the right language, with the right answer, is the operator customers stay with. Book a 30-minute walkthrough.