How to write intake questions that work on the phone
Write each question the way you would ask it out loud. Ask why they are calling first, keep choice lists to five or fewer, use short answers for names and numbers, and let the phone assistant read back phone numbers, emails and addresses so the caller can correct them.
Ask it the way you would say it
A web form can lean on layout: a heading, a hint, a row of boxes. A call has only words. Write the question the way a good receptionist would ask it, and keep the hint for detail that helps on screen.
Callers want to explain first. Put the reason for the call at the start; names and numbers come easier once they feel heard.
Pick the right kind of answer
- Short answer: names, unit numbers, anything said in one breath.
- Long answer: what happened. It is read back so the caller can correct it, so keep the question short and specific.
- Phone number: confirmed digit by digit. Never use a plain number field for it.
- Email: spelled back on a call.
- Address: the street and city are confirmed back to the caller.
- Choice: read aloud, so five options or fewer.
- Pick several: the assistant keeps asking “anything else?” until they say no.
Explain what each choice means
People rarely say the exact words of an option. A short note on what each answer means (“Power outage: several lights and outlets have lost power”) lets the assistant pick the right one from everyday language instead of reading the list.
Ask follow-ups only when they apply
A clogged sink does not need questions about the water heater. Show a follow-up only after the answer that calls for it, and the call stays short for everyone else.
Test it as a call
Before you go live, run the form as a phone call and listen for questions that sound like a form being read aloud. Reword those first.