AI booking assistant
Pilot · Augusta Labs
Four siloed systems, one human-approved offer.
3t Global trains offshore and industrial crews. Coordinators re-key every booking across four systems that share no IDs. This assistant reads them all and drafts dated, prerequisite-checked offers — a coordinator approves every send and every booking.
I built the intake that turns two request sources into one case shape, the prerequisite engine — rule checks plus an LLM reader whose every point must quote the source text — e-learning routing, and the whole certificate-expiry agent, including a port of the legacy SQL procedure that reproduces its output row for row.
Piloting on live requests; writes to 3t’s systems stay held back until a person releases them.
- TypeScript
- Bun
- Azure SQL
- Azure AI Foundry
- App Service
- of pilot cases (714 of 855) needed no human read of prerequisite text
- 83%
- expiry pickup, down from a 19–36-day cycle
- Daily
- rows matched when porting the legacy procedure
- 43 / 43
How it works
- daily sweep
- legacy TMSported SQL procedure
- training platformexpiries export
- groupone case per delegate
- refresher resolverfrom prerequisite rules
- already handled?bookings · newer certs
- prerequisite check
- dates before expirylast 90 days first
- coordinator gate
- legacy TMSrequest forms
- training platformrequest export
- intake & dedupeone case shape
- course resolver
- e-learning router
- prerequisite readerLLM, quote-verified
- date searchlive runs
- draft reply
- coordinator gate


