Make the opening easy to understand
Use a short greeting that names the business and invites the caller to explain what they need. Avoid a long menu of services, promotions and instructions before they can speak. Be honest about the automated service and answer directly if asked whether it is AI. The opening should not require the caller to memorise several choices. Listen to it on an ordinary mobile speaker in a noisy room as well as through headphones. A voice that sounds clear in a demo may be harder to follow over a real phone connection.
Ask for one piece of information at a time
A question asking for a name, number, address and preferred appointment time can be difficult to remember and answer. Collect the minimum detail needed for the current step, then move on. Use everyday wording and explain unfamiliar terms only when relevant. If the caller has already supplied a detail, retain it instead of asking again. Let them correct a mistake without restarting the entire conversation. Design the order around their task, such as leaving a message, rather than the order of fields in your internal database.
Put a limit on repeated questions
When a detail is unclear, ask a short clarification and explain what is missing. If it remains unclear after a second attempt, offer another route rather than repeating the same question indefinitely. That route might be a human transfer, callback request or a contact page the caller chooses to use. Do not assume everyone can switch to a smartphone or email during a call. Preserve the parts already understood and tell the next person where help is needed. The fallback should reduce effort for the caller, not simply move the same confusing script elsewhere.
Confirm details without taking control away
Repeat critical details such as a callback number or appointment time at a pace the caller can check. Ask whether the information is correct and allow a focused correction. Read a phone number in manageable groups instead of as a large number. For dates, include the day and date where helpful. Avoid interpreting silence as agreement. If the caller changes their mind, acknowledge the change and explain the next step. The purpose of confirmation is to catch errors, not to make the person agree with information the system guessed.
Test interruptions and different speaking styles
Include callers who pause, speak slowly, interrupt, use an unfamiliar name or answer a question indirectly. Check whether the system cuts them off or starts talking during a pause. Test background noise and a weak connection. Use consenting participants and fictional details for these exercises. Record concrete observations, such as "asked for the number again after it was corrected," rather than judging a person as a difficult caller. Work with the provider on the behaviour you observed, then repeat the same scenario to confirm whether the change actually helped.
Keep alternatives visible and measurable
Publish a working contact option alongside the phone number and ensure staff know how to handle requests that arrive through it. During calls, provide a human route when available and an honest explanation when nobody is available. Review repeated clarification, abandoned conversations and fallback requests for possible usability issues, without assuming any one metric identifies a disability. A caller asking for a person is a valid preference. Use their feedback to shorten confusing steps and improve recovery. Accessibility work continues after launch because real conversations reveal needs that a scripted demo will miss.