TTY Agent

An on-premises AI appliance for answering TTY/TDD calls without sending call audio, transcripts, or AI inference to a third-party cloud.

TTY Agent registers to your PBX as a SIP endpoint, decodes Baudot tones into text, answers routine questions with a local AI assistant, and routes complex calls to a browser-based human queue on the same call path.

Talk with Tenacity about TTY Agent

Built for low-volume, high-stakes TTY readiness

Answers TTY/TDD calls and converts Baudot tones into text over the same call leg.

Keeps call audio, transcripts, knowledge-base content, and inference inside the customer's environment.

Uses a bundled local model and approved knowledge-base content for routine public answers.

Routes HUMAN, ACCOUNT, BILLING, REFUND, and similar requests into a browser queue.

Works as a standards-based SIP/RTP endpoint for Cisco, Genesys, Avaya, Five9, NICE, Asterisk, and similar systems.

Built to meet ADA, Section 508, and NG911 requirements without a cloud AI dependency.

How the call flows

Step 1

PBX routes the call

A TTY/TDD call reaches the customer's voice network and is routed to the TTY Agent SIP endpoint.

Step 2

Baudot becomes text

The appliance answers the call and decodes inbound Baudot FSK over the audio leg into readable text turns.

Step 3

Local AI responds

A bundled local model uses approved knowledge-base content to answer routine public questions in TTY style.

Step 4

Human takes over

Private, billing, refund, or explicit human requests move into a browser queue without a PBX transfer.

AI handles routine calls. Staff handle the exceptions.

The PBX sees one continuous SIP call.

When the caller asks for a person or uses account-specific terms, TTY Agent transmits a TTY hold message, suppresses AI replies, and places the live call in a browser queue. Staff can take the call, type a reply, and release it back to AI when appropriate.

Human escalation queue shown on a browser workstation

Appliance architecture

Deployed beside your PBX

TTY Agent appliance connected to PBX, TTY endpoint, local AI, and knowledge base systems

Claim boundary

Designed for regulated teams, with pilot proof still required

The product architecture supports privacy-sensitive pilots: local model inference, customer-controlled knowledge-base content, optional transcript logging, HTTPS admin access, and TLS/SRTP configuration when the customer PBX is ready for certificate exchange.

TTY Agent is designed to be fully ADA, Section 508, and NG911 compliant at deployment. HIPAA, PCI, and procurement acceptance still depend on the customer's deployment, policies, validation evidence, and legal review.