Messaging drivers

In-platform messaging, and why it is attached to the trip rather than to the person.

Written for
Dispatchers
Reading time
1 min
Last reviewed
July 22, 2026

Dispatch and drivers exchange messages inside the platform. Messages sent in the context of a trip stay attached to that trip, which is what makes them useful three weeks later when somebody asks why a pickup slipped.

When to use it

  • Anything that changes what a driver should do — a gate code, an access instruction, a rider running late.
  • Anything you will want a record of. A phone call leaves none.
  • Not for emergencies. Voice remains the right channel when seconds matter.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator