Integrations and live features
A few capabilities in NEMT OS depend on integrations your organization turns on in Settings. Here's what each one does, what it needs to work, and what to expect once it's connected.
Address autocomplete with Google Maps
Trip creation uses Google Maps to suggest addresses as dispatchers type, and to auto-fill city, state, and ZIP code once an address is selected. It also supplies the latitude and longitude shown alongside pickup and drop-off addresses, which support dispatch accuracy, route previews on the Live Map, and audit or fraud-review confirmation.
An administrator connects Google Maps from the Integrations area in Settings by providing an API key associated with your organization's Google Cloud billing account. Google Maps usage is billed by Google based on autocomplete sessions and map loads; typical NEMT trip volumes generally stay within Google's monthly free credit, but usage should still be monitored against your account's billing alerts. Until Google Maps is connected, address entry still works, but autocomplete suggestions, map previews, and coordinate confirmation are unavailable.
New address forms default to Arizona as a convenience for the primary service area; this default does not replace verifying the actual address before dispatch.
Live GPS tracking and driver notifications
When Google Maps is connected and a driver shares their location from the driver app, the Live Map shows current operational locations to dispatchers in real time, along with distance and estimated time of arrival for active trips. Drivers can open turn-by-turn navigation directly from an assigned trip.
Location sharing depends on the driver's device permission and a working connection, and stops when tracking is turned off or the trip is complete. GPS supports operational visibility and trip evidence for dispatch and audit — it is not a substitute for signatures, odometer entries, or a completed reason for visit.
Where enabled, the platform can also send automated SMS and email notifications tied to trip status: trip scheduled confirmations, reminders ahead of pickup, a "driver en route" alert with an ETA, a "driver arrived" alert, and a completion notice. An administrator enables and configures notification recipients and timing from the Integrations area in Settings; patients and staff who should not receive these messages can be excluded from notification lists at any time.
Workflow automation with Google Drive
Workflow automation removes manual steps after a trip is completed. The first supported automation is:
Trip completed → generate the AHCCCS trip report → upload it to a Google Drive folder → send an email notification.
Connect and configure a workflow
- Open the workflow area available to your organization in Settings.
- Choose the trigger event, such as a completed trip.
- Add actions in the order they should run — generate a trip report, run a saved report, upload to Google Drive, and/or send an email.
- Connect Google Drive with an organization Google account when the workflow uploads files, and choose the destination folder.
- Configure email recipients and any other action settings.
- Save and activate the workflow.
- Review run history after the first real event to confirm it behaved as expected.
Workflow actions run asynchronously and automatically retry transient failures, so a brief Google Drive or email outage does not prevent the underlying trip from being marked complete — check workflow run history if an expected file or email doesn't show up. Use a Google account with least-privileged access for the Drive connection, and only send protected trip or patient information to recipients who are authorized to receive it.