Hey everyone!

We are releasing Version 4.99.0 on Thursday, December 04, 2025.

This release focuses on tag-driven workflows, standardized passenger identity (names & IDs), patient photo management, smarter address handling, and better dispatcher controls around cancellations and trip tickets. The goal: make it much easier to find the right passenger/trip, keep drivers fully informed, and reduce rework for dispatch and billing teams.

Key Highlights

Tag-powered dispatching & search on Operations + CSV import

Use tags end-to-end: auto-populated on the booking form, Filterable on Operations, and updatable in bulk via CSV.

Standardized passenger names & IDs across Operations, Workbooks & Invoices

First / Middle / Last / Alias / MRN / Medicaid ID now behave consistently across search, filters, display, exports, and invoices.

Patient photos from CIM to Driver App

Upload, preview, and enlarge patient photos on CIM and surface them in the Driver App for visual identification.

Smarter address & gate code model with Active Pickup Address (APA)

Introduces a clear address model in CIM plus auto-population, validation, and gate code handling on the booking form.

Dispatcher control to reverse mistaken SMS/call cancellations

Quickly restore trips canceled by passenger responses without rebuilding bookings from scratch.

Trip ticket generation fix for completed trips

Corrected timestamp validation so trip tickets generate reliably for completed trips.

Feature Enhancements

1. Tag-Based Search & Display on Operations (Trips & Routes)

What’s new?

Tag filters on Trips & Routes pane

• New “Tags” filter on the Operations → Trips & Routes pane.
• Supports dropdown selection and type-ahead search (e.g., typing “Whee” returns “Wheelchair”).
• Works with single or multiple tags at the same time.
• Tag filters work in combination with other filters (Date, Route, Driver, etc.) using AND logic so only trips that match all active filters appear.

Fast, responsive filtering

• Tag-based filters update the Trips list without noticeable delay when you add or remove tags.

Clear/reset behavior

• “Clear Filters” and de-selecting tags will reset back to the full, unfiltered Trips list.

Benefit: Dispatchers can now quickly zero in on critical trips (e.g., Wheelchair, Oxygen, School Route) and see tags at a glance while routing and assigning drivers.

