Foundations · Explore this field ↗ · Design · 2 min read
The channel is part of the system
Web chat, email, voice, messaging, and kiosks change what good behavior means.
Channel constraints are product requirements
Chat supports scanning, links, copy-and-paste, and asynchronous pauses. Voice is faster for expression but harder for reviewing numbers, citations, and choices. Email tolerates delay and longer context but can hide turn boundaries. A kiosk may have shared-device privacy and time pressure. A messaging platform may constrain buttons, identity, attachments, and retention. The core policy can be shared; the interaction cannot simply be ported.
Design the repair behavior first
In voice, interruption and recognition errors dominate. In chat, users may send fragments or several messages before the bot replies. In email, quoted threads and signatures pollute context. Define how the system asks for repetition, joins rapid messages, and signals that a request is still processing. Preserve a stable case identifier across channels so a handoff does not become a restart.
Keep commitments consistent
Channel-specific language must not change service rights. If human help is available on the website but not in the messaging channel, say so before the user invests time. Do not present teammate avatars or reply-time promises when no teammate can receive the conversation. The interface is part of the disclosure.
Operator note
Run the same ten user goals through every proposed channel. Record input limits, authentication strength, accessible alternatives, latency, transcript visibility, file handling, and handoff. Launch the smallest channel set that operations can actually support.
Channel review in practice
Take one cancellation request and prototype it in web chat, voice, email, and a shared kiosk. In chat, inspect link and transcript behavior. In voice, test noisy input, number read-back, and interruption. In email, test quoted history and delayed replies. At the kiosk, test shoulder-surfing, session clearing, and an abandoned flow. The goal is not channel parity at any cost. It is an honest service contract in each surface, including an equivalent path when one modality cannot safely support the task.
Primary reading
Sources and limits
These links support the architecture, policy, or product behavior discussed above. Vendor documentation describes vendor features; it is not independent proof of performance. Current details should be rechecked before a production decision.