Resources / Accessible communication

Offer spelling choices without making assumptions

Help callers communicate a permitted name field in a way they can manage.

01

The operational decision

Help callers communicate a permitted name field in a way they can manage. Intake communication should make the available choices understandable without requiring a particular reading style, device or input method. Operational accessibility work can be tested with fictional inquiries and public information.

02

Prepare the workflow

Allow ordinary spelling or a slower repetition and avoid requiring a particular phonetic alphabet; keep the final confirmation neutral.

03

Example wording for approval

“You can spell the example name slowly or repeat it another way. I will confirm the letters you provide before the request goes to staff.”

04

Worked example

A fictional caller does not use a phonetic alphabet and wants to spell a name slowly. The assistant should accept ordinary letters, pause and confirm the supplied sequence. It should not insist on a particular alphabet or replace an unfamiliar spelling with a common name. Test a correction near the end of the word so a partial update becomes visible. The staff record should contain the corrected permitted field, with uncertainty retained if the spelling could not be confirmed.

05

Handoff record

Record these task-specific fields: field label, supplied spelling, correction option, reviewer.

06

Acceptance check

Use an unfamiliar fictional name and a correction. The assistant should accept the correction without substituting a more familiar name.

Legal intake capacity calculator ↗

Try Ava with your business’s public information ↗

Related guides

Your workflow, first

Let’s map your first week.

Bring the calls you want covered. We’ll agree the script, handoff and limits.

Start a pilot