Skip to content

Conversational Real-Time Text

Show participants the unfinished text of an ongoing conversation in successive updates before its writer completes a message or line.

Version
v1 · 2026-10-25 · History
Domain-specific #
14374
Origin domain
Mediated Communication
Subdomains
Telecommunications, Online Group Chat → Mediated Communication
Aliases
Partial-text conversation, Live typing exchange

Core Idea

Conversational real-time text lets another participant read words while their writer is still composing them. The text appears in successive partial updates before a complete message or line. In a compatible T-Mobile RTT call, the other person can see text as it is typed; the Talkomatic implementer describes characters appearing before a full line was finished in an early group chat.[1][2]

This is about visible words, not merely knowing that somebody is typing. It gives readers an opportunity to answer an evolving utterance, but does not require them to interrupt or respond at any particular moment. Neither case establishes a universal millisecond limit, a common protocol, or guaranteed behavior for every device.

Structural Signature

Five roles define the process:

  1. Continuing conversation: other current participants can read and respond.
  2. Unfinished composition: a participant is still forming words or a line.
  3. Precompletion updates: characters or partial words reach others before the writer finishes. T-Mobile says text is visible while typed; Woolley says Talkomatic transmitted characters without waiting for a whole line.[1][2]
  4. Participant-side partial display: the other person's screen shows the changing words, rather than keeping them hidden until Send. Talkomatic used separate writer windows in a shared display.[2]
  5. Response opportunity: another participant can react before the writer completes the utterance. This is an affordance of early display, not a reported rate of actual replies.

If a server receives each keystroke but the interlocutor sees nothing until submission, the fourth role is missing. If only a typing indicator appears, the reader sees activity rather than the unfinished text.

Scope of Application

Supported mobile RTT call: T-Mobile describes RTT between compatible users on supported VoLTE or Wi-Fi calls; simultaneous voice and text are available where the service and devices support them.[1] Its description is a first-party account of an offered feature, not a measured trace of one named call.

Historical group chat: Woolley's later first-person account says Talkomatic showed characters as typed in separate windows for several simultaneous writers.[2] Hody's 1974 PLATO user report separately corroborates an operating shared display with five participants; it does not document the character-level mechanics.[3]

The call and the group channel differ in participant number, transport and interface. Both fit because another participant can see actual unfinished words. The cited BT Relay UK service is a held neighbor: its operator note describes mediated text and voice, but does not show whether an assistant saw unfinished text before a submit or turn boundary.[4]

Clarity

Ask what the other person sees before a message is complete. A fast ordinary message appears soon after Send. A typing indicator reveals that somebody is composing. Conversational real-time text reveals the unfinished characters or words themselves. The current Instant Messaging entry describes a network message-turn service. Talkomatic's group chat can overlap that service and this real-time-text process.[2] T-Mobile instead describes an answered and ended RTT call, without establishing that an instant-messaging service organizes every such call.[1]

In a direct RTT call the partial text reaches another compatible endpoint; in Talkomatic, several writers could keep their contributions distinguishable in separate screen regions.[1][2] The window arrangement belongs to Talkomatic, not to every instance of this abstraction.

Manages Complexity

The five roles locate where a purported real-time-text service differs. Is there an active conversation? Is actual unfinished content sent? Does the other participant see it before completion? Can that participant reply while composition continues? A system can move bytes quickly yet fail this test by withholding display until a complete message.

The roles also prevent a mistaken protocol inference. T-Mobile's mobile-call feature and Talkomatic's PLATO channel are unlike implementations; the sources establish shared interaction behavior, not a shared packet format or quantified delay.

Abstract Reasoning

Consider the prefix of text a writer has produced and the prefix another participant can see. If the visible prefix changes before the writer finishes a conventional line or message, the defining early-exposure relation is present. Changing an unfinished update in a functioning system changes what can be read at that moment; this is a diagnostic causal model of the described behavior, not a measured trial of every compatible call.

Waiting until Send lets a writer privately revise more text, but removes the precompletion display relation. Revealing partial words enables an early response while also exposing provisional spelling and wording. The source accounts establish the early visibility; the social trade-off is analysis, not a measured outcome in either report.

Knowledge Transfer

The same five questions work for both cases despite their different interfaces: who is conversing, what is unfinished, how do updates travel, what does the reader see, and can the reader answer before completion? The phone feature may combine voice and text; Talkomatic's group channel let multiple writers type in separate windows.[1][2] Neither implementation detail is mandatory for the shared identity.

Outside conversation, a collaborative editor can also expose unfinished text, but that resemblance alone does not make it an addressed conversational exchange. Live caption text represents an audiovisual program interval rather than one participant's unfinished utterance to interlocutors.

This entry includes Coupling.

Coupling is an internal part of the staged mechanism. A newly emitted unfinished update changes another participant's visible prefix before completion in a functioning supported session; withholding it leaves that content absent.[1][2] The contrast is a curatorial inference from the described behavior, not a measured intervention. Flow and Concurrency are related comparisons, but their full signatures are not necessary across both cases. The Coupling edge still awaits post-edit and physical graph review before canonical release.

Relationships to Other Abstractions

Local relationship map for Conversational Real-Time TextParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.ConversationalReal-Time TextDOMAINPrime abstraction: Coupling — includesCouplingPRIME

Current abstraction Conversational Real-Time Text Domain-specific

Parents (1) — outgoing typed relations

  • Conversational Real-Time Text includes Coupling Prime

    Precompletion changes in a writer's text affect another participant's visible partial words, a directed Coupling constituent of conversational real-time text.

Hierarchy path (1) — routes to 1 parentless root

  • Conversational Real-Time Text → includes Coupling

Neighborhood in Abstraction Space

Conversational Real-Time Text sits in a moderately populated region (59th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Language, Mind & Meaning-Making (69 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With

  • Instant Messaging: see the current service entry. Talkomatic's group channel can overlap its message-turn pattern, while IM need not expose unfinished words.[2] T-Mobile describes an answered RTT call and as-typed text, without establishing that an IM service is necessary for every such call.[1]

  • Typing indicators: show that composing is happening without displaying the words.

  • Live Timed Caption Delivery: creates and times captions for an audiovisual program, not participant-to-participant utterances.

  • Text relay: the consulted Relay UK note does not establish the partial-word display needed for a positive case.[4]

References

[1] T-Mobile, “T-Mobile accessibility”, Real-Time Text (RTT) section, consulted 22 October 2026. First-party operator description of compatibility-limited direct RTT service, text visible while typed, and simultaneous voice/text where supported; no quantitative performance or protocol trace. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h

[2] David R. Woolley, “PLATO: The Emergence of On-Line Community”, 1994, “Talkomatic and Term-Talk” section. First-person retrospective account of character updates before line completion and multiwriter window design. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i

[3] G. L. Hody, “PLATO IV: A User's Overview”, 1974 ADCIS presentation, zero-based PDF pp. 6–7. Contemporary report corroborating an operating shared Talkomatic display; does not itself establish character-level transmission. registry ↩

[4] British Telecommunications plc, “Relay UK Service Description”, Suppliers' Information Note 359, issue 1.11, October 2023, pp. 2–5. Operator description of mediated text and voice; unfinished-text visibility before submission is not established. registry ↩a ↩b