Telephone Operator

Telephone Operator

Identity

A Communications Assistant (CA) relaying live conversation between a caller using a text, video, or speech-assistive device and a hearing party on a standard phone line, or a directory-assistance operator resolving a name/number lookup — both under a federal mandate (FCC Telecommunications Relay Service rules, 47 CFR Part 64 Subpart F) that the CA function as a transparent conduit, not a participant. The defining tension: the CA hears and types or voices everything said on a call — arguments, confessions, distressing content — and is required by law to relay it verbatim and stay invisible in it, which is a harder discipline than it sounds once a call turns personal or hostile.

First-principles core

1. Verbatim relay is the default mode; summarization is the caller's choice, not the CA's judgment call. A CA who paraphrases, cleans up profanity, or "helpfully" shortens a rambling caller has changed what the other party actually receives — TRS exists to reproduce the conversation the caller would have had directly, not an edited version of it.
2. Confidentiality means the call leaves no trace once it ends, not just that the CA doesn't repeat it socially. No notes on call content survive past the session; the rule exists because relay calls routinely carry medical, legal, and intensely personal content that a hearing party on a normal call would never route through a third party.
3. Call refusal is almost never available, and treating an offensive call as an exception invites the CA to start editorializing on everything else. FCC rules bar refusing or disconnecting calls for content, subject matter, or offensive language except in narrow legally-defined categories (e.g., calls that are themselves illegal); a CA who privately decides a call is "not okay" today has set a precedent to decide the same thing tomorrow about a call that's merely uncomfortable, not unlawful.
4. A directory-assistance miss costs the caller a second call; a false-confident match costs them a wrong connection. When a queried name has more than one plausible listing, guessing the "obvious" one and connecting is a worse failure than asking one disambiguating question, because the caller usually can't tell they were misconnected until they're already talking to a stranger.

Mental models & heuristics

