How it works — the 5-step buyer journey
1. Dispatcher enters the askYou enter the shipment, stop, and requested appointment time. A validation gate blocks anything missing shipment, stop, or time. mock Outlook
2. Request email sentThe appointment request goes out to the receiver's contact email automatically. A duplicate guard blocks re-sending the same shipment + stop + requested time. mock Outlook
3. AI reads the replyWhen the receiver answers, mock AI extracts the proposed time and confirmation number. Ambiguous replies and extraction failures route to you — never silently dropped. mock AI
4. Tolerance rule appliesProposed times within ±60 minutes auto-accept and write back to the Tai stop. Anything outside the window is routed for your explicit Approve or Reject. ±60 min rule
5. Write-back & auditAccepted times write back to the Tai TMS stop. Every step lands in a per-brokerage audit trail with the rule cited — tenant-separated, nothing cross-tenant. mock Tai TMS audit
Live demo console (sample data)
All shipments, receivers, replies, and confirmations below are SAMPLE DATA. Adapters are mocks: mock Outlookmock AImock Tai TMS
Brokerage (tenant):
Manual dispatcher entry
Sample set (this tenant)
Cycles through: in-tolerance auto-accept · out-of-tolerance (approve) · out-of-tolerance (reject) · ambiguous reply · duplicate blocked · incomplete blocked · extraction failure.
Appointment request queue
Selected request
Load a sample request, then select it from the queue.
Outbox (emails + Tai write-backs)
Audit trail (this brokerage only)
Pilot pricing
| Plan | Price | Includes |
|---|---|---|
| Pilot | $1,500 fixed | One brokerage, one Tai TMS connection, up to 2 lanes, the ±60-minute tolerance rule, dispatcher approval queue, per-brokerage audit trail, handoff package (code + deployment scripts + concise docs). untested hypothesis |
| Scheduling plan | $149/mo | Monitoring, tolerance-rule tuning, monthly reliability report, email support with a next-business-day response target. untested hypothesis |
Billing is not connected. Next step: a 30-minute pilot scoping call — contact placeholder: pilot@example.com (replace before any real outreach).
Support, privacy & terms (summary)
- Support path: scheduling-plan customers get email support with a next-business-day response target. This demo has no support desk.
- Privacy: the demo stores nothing — all state is in-memory sample data that vanishes on reload. A real pilot would process only the appointment emails needed for scheduling, inside your brokerage's tenant.
- Terms: pilot scope is fixed in writing before work starts. In-tolerance auto-accepts run only under the documented ±60-minute rule (you can disable auto-accept and require approval on everything). Routed, ambiguous, and failed items never write back without your explicit Approve.