Industries / Logistics & Delivery
Industry · Logistics & last-mile delivery

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.

Copilot · private note to the agentnot sent to the customer
Intent
Refund status
Sentiment
Annoyed
Confidence
0.86
Summary
Refund for a cancelled order, 6 days ago. Meera is asking for the second time.
Suggested reply
Your refund of ₹486 was issued on Tuesday (RF-2291). Banks take 5–7 working days, so it should reach you by Monday.
refunds.md · §4live: RF-2291
Next best action: none needed — refund already issuedUse reply
1 replywith the live position and ETA, not a script
Auto / approvereads run themselves; cancellations and refunds follow your policy
Identity firstthe contact must match the consignee before anything changes
Hindi · Hinglish · Englishon calls; chat and WhatsApp in the customer's language
WISMO

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.

Tools the voice agent can callsame as every channel
track_orderRead · automatic
ST-48213 · out for delivery · Sunil · ETA 8:25
answer_questionRead · grounded
Delay policy §2.1 — ₹50 credit past 30 minutes
perform_actionWrite · confirmed
“Shall I add the credit?” — “Haan.” · phone matches order
transfer_to_humanHandoff
Same call · ticket fallback after 60 s
Slow lookup? It says “one moment, checking that for you” — and never asks the same question twice.
Failed and false deliveries

“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.
Handoff briefing · pinned to the conversationhuman assigned
low confidence · 0.41intent · damaged itemsentiment · angry
Why you're seeing this
Asking for a refund above ₹50 — that needs a person.
What they want
Full refund for a cracked blender jar, order ST-51840.
What's already known
Delivered yesterday 7:42 PM · photo attached · first complaint.
What I told them
That a colleague will confirm the refund within the hour.
Status → open · auto-assigned to the next available agent
Changes

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.

Website chat · signed-in customeronline
Wrong item — I got peanut butter, I'd ordered almond.
order ST-48226 readsubstitution policy §3
Sorry about that, Priya. A replacement almond butter is on its way — free, arriving 9:10 PM. Keep the jar.
Oh nice, thanks!
✓ replacement sent · 39 s
Type a message…
Returns and replacements

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.

Intake · email in its own shapeattached to case
Fromneha.kapoor@… → matched to customer
SubjectRe: Order ST-48990 — still no refund?
OrderST-48990 found in the body
Attachmentsbank-statement.pdf
Thread3 earlier messages · same case
Follow-upSecond time asking → priority raised
intent · refund statussentiment · frustrated
COD and payments

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.

Voice inbox · filed automaticallyresolved by AI
Private note · call summary
Caller+91 98•• ••4471 · Priya Menon
TopicDelivery delay · ST-48213
Outcome₹50 credit applied · no transfer
Duration1:12
Mera order abhi tak nahi aaya…
Let me pull that up — Sunil is about seven minutes away.
channel · voiceresolved_by_bothandle time 72 s
Riders and partners

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.

Case lifecycle10 steps · one record
01
Intake
Arrives on any channel, in that channel's shape
02
Identify
Phone, email, handle or VIN → the customer
03
Enrich
Live order, vehicle or account read automatically
04
Deduplicate
Same customer, same issue → the master case
05
Classify
Category, sentiment, priority, SLA
06
Decide
Next best action from your rules
07
Act
Reads auto-run; writes wait for approval
08
Communicate
Reply in the customer's own channel
09
Close
Checklist complete, closure record drafted
10
Grade
Scored by the judge, fed to analytics
Also in Logistics & Delivery
Channels

WhatsApp, voice, chat, email, social

The channels your customers and riders already use, on one case per shipment issue.

Lookups

Tracking, attempts, proof of delivery, payments

Through an adapter to your OMS, tracking and payments systems — read before the agent replies.

Actions

Track, reschedule, redirect, cancel, refund, book pickup

Reads auto-run; writes follow your policy, with identity checked first.

Languages

English, Hindi, Hinglish on calls

Regional languages on chat and WhatsApp; callers switch mid-sentence.

Analytics

Hotspots, leakage, repeat contacts

Delay hotspots by zone and rider, refund leakage against policy, what forces a second contact.

QA

Every conversation judged

Identity verified before action, ETA accurate, refund policy applied, escalation correct — scored on each transcript.

Questions

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.

GET STARTED

The queue that empties itself.

Give us your three worst intents and two weeks. We'll run them against your real tickets and show you what closes itself.

↗A working agent on your data, not slides
#Grounded on your policies — cited or handed off
✓Human approval on every action that moves money
TYPICAL RESPONSE · WITHIN ONE WORKING DAY
We use these details only to reply. Privacy policy