112NG112.netNext generation emergency communications

NG112 reference

Emergency Text

Structured NG112 reference page.

112 readiness

Policy, location, routing, and response quality connected in one operational model.

Accessibility

Emergency Text

Some emergency text services are message-based, while RTT is conversational and character-by-character. Both can support accessibility, but they create different routing, timing, user-experience and PSAP workflow requirements.

Emergency text may be message-based; RTT is real-time conversational text.
Caller text channel
->
Emergency text service
->
PSAP or relay workflow

What it does

Emergency text covers text-based emergency access mechanisms and should be distinguished from Real-Time Text.

Emergency text provides non-voice access paths where supported by national emergency services.

How it works

  • May use national messaging, app, relay or IP session mechanisms.
  • Routes text to a PSAP or specialized handling service.
  • Requires clear public instructions about availability and limitations.

Key interfaces and protocols

  • RTT where used
  • Messaging/app interfaces
  • Relay services
  • PSAP text handling

Systems it interacts with

  • RTT
  • Accessibility
  • Emergency apps
  • PSAP
  • Recording

Common failure modes

  • Public assumes text works everywhere.
  • Message delivery latency is mistaken for live conversation.
  • Location is weaker than voice call location.
  • PSAP workflow is disconnected from voice call handling.

Implementation considerations

  • Tell the public when and how text is supported.
  • Keep location and callback workflows clear.
  • Do not blur message-based text and RTT in technical requirements.

Standards

  • European accessibility policy
  • ETSI NG112 references

Related NG112 technologies

Related country deployments

No country deployments are listed here until independently verified against official or high-confidence sources.

Related articles

Sources

Last verified: 2026-08-31

Advertisement