The conversation becomes the trip.
Email, SMS, and MMS arrive in one shared workspace. InstaRoute understands the request, connects it to the customer and reservation, and helps dispatch create or update the trip without re-keying the conversation.
Hi team,
Attached is Tuesday's Chicago airport manifest: seven transfers total. Please note the DL 1576 crew count increased to five.
Thank you,
Lakefront Events Operations
NBNadia BrooksInternal note · team onlyJul 20 · 02:28
Crew count checked. Sprinter CHI0308 still fits all seven transfers. Ready for manifest review.
Crew count 4 pax → 5 pax
Changes stay staged until dispatch applies them together.
Create or update the trip from the conversation
For a new request, InstaRoute prepares the booking from the message. For a change, it brings up the connected reservation and requested update. Dispatch reviews and confirms the details.
Payment failures arrive with the trip and the next action
When a scheduled authorization fails, the customer gets a secure card-update request and dispatch gets a critical inbox alert tied to the reservation. The team can call, text, take payment, or apply its unpaid-trip policy without hunting for context.
Forward the manifest. Review every trip at once.
InstaRoute extracts each trip from the manifest, compares it with the board, and stages new trips, updates, and matches for dispatch to review and apply together.
Assign it. Snooze it. See who is working it.
Email, SMS, and MMS share open, snoozed, and done states. Assign a conversation, see presence and typing, leave internal notes, share drafts, and avoid duplicate replies.
The conversation stays with the reservation
Replies, attachments, internal notes, and booking changes remain connected to the trip.
Draft the reply with the trip already understood
InstaRoute can prepare or refine a response using customer, reservation, and conversation context. Dispatch reviews and edits before sending by email or SMS.
Questions about the inbox.
What mailbox access does InstaRoute request, and why?
InstaRoute asks for access to the one company mailbox you connect, and nothing else. It works the same way for Gmail, Outlook, and IMAP. We use that access to show your mail in the shared inbox, send replies from your company address in the same thread, and mark threads read or filed when your team resolves them. Trip details are extracted from incoming reservations and manifests so they can become trips on the board. We do not sell your data, use it for advertising, or use it to train AI models. You can disconnect at any time from InstaRoute settings, or from your Google Account permissions page for Gmail. See our Privacy Policy.
Can Inbox create and update reservations?
Yes. For a new request, InstaRoute prepares the booking from the message. For a change, it brings up the connected reservation and the requested update for dispatch to review.
How does manifest review work?
InstaRoute extracts each trip from the forwarded manifest, compares it with the board, and stages new trips, updates, and matches for dispatch to review and apply together.
Does dispatch approve changes before they reach the board?
Yes. InstaRoute prepares the booking or update from the conversation, and dispatch reviews and confirms the details before anything changes.
How do assignments, snoozing, and shared drafts work?
Email, SMS, and MMS share open, snoozed, and done states. Dispatch can assign a conversation, see presence and typing, leave internal notes, and share drafts to avoid duplicate replies.
Are SMS and MMS included?
Yes. Email, SMS, and MMS all arrive in the same shared workspace alongside every reservation they touch.
How is Inbox different from Chat and Radio?
Inbox is the shared customer email, SMS, and MMS workspace. Team Chat carries internal company conversation, and Radio carries driver voice. The three stay separate.
Turn a real customer message into work on the board.
Follow a manifest or booking request as InstaRoute extracts the trips, connects the conversation, stages the changes, and prepares the reply.