Skip to content

Voice Conversation

Why Spoken Answers Are Shorter

Listening is not reading. Why a website assistant should answer a call in a few sentences, offer more, and leave the details on the screen for the visitor.

Updated 19 Nov 2026

A good written answer and a good spoken answer are not the same thing.

Listening is not reading

A reader skims, jumps back and picks out the line they need. A listener cannot: every sentence costs the same time, in the order it is said. A written answer of ten lines takes half a minute to read aloud, and the part the visitor wanted may come last.

Write for the ear

A spoken answer works best when it:

  • Leads with the answer. The essential point comes first.
  • Stays short. Two or three sentences, then an offer to say more.
  • Avoids lists and symbols. A bullet list or a table does not survive being read aloud.
  • Says less to a greeting. "Hello" deserves a short hello, not an introduction and a menu.

Let the screen do the rest

A voice call on a website has something a phone call does not: a screen. Prices, a booking picker or a contact button can appear while the voice says, in one line, that there is something to look at. The visitor hears the essentials and keeps the details.

Choosing the length

Some organisations prefer fuller spoken answers. A setting for answer length lets them choose between short and medium, while the ear's limits still apply. See Call Experience.