What the contact page is for
The support channels and self-service guide chooses which channels a business offers, runs the help centre as a product and sets a standard for each channel. It asks for the email and form standard to be published where customers write in, wants chat hours shown with an alternative outside them, and counts hiding the way to a person among its mistakes. What it does not design is the page those routes sit on. Several other guides send something there too, from the customer version of a complaints procedure to a line about a current problem, and none of them says how the whole page should be put together.
The page has one job: to get each customer from the problem they arrived with to the help that will solve it, with as little guessing as possible. That means answering the questions it can answer, pointing everything else to the route that suits it and telling the customer how long each route will take. The guide to reducing customer effort lists contact forms and finding answers among the kinds of effort a business moves onto its customers. A page that holds nothing but a blank form and a number adds both: the customer looks for an answer that is not there, types out the whole problem in a single box and then waits without knowing for how long.
The page also sets an expectation. The expectation-disconfirmation model treats satisfaction as a comparison: what happened, set against what the customer had expected beforehand. A stated reply time that the team keeps gives the customer something firm to judge the wait against. A page that states nothing leaves the customer to supply the expectation, and the business has no say in what they assume.
This tutorial covers the help and contact page for people who have already bought or booked, and the routes it leads to. Lead and enquiry forms for prospects belong to the forms and pre-purchase guides linked in the steps. How the help centre is structured and found in search is the subject of the help centre and documentation SEO guide. The page describes no chat, help desk or telephony product and no phone menu set-up, and it states no legal requirement about the contact details a business must publish in any country; those are questions for the business and its advisers.
Before you start
- Tag a sample of recent contacts by reason. The tutorial that tags support contacts by reason drafts the reason list from real contacts, named in the customer's own words. If the list already exists, pull a recent period of counts by reason and by channel.
- List every route customers use today. Phone, email, the form, chat, messaging apps, social messages and any counter or site visit, with who answers each, when it is staffed and the reply standard it works to, if it has one.
- Find every place that links to the current page. The site header and footer, order and booking confirmations, account pages, help articles, error pages and service messages.
- Collect what other processes want on the page. The customer version of the complaints procedure, any notice about a current problem, the route for customers who need the process adapted, and the hours for each market if the business serves more than one.
- Bring the right people together. The support lead, whoever owns the website and someone who can test the page with a keyboard and a screen reader.
The steps
List why customers get in touch and rank the reasons
Start from the Contact ReasonThe main reason a customer contacted support, tagged by the agent from a fixed, defined list so volume and other service metrics can be read by cause. counts, not from the current page. Put every reason in a single list across all channels and sort it from the largest count to the smallest, with a running total beside it. The Pareto principle is the reason for the ranking and also a warning about it: value can be concentrated in a few items, but how concentrated it is in a given list has to be found by ranking it, not assumed from a rule of thumb. Note the point where the running total stops rising quickly and levels off.
Mark the reasons near the top as the ones the page must answer. Then mark, separately, the reasons that need a person every time whatever their count: a complaint, damage, a safety worry, something going wrong on the day of a delivery or visit. Those are not answered on the page; they are routed. Keep the customer's wording for every reason, because those words become the headings on the page.
Put the answer to each top reason on the page or one step away
For each top reason, decide what the customer needs to sort it out. Some need a sentence on the page. Others need a link that takes them directly to where they can fix it themselves, such as the page where a booking is moved or an order is tracked. Others need the help article that explains it. Write each as a short heading in the customer's words with the answer or the link directly beneath.
Placement matters because people scan. The guide to writing for the web, drawing on Nielsen Norman Group's research into how people read online, describes readers jumping through a page for the thing they came for and moving on once they have it, or once they conclude it is not there. Put the answers at the top in a list the eye can run down, not inside paragraphs.
A question about ending a plan gets the route itself. The guide to designing the cancellation experience asks for the answer to "how do I cancel" to link to the same cancel route as the account settings and the help centre, so the contact page does the same rather than sending the customer to a form.
The answers sit beside the routes to a person, not in front of them. Counting DeflectionThe share of customer contacts handled without ever reaching a person, usually by an assistant or help content; read beside resolution, never as the goal. as a win treats a customer who found the answer and a customer who gave up as the same result, and the site's service guides decline to make it the goal. The answers are there to spare the customer a wait, never to keep them from a person.
Show every route with its hours and reply time
Below the answers, list every route the business staffs. For each, say what it suits, when it is answered and what the customer can expect: a phone line with its hours, a written route with the reply time the team works to, chat with the hours it is staffed. The support channels guide matches channels to the kinds of question they handle well, so a line such as "for a problem with a visit today, call" or "for anything with photos, use the form" helps the customer choose.
Show chat only when someone is there to answer it, and outside its hours say so and point to the route that is open. Every reply time and every set of hours on the page is a promise, so set them from what the team keeps on a normal week, not from what it would like to keep. Together those hours and reply times are the business's response standardA written commitment about which customer and audience messages get answered, how fast, by whom and how, set per message type and channel. as customers see it. Where customers live in other time zones, the guide to support across languages and time zones sets out what each market's version of the page states, and that guide is the place to plan it.
Give urgent and sensitive problems their own route
Decide what counts as urgent for this business and write it down: something unsafe, a problem on the day of a service, money taken in error, an account someone else has got into. Give those problems a route that is answered quickly, shown near the top of the page with a plain description of what it is for, and backed by an Escalation RouteA short written route naming who front-line staff contact, how and how fast, when a problem is beyond what they can decide alone. inside the team, so the person who picks up knows who decides and how to reach them.
Complaints get their own line too. The tutorial on writing a complaints procedure writes a short customer version of the procedure, covering how to complain, the channels it accepts, the next steps, when to expect a response and the route upward for anyone still unhappy, and places that version on the contact page. Give it a heading that uses the word "complaint", so a customer who wants to complain can see that the business expects them to. When the staff version of the complaints procedureThe written process for complaints: what counts as one, how every channel feeds one log, the response promised, who decides and how customers escalate. changes its promises or stages, the line on the contact page changes with it.
Some customers need the process itself to change. The guide to supporting customers in vulnerable circumstances gives a relative who contacts the business after a death a single route and a single contact person, and lets customers choose the channel and format that work for them. Give that route a line of its own, worded gently, such as "if you are contacting us about someone who has died, or you need us to do things differently", so nobody has to explain their situation to a general queue first.
Build the form around the reason list
Start the form with the reason. Offer a short list in the same customer words as the tags agents use, with an option for anything else, so the contact arrives already sorted and can be routed without an agent reading it first. Where a reason has an answer on the page, show it beside the choice, and let the customer send the form anyway.
Then ask only for what the reply needs: a name, a way to reply, the order or booking reference where the reason involves one, and the message. The forms guide starts from Nielsen Norman Group's research on form usability and sets out its own rules: keep the form short, put fields in a logical order, keep labels visible above the fields, and make error messages say what went wrong and how to put it right, next to the field concerned, without clearing what the customer typed. Add an optional attachment only for the reasons that need one, such as a photo of damage.
Give people who have not bought yet a reason of their own. The guide to answering pre-purchase questions warns that buyers' questions and complaints both suffer when they share agents in a single queue with no way to separate them, and it sets out who should answer each kind of buyer's question.
Say what happens after the customer presses send
When the form is sent, the screen confirms it and a message follows to the address the customer gave. Both carry a reference, the time by which a person will reply, what to do if the problem becomes urgent in the meantime, and the links to the answers for the top reasons. Write it as a plain statement of what happens next, not a thank-you with no detail.
This acknowledgement is not a reply. It tells the customer how long they will wait; it does not answer them, and the team should not count it as an answer when it measures how quickly customers hear back. If the reply time changes, for instance during a busy week, change the acknowledgement on the same day so the promise stays true. When the queue behind the page has grown well past the reply time it states, the tutorial on clearing a support backlog deals with the customers already in the queue while the page tells new ones the honest wait.
Keep a person reachable from every route
Every answer on the page, every help article it links to, every chatbot and every form ends with a visible way to reach a person. The support channels guide asks for more than one route to a person, a written one and a spoken one, because some customers cannot use the phone and others cannot easily type. Check that each route on the page leads somewhere a person reads, that nothing loops the customer back to the help centre, and that a customer who arrives outside the hours of every live channel still finds a written route with a stated reply time.
Link the page from where questions arise
Customers look for help from wherever they are when the problem appears. Link the page from the site header and footer, from order and booking confirmations, from account pages, from the foot of every help article and from error pages. Where a confirmation or a service message is about a specific order or booking, link to the part of the page that covers it, so the customer lands on the answer rather than the top.
Keep a slot near the top of the page for a current problem. The guide to proactive service messages puts a short line about a disruption on the contact page and describes a status line: one place, dated and kept up to date, naming what is affected, the action customers should take and the time of the next update. When nothing is wrong, the slot stays empty.
Test it with a keyboard, a screen reader and a phone
The support channels guide applies WCAGThe W3C's Web Content Accessibility Guidelines, the widely used standard for making web content usable by people with disabilities. to contact forms and chat as much as to any other page, under the four principles of being perceivable, operable, understandable and robust. Test the page in practice. Move through the whole page and the form with the keyboard alone, and check that the order makes sense and the focus is visible. Use a screen reader to check that every field has its label read out, that the reason list can be chosen, that errors are announced and that the chat window can be opened, used and closed. Check that nothing relies on colour alone and that the form does not expire while someone is still typing.
Then open the page on a phone. The answers should come first, the routes should be readable without zooming, a phone number should start a call when tapped, and the form should fit the screen with the right keyboard for each field. Where possible, watch a customer who uses assistive technology try the page, because they will find things a checklist misses.
Measure where the page sends people and review it
Judge the page by whether people reach the right help, not by how few get in touch. The guide to customer service metrics defines Contact RateSupport contacts in a period divided by orders, active customers or bookings in the same period, showing how often customers need help. as contacts per order, active customer or booking, and names making it harder to get in touch as the way that number is gamed. Read the rate beside complaints and reviews about getting help and beside repeat contacts, the pair that guide sets against it, so a fall caused by a harder page shows up as the worse service it is.
Read four further things from your own records. Which route contacts arrive through, by reason, and whether each reason reaches the route that suits it. Whether the reason customers chose on the form matches the reason agents record at the end. Whether customers still get in touch after viewing an answer on the page, which shows an answer that does not work. And whether the hours and reply times on the page held true in practice. Give the page an owner and a review date, review it with the reason list on a fixed cycle, change the answers when the ranking changes, and change the hours and reply times on the day they change.
What the page holds: a table
The finished page can be checked against a short list of parts, each with a source and an owner.
| Part of the page | What it says | Built from | Owner |
|---|---|---|---|
| Current problem slot | A dated line on any disruption, what to do and when the next update comes; empty when nothing is wrong | The status line kept by whoever owns disruption messages | Operations or support |
| Answers to the top reasons | A heading in the customer's words with the answer or a link to the self-service fix | The ranked contact reasons | Support lead |
| Routes | Each route, what it suits, its hours and the reply time | The business's own standards per channel | Support lead |
| Urgent route | What counts as urgent and the route answered quickly | The written list of urgent problems and the escalation route | Support lead |
| Complaints | How to complain, the next steps, when to expect a response and how to take it further | The customer version of the complaints procedure | Complaints owner |
| A different approach | A gently worded route for customers who need the process adapted | The business's guidance on vulnerable circumstances | Support lead |
| The form | A reason first, then only what the reply needs | The reason list and the form rules | Website owner |
| After sending | A reference, the reply time and what to do if it becomes urgent | The written-channel standard | Support lead |
| Other markets | Each market's channels, languages and hours in local time | Each market's support plan | Market owner |
A chimney cleaning firm rebuilds its contact page (illustrative)
Thubrinzel Chimney Care turns a bare form into a contact page
Thubrinzel Chimney Care, an invented chimney cleaning and inspection firm with 4 sweeps and an office of 2, has a contact page that holds a phone number and a form with a single message box. The office manager tags 4 weeks of contacts by reason: 386 across phone, email and the form. 3 reasons sit at the top: moving or cancelling a booking (131), a copy of a past sweep certificate (74) and how to prepare the room before a visit (58), together 263 of the 386.
The new page opens with those 3 headings in the customers' words. Moving a booking links to the booking page, where a visit can be changed up to 48 hours ahead. Certificate copies link to a page where past certificates are downloaded by booking reference. Preparing for a visit gets a 6-point note on the page itself. Below them come the routes, starting with a separate number for problems on the day of a visit, answered by the sweep on duty from 7am, then the office phone from 8am to 5pm Monday to Friday and email and form replies within 1 working day. A complaints heading holds the short customer version of the firm's complaints procedure.
The form now starts with a choice of the same 9 reasons the office tags, followed by the booking reference, the address and the message. After sending, the customer sees a reference and a line saying a person will reply within 1 working day, with the on-the-day number repeated. Booking confirmations and the reminder sent 2 days before each visit link to the page.
Over the next 8 weeks, contacts about moving or cancelling a booking fall from about 33 a week to about 14, and the reason chosen on the form matches the office's own tag at close on 81% of form contacts. Certificate requests by email barely move. Reading them shows customers asking for certificates from visits before the booking system existed, so the page gains a line saying how to request those.
Common mistakes
- A bare form and a number. The customer writes out a problem the page could have answered and has no idea when anyone will reply.
- Answers placed in front of the routes. Customers who need a person have to open help articles before any route appears; answers belong beside the routes.
- Hours and reply times left off. A silent page leaves the customer to set the expectation the wait is judged against.
- Chat shown when nobody is on duty. A window that opens onto an empty team tells customers the business is absent at the moment it invited them in.
- No route for urgent problems. A problem on the day of a visit waits in the same queue as a question about next month.
- A form that asks for everything. Fields the reply does not need make the form slower to finish and the messages vaguer.
- An acknowledgement that says nothing. "We have received your message" without a reference or a reply time leaves the customer to chase.
- Judging the page by fewer contacts. A falling contact rate can mean customers gave up; read it beside complaints about getting help.
- Testing with a mouse only. A form or chat window that fails with a keyboard or a screen reader locks out the customers who rely on them.
- Hours that drift from the truth. A page written once promises hours and reply times the team stopped keeping long ago.
The hub for service and support covers the response standards and routing rules that this page shows to customers.
