In legacy 911, transferring a call usually meant moving the voice path from one PSAP to another.

But in NG911, that is no longer enough.

Today’s emergencies are no longer defined by a single phone number, a fixed address, or one local jurisdiction. A caller may be mobile. A crash may happen near a boundary. A school emergency may involve panic buttons, maps, alarms, camera feeds, access-control systems, and multiple responding agencies.

So the real question becomes:

Are we transferring the call?

Or are we transferring the emergency?

In this episode of TiPS: Today in Public Safety, Fletch looks at one of the most important hidden tests of NG911 interoperability: whether the full emergency context can move with the incident as it crosses agencies, counties, states, networks, and vendor platforms.

That means voice, location, callback information, text, multimedia, crash data, alarm information, maps, notes, confidence levels, operational decisions, and audit trails all need to be treated as part of the public safety event package.

Legacy 911 was built in silos because that was the fastest and most practical way to get the job done. But as public safety moves into NG911, those same silos can become barriers to the shared awareness, continuity, and accountability that modern emergency response requires.

The promise of NG911 is not more dashboards, more portals, or faster silos.

The promise is shared context.

Trusted information.

Operational continuity.

And an emergency response system that finally starts acting like the interconnected system the public already assumes it is.

In legacy 911, we transferred the call.

In NG911, we have to transfer the emergency.