Philippines staffing blog ·
Record a customer accessibility preference at first contact
A practical intake step that captures how a customer needs to receive support without turning a reasonable adjustment into a permanent assumption.

Direct answer
Operational guidance
Why accessibility needs its own intake field
A customer may need a larger font, a phone call instead of a portal reply, or extra time to finish a step. If the desk learns that only after three failed attempts, the delay looks like a queue problem when it is an intake gap. Recording the preference at first contact gives the next agent a usable starting point. It also stops the customer from repeating the same explanation to every shift. A short field costs far less than a failed contact and a repeated explanation.
The preference is not a medical label and should never become one. Record only the practical adjustment the customer asked for and the channel where it applies. A note that says the customer prefers a phone call is useful, while a note that speculates about a diagnosis is unnecessary and risky. Keep the wording factual, attached to the ticket, and easy for the customer to change later. The customer should be able to withdraw the preference as easily as they gave it.
Ask one clear question at intake
Add one short optional question to the intake form instead of a long accessibility questionnaire. Ask whether a format, channel, or pace would make support easier to use. Offer examples such as a phone callback, a plain-language summary, or a larger attachment. Make clear that the answer is optional and that the customer can update it at any time. Keep the question visible on the form instead of hiding it behind a help link.
When the customer answers, repeat the request back in one sentence before acting on it. Confirm the channel, the time window, and any limit the customer named. If the preference conflicts with a security control, explain the constraint and offer the closest safe alternative. Record both the request and the alternative so the next agent does not reopen the same negotiation. The agreed handling should be written in the same plain language the customer used.
Separate a preference from a requirement
Some adjustments are preferences, while others are conditions the customer needs in order to use the service at all. A plain-language summary is usually a preference, but a screen-reader-compatible document may be a requirement. The agent should not settle that question alone when the consequence is access to a protected service. Escalate the classification to the owner and record the interim option offered. The distinction matters most when the request touches an account or a payment.
Use two fields rather than one, one for the requested adjustment and one for the confirmed handling. The first records what the customer asked for, and the second records what the desk agreed to do. A blank second field means the request is still open, not that the customer has no needs. This distinction keeps a note from closing a conversation that never reached agreement. A reviewer should be able to tell the two fields apart without opening the thread.
Where the preference gets lost
Preferences disappear when the ticket moves to a new queue or a new tool. The receiving agent sees the latest message but not the intake answer that made the exchange work. Copy the confirmed handling into the handoff summary and name the channel it applies to. Check that the destination system shows the same field before releasing the ticket. A preference that lives only in the latest message will be rediscovered by every owner.
A preference can also expire or change after a product update. If the customer says the callback no longer reaches them, update the record instead of assuming the old note is still right. Review preferences when a case reopens and when a customer reports a missed contact. A short refresh question protects the relationship better than a silent assumption. Ask again at the start of a new request type instead of copying the old answer.
A worked example
A customer asks for help resetting access to a billing portal and mentions that phone calls are difficult. The agent confirms a written step-by-step reply with a larger attachment and records the format, the channel, and the agreed follow-up time. Nobody labels the customer or guesses at a cause. The ticket now carries a usable instruction rather than a vague note about a difficult call. The customer does not have to explain the reason to receive a workable format.
Two shifts later, the ticket moves to a specialist who normally calls. The handoff summary shows the confirmed handling and the reason for it. The specialist sends the written update and keeps a callback as a backup only if the customer asks. The case closes without a failed call and without repeating the intake questions. No one has to guess whether the written update was approved or improvised.
What the manager decides
The manager decides which adjustments the desk can promise and which need a service owner. A written menu of supported formats stops each agent from improvising under pressure. The menu should name the channel, the expected turnaround, and the person who approves an exception. Review the menu whenever the tooling or the service catalogue changes. The menu should be short enough to read on a call and specific enough to audit.
The manager also owns the privacy boundary around the field. Decide who can see the preference, how long it is kept, and when it is removed. Access should follow the same least-privilege rule as other sensitive ticket data. A field that everyone can browse becomes a quiet privacy liability. Collect only the detail that changes how support is delivered to this customer.
Train the habit with two examples
Use one successful case and one failed case in the next team meeting. Ask agents to point to the exact field where the adjustment was captured and where it was lost. The discussion should stay on the record and the handoff, not on whether the customer was easy to serve. Two examples are enough to show the habit without turning the meeting into a policy lecture. The customer's confirmation is stronger evidence than the agent's closing sentence.
Add the check to the quality sample and look for closed tickets with no confirmed handling. Coach the pattern when the same gap appears twice and update the template after the second review. Keep the language neutral and the field optional. A consistent habit is more useful than a long form that customers skip. Repeat the field in the help article so customers know the option exists.
Close and review
Close the case only when the customer confirms the adjustment worked or the agreed alternative was delivered. Record the confirmation and the channel used, not just the agent's impression. Sample a few closed cases each week to see whether the preference was honored. A missed preference is a process defect worth fixing at the source. Ask the team to name the moment the adjustment would otherwise have been lost.
Update the intake form when the same adjustment is requested repeatedly. Add the wording to the help article and the saved reply library so the answer stays consistent. Keep the field optional and the language plain. The goal is a desk that adapts without making the customer prove the same need twice. The field should stay a support aid, not a label that follows the customer forever.
Authoritative sources
- W3C Web Content Accessibility Guidelines 2.2
- Section 508 accessibility program
- ISO 18295-1:2017 customer contact centres