We don’t always plan trips. Can Tranzia still work?
Yes. Tranzia can run at dispatch time (ticket creation/assignment), or via a lightweight “dispatch link” workflow that captures destination + context in seconds.
What’s the minimum integration?
One API call when a travel decision is made, store receipt_id with the ticket/trip record, and optionally export receipts to your storage.
Can you integrate with SMS or chat dispatch?
Yes. For pilots, start with a dispatch link or ticket hook. SMS/chat automation can be added once value is proven.
What if your API is down?
You choose behavior: advisory fallback (proceed without receipt and log unavailability) or fail-closed (block the workflow until a receipt is generated, only for strict environments).
How do you handle travel outside NYC/London or low-coverage areas?
We return a coverage level and explicitly list known gaps. In low coverage, Tranzia emphasizes policy-first decision governance rather than pretending to have precise local scoring.
Do you support global time zones and 24/7 operations?
Yes. Receipts record local_time and timezone; policy can be expressed relative to local time windows (e.g., after-hours).
How do we enforce recommendations?
Tranzia is advisory by default. Enforcement occurs where you integrate it: dispatch assignment, authorization, or reimbursement rules that require a PASS receipt.
How long does a pilot take to set up?
A minimal pilot can start without deep integration using a dispatch link and a small set of policy rules, then mature into tighter integrations after value is validated.