Checking technology from the customer's side
Test forms, signatures, messages, appointments and calls as a customer so technology changes address real service friction.

A customer experiences your technology through the task they’re trying to finish: asking a question, signing a document, booking time or getting an order update.
Test that task from their side before buying another tool. Try it on a phone, with only a keyboard and, if you can, with a screen reader.
1. Forms: make the request clear
Ask only for information needed for the task. Explain where the response goes and what happens after submission.
Test labels, validation, failed submissions and confirmation. Check whether staff receive the record and can follow up without asking the customer to repeat everything.
2. Signatures: verify the document process
An electronic signing tool can remove printing and scanning steps. Check that an e-signature is acceptable for the document first.
Provincial electronic commerce laws, such as Ontario’s Electronic Commerce Act, accept most electronic signatures but exclude some documents, including wills, powers of attorney and negotiable instruments. Get legal advice for anything unusual. A signing tool’s button doesn’t make every document valid.
Test delivery, signer identity checks, final-copy access and retention.
3. Chat: provide a usable handoff
A chat tool needs maintained answers and an escalation route. Test unclear questions, unsupported requests and a customer asking for a person.
If AI is involved, define what it may answer and which actions require human approval. Tell customers when a person will reply, since a bot that answers at night doesn’t mean staff are there.
4. Notifications: respect the message’s purpose
Offer useful updates without exposing sensitive details on a lock screen. Test failed delivery and the customer’s choice of channel.
The CRTC’s CASL guidance covers commercial electronic messages, including commercial texts. Promotional texts need consent, sender identification and a working unsubscribe. Messages that only confirm an order or give factual updates about an existing account or service are exempt from the consent requirement, but they still need sender identification and an unsubscribe. Check each type of message against the guidance.
5. Mobile access: test the existing journey
Check whether the current website already handles the task well on a phone. A separate app adds installation, account and maintenance work.
Build an app only when it does something the website can’t and someone is ready to keep it updated. Wrapping a hard-to-use website in an app leaves it just as hard to use.
6. Kiosks: include privacy and assistance
A public kiosk needs accessible controls, an alternative assistance route and a way to clear the previous person’s session.
Test placement, viewing privacy, timeouts and failure behaviour. Make sure the next visitor can’t see the last person’s details.
7. Calls: follow the caller’s route
Call from outside the organization and try the main options, busy periods and after-hours message. Check transfers, voicemail and the route to a person.
For a VoIP change, ask the provider what happens to calls when the internet is down, and check how 911 calls work, including the address on file for each phone. The business communications service covers the wider setup.
Choose a change from the findings
Record where customers get stuck and how staff resolve it today. Pick one improvement, name the person responsible and decide how you’ll know it worked.
Measure completed tasks and support effort after the change. Use that evidence to decide the next step.


