01
Lemic302, CC0Play inside the rules
Shopee allows 2–3 contacts within 5 days. Alodi never steps outside.
Alodi messages and calls the buyer the moment a delivery fails, then hands the next shipper structured context — so the second drop lands.
No answerRescheduledRefusedRoute plannerVoice memo
CHATCALLEXTRACTGUARD
Shipper cardDispatcherCS queueOrder contextMetrics log
Shippers we
interviewed
interviewed
The problem
₫0
return fee the seller pays on each failed order
Source: Shopee policy §7.1; ₫40,000 cap since Apr 2025 (GHN)
0–0%
of orders refused at the door, nationwide
Source: VECOM, Nguoi Lao Dong, 19 Jul 2025
0
delivery windows a Shopee buyer can choose
Source: Shopee Help Center, article 79559
₫0M
lost a month in one area of 4,000 orders a day
Source: Team cost model, PRD §18.8 (modelled)
We asked both sidesPlaceholder values until the interview export lands
Buyersn = 100 · online shoppers
- 0%want to choose a delivery window
- 0%called the shipper back and couldn’t reach them
Shippersn = 12 · 6 carriers
- 0%of their calls to buyers go unanswered
- 0%would use an Alodi-like system
Our approach
02
Samson Vowles, CC0Draw a hard line
The agent asks and calls. Money and a buyer’s record go to a person.
Ask for a window
Label a refusal
Call 08:00–20:30
Return to seller
Apply ≥ 0.85
Settle a conflict
03
Tirza van Dijk, CC0Prove it with evals
Codex changes one thing per round. The held-out set decides.
0.59
held-out F1
Introducing Alodi
Alodi turns a failed delivery into a confirmed next attempt. One shipper tap starts chat and voice outreach, and the next shipper gets a rule-checked card: when, where and who.
- For
- Carriers like SPX, their shippers and buyers
- Starts with
- One tap: No answer · Rescheduled · Refused
- Does
- Asks for a window before dispatch, recovers by chat and voice, writes a context card
- Never
- Labels or returns an order without a person
- Built on
- GPT-Live-1, the Decisions API on GPT-6 Luna and GPT-6.1 Terra; built with Codex
One-Tap Rescue Pipeline
One agent with four tools runs as a state machine per order. The shipper’s tap starts it; the policy guard decides when it stops.
Shipper tapTrigger · A
↳Always
Rescue chatAgent
↳Silent 60 min
Voice callAgent
↳Answered
ExtractorJSON + confidence
OR
Auto-applyall fields ≥ 0.85
Human reviewlow or conflicting
In-Flight Context Extraction
Turn a 74-second call into four typed fields before the shipper reaches the next stop. Every field carries its own confidence.
“Tomorrow after five, please. Leave it with security in Tower B — or call my wife.”
Extractor · strict JSON
time_windowSun 1 Nov · 17:00–20:00
drop_locationSecurity desk, Tower B
alt_receiverWife · 0903 *** 214
Rule-Based Escalation
Quiet hours, contact caps and confidence thresholds are rules, not prompts. Anything high-stakes is routed to a person.
↳ Always↳ AND↳ OR
Policy guard rules
- 1key call_hoursonly between08:0020:30
- 2key max_callsper cycle is2
- 3key confidencebelow0.85→ human review
- 4key triggerequalsREFUSED→ CS, no contact
Deploy Your Way
Browser demo today, shadow mode at one depot next, a regional on-prem gateway when the data has to stay in-house.
Demo
Browser onlyMock dataFast-forward clock
Pilot
Shadow modeOne depotNo buyer contact
On-prem
Regional gatewayPII stays inFine-tuned ASR
One tap instead of an error code
The shipper picks No answer, Rescheduled, or Refused. The agent does the rest.
Ask for a window before delivery
Send two or more slots from the route planner as quick replies. Only for risky orders: high COD, past failures.
Message first, call if silent
Chat goes out the moment the shipper taps. 60 minutes of silence triggers call one, two hours later call two. Calls only 08:00–20:30.
A ten-second voice memo
Buyer rescheduled on the phone? The shipper repeats it aloud; speech-to-text turns it into structured data.
Extraction with confidence
Window, drop-off, alternate receiver, address fix: each field is JSON with a confidence score. Low confidence goes to a person.
Policy guard
Quiet hours, contact caps, “stop” means stop, recording consent before every call.
Order Context Object
Versioned context with an audit log: who changed what, and when, across agent, buyer, shipper and CS.
Refusals go straight to CS
Never spend effort calling a buyer who refused at the door. A “suspected bomb” label is only a suggestion; a person approves it.
Architecture
GPT-6.1 Terra runs the agent in the middle. The carrier keeps every system it already has.
Route planner
feasible windows
Order system
today’s orders, COD
Shipper tap
No answer · Rescheduled · Refused
Buyer chat
quick replies, free text
AI call
GPT-Live-1 over a branded SIP line
alodiagent layer
Alodi Agent
GPT-6.1 Terra · Agents SDK, one run per order
Triage
Decisions API on GPT-6 Luna
Policy guard
quiet hours · caps · 0.85 · masks PII
Scheduler
60′ and +2 h timers, retries
PostgreSQLRedisMinIOmasked text out
Context card
to the shipper, next attempt
CS queue
a person decides
Ops dashboard
events, metrics, audit
Models · OpenAImasked text to the cloud · calls after consent
- GPT-Live-1real-time voice calls with the buyer
- Decisions APIGPT-6 Luna triages every message
- GPT-6.1 Terraorchestrates buyer, shipper and policy
- gpt-oss-20blocal fallback · PhoWhisper for memos
Source: PRD §16, §16.7, §18.8. The demo runs the same shape on the OpenAI API, SQLite and mock data.
Outcomes
Saved a month, one areaProjected
₫0M
Lost today₫473M
With Alodi₫286M
−₫187M · 40%
From answer to cardTarget
< 0 s
0 s2 s4 s6 s8 s10 s
Answers
Buyer
Sees the card
Next shipper
No form to fill, no extra step. The next attempt simply knows when, where and who.
Source: Team cost model, PRD §18.8, best-in-class rescue 25% → 65% (Shipsy vendor range); time-to-context target, PRD §2.3.
OpenAI ecosystem · tech stack
GPT-Live-1 talks to the buyer, GPT-6 Luna triages through the Decisions API, GPT-6.1 Terra orchestrates. Codex builds it.
OpenAI, end to endproduction design · the demo runs the OpenAI API
RuntimeOne agent, six workers
- Alodi Agent · Agents SDK · GPT-6.1 Terra
- TriageDecisions API · GPT-6 Luna
- VoiceGPT-Live-1
- Rescue chatGPT-6.1 Terra
- WindowDecisions API · choice
- ExtractorTerra · Structured Outputs
- Guardrailscode + SDK guardrails
- Triage first
- GPT-6 Luna answers routine questions through the Decisions API; only real cases reach Terra
- Private by default
- Text to the cloud is masked; calls run on GPT-Live-1 after consent; gpt-oss-20b stays local as fallback
- Gated
- OpenAI Evals on the held-out set before any prompt or model change
Build timeShipped with Codex, reviewed by people
- SpecifyPRD and rules become scriptsChatGPT + Codex
- BuildPair-programming with AGENTS.mdCodex CLI · IDE
- ParalleliseOne task, one branch, one PRCodex cloud
- ReviewEvery PR reviewed before mergeCodex in GitHub
- EvaluateOne change per round, held-out F1Codex + Evals
Demo · 31 Oct
- Next.js
- TypeScript
- Tailwind CSS
- Motion
- FastAPI
- Pydantic
- OpenAI API
- GPT Live
- GPT Transcribe
- Presidio
- SQLite
- Caddy
- Docker
Production · per area
- GPT-Live-1
- Decisions API
- GPT-6.1 Terra
- gpt-oss-20b
- Ollama / vLLM
PhoWhisper- Piper TTS
- NVIDIA RTX
- PostgreSQL
- Redis
- Temporal
- MinIO
- Zalo ZNS
- Asterisk
- Grafana
Competitive landscape
Source: ClickPost NDR Management and Parth (Angel One); Shipsy NDR guide and last-mile page; AfterShip exception agent; Ringg AI failed-delivery recovery; Shiprocket contact-buyer docs; GHTK scheduled delivery. Vendor figures are self-reported. “Not disclosed” means we found nothing on the official pages as of October 2026.
The team
Four builders from UTS × HCMUT.
One shipper tap, one well-timed conversation, one context card for the next attempt.
Sources
- Shopee Return & Refund Policy §7.1–7.2 — Sellers pay return shipping on failed-delivery orders; no fee when the carrier is at fault. Checked 31 Oct 2026.
- GHN, Who pays for Shopee returns — Since 1 Apr 2025 the seller pays return shipping up to 40,000 VND per order (20,000 VND for express); Shopee covers the rest.
- Shopee Help Center, article 79559 — “Shopee does not yet support choosing a specific delivery time.”
- Nguoi Lao Dong, 19 Jul 2025 — VECOM: 8–12% nationwide, up to 20% in remote areas. Tran Anh Tung (UEF): 10–15% today, 25–30% in sale season.
- GHN, shipper earnings per order — 6,000–8,000 VND per order (not an official Shopee figure).
- Metric via Brands Vietnam, E-commerce Report 2025 — 429.7 trillion VND across 4 marketplaces (Shopee, TikTok Shop, Lazada, Tiki), up 34.75%.
- Shipsy, What is NDR management — Industry-average rescue rate 20–30%, best-in-class 50–65% (vendor figures).
- Shopee Help Center, article 79196 — Three failed COD orders within 90 days disables COD for the buyer.
- Shopee Help Center, article 79569 — Redelivery process: 2–3 contact attempts, rescheduling within 5 days.
- ClickPost, NDR Management — Automated buyer outreach over SMS, email, WhatsApp and IVR; responses become reattempt or return instructions.
- Angel One, ClickPost Parth — Brands using the Parth voice agent report 15–20% lower RTO; MyMuse resolves 80% of NDRs within a day.
- Shipsy, Last-mile delivery — Proactive delivery windows, geofencing, CX Agent rescues NDRs before a return is triggered.
- AfterShip, Exception handling agent — Gathers exception context and drafts a fix for approval; customer Dr. Squatch reports 58% faster resolution.
- Ringg AI, Failed delivery recovery — Voice agent calls after a failed attempt, classifies the cause and confirms a reattempt.
- Shiprocket, Contact buyer / IVR — Automated SMS + IVR when the shipper marks the buyer unreachable; IVR on Advanced/Pro plans only.
- GHTK, Scheduled delivery — Recipients pick a date and a morning/afternoon window in the app; no exact hour yet.
- AssemblyAI, Vietnamese — Vietnamese supported for batch and streaming transcription.
- VinAI, PhoWhisper — Open-source Vietnamese speech recognition.