Logistics customer support where the shipment answers for itself.
Where is my parcel, it says delivered but I don't have it, the rider never called, change the address, I want to return this. Settl's AI agent reads the tracking feed, the delivery attempt and the proof of delivery before it replies, takes the action your policy allows — a reschedule, an address change, a refund under the cap — and hands the rest to a person with the facts already gathered.
Where is my order, answered from the tracking feed.
Most of a logistics queue is one question asked a thousand ways. The agent finds the shipment from the phone number, the order number or the AWB, reads the latest scan and the rider's live position, and gives the real status and ETA — on the phone in a spoken sentence, on WhatsApp in two short lines, by email with the number and the date in the body. When the promise is already missed, it says so, and applies the delay credit your policy defines instead of making the customer ask.
“Marked delivered, not received” is decided from the proof, not the argument.
A non-delivery report or a false-delivery claim is where generic bots give up. Settl reads what the record says happened and acts on it.
- Attempt failed, customer unreachable — the agent reaches the customer on their channel, confirms the address and books the next attempt.
- Delivered but not received — the proof of delivery and the rider's position at drop are checked; if they don't match the address, the claim goes to a person with the evidence and the rider is flagged.
- Rider never called, asked for extra cash, was rude — a complaint is logged against the rider, Last-mile Ops sees it, and the customer gets the goodwill credit your policy allows.
- Repeat claimants — a customer's claim history sets a trust level; risk-level claims go to review instead of automatic refund.
Reschedule, redirect and cancel — within the rules of the shipment.
A delivery can be rescheduled while it is still out; an address can change within the same zone; an order can be cancelled until it is picked up. The agent knows which of these the shipment's state still allows, does the ones your policy lets it do, and asks for approval on the rest. Your backend enforces its own rules on top: a delivered order is never cancelled, whatever anyone asks.
Returnable or not — and the customer told which, before they argue.
Return eligibility depends on the item: fresh produce and some categories are not returnable, and the agent says so with the policy cited, rather than opening a return that will be refused later. For a returnable item it books the pickup, or offers a replacement the customer can choose, and tracks the refund through to the gateway's reversal date.
The money questions, answered from the payment record.
A UPI debit with no order gets the reversal date from the gateway. A failed COD is re-attempted or converted to prepaid with a payment link in the thread. A refund request is checked against what was already refunded on the order — the total can never exceed the order's value, however many channels the customer tries.
The other half of the queue: your riders and merchants.
Rider and partner support is a separate surface on the same brain: payout and earnings lookups, onboarding and KYC status, app and device problems, catalogue and store availability for merchants. Reads run automatically; disputes go to the right team with the record attached.
WhatsApp, voice, chat, email, social
The channels your customers and riders already use, on one case per shipment issue.
Tracking, attempts, proof of delivery, payments
Through an adapter to your OMS, tracking and payments systems — read before the agent replies.
Track, reschedule, redirect, cancel, refund, book pickup
Reads auto-run; writes follow your policy, with identity checked first.
English, Hindi, Hinglish on calls
Regional languages on chat and WhatsApp; callers switch mid-sentence.
Hotspots, leakage, repeat contacts
Delay hotspots by zone and rider, refund leakage against policy, what forces a second contact.
Every conversation judged
Identity verified before action, ETA accurate, refund policy applied, escalation correct — scored on each transcript.
Frequently asked
Can the AI change a delivery address or cancel an order?
Within the rules you set and the shipment's state: an address change in the same zone while the parcel is out, a cancellation before pickup. Anything outside that goes to a person with one click to approve, and your order system still enforces its own rules.
How does it handle a parcel marked delivered that the customer says never arrived?
It reads the proof of delivery and where the rider was at the time of the drop. If they match the address, the customer is told what the record shows; if they don't, the claim goes to a person with the evidence and the rider is flagged. Customers with a history of such claims are routed to review.
Which systems does it need access to?
Your order management system, your tracking or delivery feed, and your payments provider, each through a swappable adapter. WhatsApp connects through Meta's Cloud API, Gupshup or Twilio; phone numbers over SIP.
Does it support riders and delivery partners, not just customers?
Yes. Partner support — payouts, onboarding, device issues, merchant catalogue questions — runs on the same agent as a separate surface, so a rider's query is never mixed into the customer queue.
How quickly can it go live?
About two weeks: one to connect the systems and policies and rehearse against past conversations, then copilot mode on live tickets. Tracking and reschedule intents usually go autonomous first.