2. Tagging on Dispatch Booking Form + Propagation to CIM & Driver App (V

What’s new?

Auto-populate tags from Passenger profile

• When you create a booking and select a passenger, Tobi auto-populates all tags from that passenger’s CIM profile onto the booking form.
• Tags appear grouped and clearly labeled under their respective tag groups.

Edit & override on the booking form

Dispatchers can:

• Add new tags from the system list.
• Update/replace tags as needed.
• Remove tags that don’t apply to this particular trip.
• Changes persist on save and show exactly as configured when the booking is reopened.

Tags on  Driver App

• When the trip is dispatched, the same tags propagate to the Driver App under trip details (using the configured grouped/icon-based representation).

Tag propagation to CIM for new passengers

• If you create a booking for a new passenger and add tags, those tags also propagate back to CIM, ensuring the passenger profile stays in sync.

Benefit: Tags now flow smoothly from passenger profile → booking → trip card → driver, keeping everyone consistent and reducing manual re-entry.

3. Tag CSV Import & Validation

What’s new?

Bulk tag updates via CSV

• Tenant Admins can upload a CSV to update tags for passenger bookings in bulk.
• On successful commit, tags are applied to the relevant Passengers/Trips/Routes/Standing Orders.

Dry run & validation

• During upload, the system checks for:
  • Deleted tags.
  • Tags that don’t exist in the system.
  • Invalid rows are flagged in an error log file so Admins know exactly what failed.

CIM propagation for new passengers

• As with booking form tagging, tags created for new passengers via import also propagate to CIM where applicable.

Benefit: Large-scale tag updates are now manageable and auditable, greatly cutting down manual maintenance across passengers and trips.

4. Standardized Passenger Search (Operations, Global Search, Generate Invoice)

What’s new

Search across First / Middle / Last / Alias / MRN / Medicaid ID

• Global Passenger Search and relevant search interfaces now support:
  • First Name
  • Middle Name
  • Last Name
  • Alias Name
  • MRN Number
  • Medicaid ID

Users can search by any single field or any combination of these.

Standardized display format

Search results render passenger names in a consistent format:

Last, First Middle (Alias)

Alias appears in parentheses only if it exists.

Partial & progressive search

• Typing partial text (e.g., “Joh”) returns all matching records where that substring appears in First, Middle, Last, or Alias.
• As you add more fields (e.g., start with Last Name, then add First or Middle), results progressively refine using AND logic.

Benefit: Dispatchers can reliably find the right passenger even with incomplete name information or when only an MRN/Medicaid ID is available.

5. Enhanced Search & Display in Generate Invoice

What’s new?

Richer search in Generate Invoice

• The Generate Invoice panel search bar now looks across:
  • First Name
  • Middle Name
  • Last Name
  • Alias Name
  • MRN Number
  • Medicaid ID
• Search is case-insensitive and supports partial text.
• Standardized display format in invoice search results

Results display passenger names as:

Last Name, First Name Middle Name (Alias Name) — MRN# 123456

• Middle Name and Alias are optional and only shown if present.
• MRN is shown whenever available.

Benefit: Billing teams can quickly locate the correct passenger bookings for invoicing, even with messy or partial naming data.

6. Workbook: Filters, Display & Export for Names + IDs

What’s new?

New workbook filters

• In Workbook views (Bookings, Trips, Invoices), you now search passengers based on:
  • First Name
  • Middle Name
  • Last Name
  • Alias Name
• Filters are case-insensitive and support partial text.
• Combining multiple filters uses AND logic (e.g., First = John, Last = Doe).

Standardized display in Workbooks

Workbook views display passenger names in format:

Last, First Middle (Alias)

• Alias appears in parentheses if present.

Workbook exports

• Exports now include standardized columns for:
  • First Name
  • Middle Name
  • Last Name
  • Alias Name
  • MRN Number
  • Medicaid ID
  • Full Name (Last, First Middle (Alias))
• Exported data matches what you see in Workbook views, including sort order and values.

Benefit: Operations, reporting, and billing teams now work off a single, consistent source of truth for passenger identity across UI and exported data.

7. Generate Invoice – Name Format & ID Display

What’s new?

Standardized passenger name on invoices

• Invoices generated from Trips or Workbooks render passenger names as:

Last, First Middle (Alias)

• Alias is only shown if available.

MRN & Medicaid ID on invoices

• Invoices now include MRN Number and Medicaid ID beneath passenger details, by default.
• An option in invoice configuration allows you to hide MRN and Medicaid ID from invoices and exports when needed for privacy or policy reasons.

Benefit: Invoices now align with the new naming and ID standards while still allowing tenants to adapt to their own privacy policies.

8. Patient Photo Management (CIM + Driver App)

What’s new?

Upload & manage photos in CIM

• Dispatchers and authorized admins can upload or replace a patient photo from the CIM passenger profile.
• Only JPG/PNG up to 2 MB are accepted.
• Re-uploads replace the previous photo (with version control handled on the backend).
• If no photo exists, a placeholder icon is shown.

Dispatcher photo preview for emergencies

• Clicking the photo in CIM opens an enlarged preview (overlay/pop-up).
• Dispatchers can use this enlarged view to capture a screenshot and share via Connect Teams in emergencies.

Driver App visibility

• When a passenger with a stored photo is part of an assigned route, the Driver App shows the passenger photo for visual verification at pickup.

Benefit: Visual identification significantly reduces the risk of wrong-patient pickups, especially in facilities with high passenger volume and similar names.

9. Booking Form & CIM: Address Model, APA & Gate Code

What’s new?

CIM address model (Primary, Temporary, APA, Gate Code)

• Each passenger address in CIM supports:
• A freeform Address Label (e.g., Home, Work, Relative’s House).
• An optional Gate Code.
• Address types and behavior:
  • Exactly one Primary Address.
  • Zero or more Temporary Addresses.
  • One Temporary Address can be marked as Active Primary Address (APA) at a time.
  • If an Active Temporary Address is deleted, the Primary Address automatically becomes active again.
  • Changing the APA does not retroactively update existing trips or standing orders; it only affects future bookings created via the booking form.
  • Address remains optional on the passenger profile; profiles can be saved without any address.

Auto-populated addresses on booking creation

• When creating a booking for a passenger with existing addresses/bookings:
• Pickup/Drop-off fields auto-populate using this hierarchy:
  • Active Primary Address (Other/APA)
  • Primary Address
  • Last Booking Address

Gate Code and Label are included.

A source label under the field indicates:

• “From Active Primary Address (Other Address)”
• “From Primary Address”
• “From Past Booking”

Available Address dropdown

• Clicking “Available Address” shows all active CIM addresses for the passenger, with labels (Home/Work/Relative, etc.).
• Selecting an address auto-fills full address, label, and gate code.

New address entry + validation

Dispatchers can type a new address and:

• Add a Label.
• Add an optional Gate Code.
• Address is validated using Google Maps API; if validation fails, an error displays (but label/gate code remain unaffected).

Leg-level address validation

• The system checks whether Leg 1 pickup and Leg 2 drop-off exist as Active Addresses in CIM.
• If they don’t, it warns the dispatcher and allows saving the address back into CIM.

Manual entry respected

Dispatchers can still freely enter addresses without auto-overwrite unless they explicitly choose “Populate from CIM”.

Benefit: You get a robust address model that supports recurring pickup locations (e.g., school, dialysis center) without overwriting permanent addresses, while still ensuring addresses are validated and reusable.

10. Dispatcher Reversal of Mistaken SMS/Call Cancellations

What’s new?

Visual indication of SMS/call cancellation

• Trips canceled due to passenger SMS or call response are marked with a warning triangle on the trip card.

“Confirm Booking” reversal option

Dispatchers can click “Confirm Booking” on a canceled trip to:

• Open the standard confirmation dialogue.
• Optionally add notes/confirmation text.
• Restore the trip as Confirmed (or appropriate active state).

Status & logs

Once reversed:

• The trip’s status and color coding update immediately on the Operations screen.
• The action is captured in Activity Logs for auditability.

Benefit: Dispatchers can safely recover from accidental cancellations without rebuilding bookings, while leadership still has visibility into how often reversals occur.

Bug Fixes

Trip Ticket Not Generating for Completed Trips (Timestamp Validation)

Identification:

Generating a trip ticket for a completed trip showed the error:

“Pickup time should be greater than arrival time and dropoff time should be greater than arrival time”

even when timestamps were valid or only one of the fields existed.

The trip ticket was not generated and “View Trip Ticket” never appeared in the menu.

Resolution

• Adjusted the timestamp validation logic so that:
• Completed trips with valid PU/DO and arrival timestamps pass validation.
• Validation no longer incorrectly blocks ticket generation when only one time in a pair is present.

After resolution:

• Trip tickets generate as expected for completed trips.
• A “View Trip Ticket” option appears in the three-dot menu for eligible trips.

Benefit: Dispatchers can reliably generate and access trip tickets for completed runs without being blocked by incorrect validation errors.