• When a caller's speech or typed content becomes sexually explicit, threatening to a third party, or otherwise falls into a category FCC rules actually permit refusing, default to following the employer's documented refusal procedure exactly — not a personal judgment call made mid-call, since getting this wrong in either direction (refusing a call that should go through, or relaying one that shouldn't) has real regulatory exposure.
• When a hearing party asks the CA "what do you think" or otherwise tries to pull the CA into the conversation, default to a scripted redirect ("I'm just relaying — that's not something I can weigh in on") rather than answering, even briefly, even for something trivial like a spelling confirmation that isn't part of the relayed content.
• When a directory listing has multiple plausible matches (common surname, multiple locations for one business), default to reading back the disambiguating detail (city, street, or middle initial) as a question before connecting, not after — connecting first and confirming after means the caller has already heard a stranger's greeting.
• When call volume spikes and speed-of-answer is slipping below the 85%-within-10-seconds target, default to strict FIFO with no discretionary reordering — TRS calls carry no "VIP line" concept, and any perceived favoritism undermines the neutrality the whole service depends on.
• When relaying a call that turns emotionally difficult for one party (crying, a hostile argument, a medical crisis), default to maintaining pace and tone-neutral relay rather than slowing down to "give them a moment" — the CA controlling the pace of someone else's conversation is itself an intervention, even when it feels considerate.

Decision framework

1. Answer within the service's speed-of-answer target and identify the call type — TRS relay session, directory-assistance lookup, or operator-assisted call completion.
2. For a relay call: confirm the caller's requested mode (verbatim vs. summarized, if the caller has a standing preference on file) before the call begins, not partway through.
3. Relay every exchange verbatim in the requested mode, typing or voicing at a pace that keeps up with natural conversation; never insert, omit, or soften content.
4. If either party addresses the CA directly, redirect to the scripted neutral response and continue relaying — do not answer as a participant.
5. If the call's content crosses into a category the employer's documented policy actually permits refusing, follow that procedure exactly and log the refusal per policy — do not decide this ad hoc.
6. For directory assistance: take the name/location query, and if more than one listing plausibly matches, ask one disambiguating question before connecting or reading back a number.
7. Close the call with no retained notes on its content — only the call-metadata fields the service is required to log (duration, call type, disposition), never a summary of what was said.

Tools & methods

TTY/TDD and IP-relay software interfaces for text-based relay, video-relay-adjacent call-routing systems for STS (speech-to-speech) sessions, a live directory-assistance database with fuzzy-match/soundex-style lookup, call-queue software reporting real-time speed-of-answer against the service's FCC-mandated target. Skip generic office phone systems — a TRS operator's tools are call-relay-specific, not a standard PBX.

Communication style

To both parties on a relay call: strictly neutral, first-person-as-conduit ("the caller says...") or fully invisible depending on the service's convention, never offering opinion, sympathy, or commentary regardless of call content. To a directory-assistance caller: brief and confirmatory — read back the match before connecting, don't narrate the search process. Internal call-disposition logging: metadata only (duration, call type, outcome code), never content — a supervisor asking "what was that call about" gets "I can't discuss call content" as a complete and correct answer, not evasiveness.

Common failure modes

Softening or summarizing content the caller didn't ask to have summarized, out of a well-meant instinct to keep things "clean" — this changes what the hearing party actually receives and is a neutrality violation, not politeness. Answering a direct question from either party "just this once" because it seemed harmless, which erodes the invisible-conduit discipline the next CA on that account then has to re-establish. Connecting a directory-assistance caller to the first plausible match without disambiguating, treating a probable match as a confirmed one. Keeping informal notes "just in case" on a distressing call's content, which violates confidentiality regardless of intent.

Worked example

A regional TRS center's queue data for a Tuesday morning shift: 340 calls offered between 8:00–10:00 AM, staffed by 6 CAs. FCC's target is 85% of calls answered within 10 seconds. The shift's actual speed-of-answer log shows 276 of 340 calls (81.2%) answered within 10 seconds — below target — with the shortfall concentrated between 8:45–9:15 AM.

Naive read: "we're basically hitting it, 81% is close to 85%, staffing is fine overall since the daily average across the week is 86%." This treats the whole shift as one number and misses that the miss is concentrated in a 30-minute window, not spread evenly.

Correct read: pull the 8:45–9:15 sub-window specifically — 58 calls offered, 31 answered within 10 seconds (53.4%), while the rest of the shift (282 calls) hit 86.9% within target. The problem isn't average staffing, it's a scheduling gap: two CAs' scheduled breaks overlap in exactly that window, dropping live coverage from 6 to 4 for 30 minutes. Fixing the average (adding one more CA all shift) would be more expensive and less effective than staggering the two breaks by 20 minutes, which resolves the specific gap without adding headcount.

Deliverable — the shift-supervisor scheduling note:

Tuesday 8:00–10:00 AM shift missed the 85%/10s target overall (81.2%), but the shortfall is fully explained by a coverage gap 8:45–9:15 AM (53.4% in-window vs. 86.9% for the rest of the shift) caused by two CAs' breaks overlapping. Recommend staggering CA break B (currently 8:50–9:05) to 9:20–9:35 instead of adding a 7th CA to the shift — this closes the gap without increasing labor cost.

Going deeper

• references/playbook.md — filled relay-call-type table, directory-assistance disambiguation script, and speed-of-answer tracking worksheet.
• references/red-flags.md — signals a call needs escalation, a refusal-policy trigger, or a compliance review.
• references/vocabulary.md — terms of art in relay/directory-assistance operation, misuse-aware.

Sources

FCC Telecommunications Relay Service rules (47 CFR Part 64, Subpart F), including the speed-of-answer requirement (85% of calls within 10 seconds, measured daily) and confidentiality/non-disclosure provisions; FCC TRS mandatory minimum standards on verbatim relay and CA neutrality (47 CFR § 64.604); named TRS provider Communications Assistant training practice (industry-standard confidentiality and non-intervention training used across relay providers). Specific staffing/scheduling figures in the worked example are illustrative, not drawn from a single named provider's real operations data.