Someone reaching your contact page may have chosen a service, need clarification or want to arrange a meeting. They need a short answer for their task. A long list of equally prominent icons leaves the visitor to work out which one to use.
This guide helps you agree the page’s content. Enquiry form fields and testing the mobile journey are separate topics. We are not setting legal disclosure requirements or promising more enquiries.
Start with requests the team handles
List the reasons people contact you: discuss a new service, ask about an existing order or arrange a meeting. Give each request an owner and a channel they actually check. New orders and support can share a contact if that fits the team’s work.
Choose a main action and explain an alternative. For example, a form may help describe a task while email supports correspondence. Do not create a separate address for every topic just to look like a large company. Remove a channel from the public page if no one handles it.
Help people choose a contact channel
Name the method and its purpose in words. “Message us about a service” explains more than an icon alone. Keep an address or profile name visible so people can check and copy it if the automatic link does not work. Do not substitute a newsletter subscription for contact.
The table below offers options to agree, rather than a required set. Do not add a phone number just because other websites have one: establish whether the business can take calls. A form is not the only possible way to make a first enquiry either.
| Channel | Suitable request | What to explain alongside it |
|---|---|---|
| Form | Describe a new task | What to send and how the team will reply |
| Correspondence with details | Current address and a relevant subject | |
| Phone | Conversation, if the team takes calls | Call hours and the number’s purpose |
| Messaging app | A short question, if the channel is staffed | Profile name and response arrangements |
Separate opening hours from response expectations
Office opening hours, call hours and message handling hours may differ. Label what the schedule applies to. If customers are in different time zones, add a clear reference, such as Kyiv time when that is what the team uses.
A form may accept requests outside working hours without providing round-the-clock replies. Publish a first-response timeframe only when the team has agreed it and can meet it. If there is no fixed timeframe, explain how enquiries are handled. Update this block for holidays and temporary pauses.
Explain the service area and visiting arrangements
Distinguish a visiting address, an area served by visits and remote work. If an office does not receive customers, do not present its address as an invitation to come over. Explain how to arrange an appointment; for an on-site service, name the city or areas served, or explain how to check availability.
A map makes sense when it helps people reach a real location. Keep the address in text alongside it, with any useful entrance directions. If there is no visiting location, you can leave the map out. Do not present an arbitrary point or someone else’s office as the business’s premises.
Show what happens after an enquiry
Explain what is needed to start a conversation and what the team will do next. A few sentences about the task and a reply method may be enough; a detailed brief can follow later. Do not request confidential documents through a routine contact channel merely to complete an enquiry.
A message confirming acceptance of a request does not mean an order or meeting has been agreed. Match the copy to the actual process. If the business has another working channel for form problems, show it; do not invent a backup contact that nobody checks either.
Check links and the route to contact
Reach contact from the menu, a service page and the footer. Check that links lead to current addresses, the intended number or profile. Opening an email application does not confirm delivery, and opening a messaging app does not start a conversation.
Link names should explain the action. Avoid identical “Here” labels for a form, map and email. W3C WAI guidance on meaningful link text explains this principle. A visible label also helps with a contact that can only be copied.
- Language versions list the same channels and conditions unless differences are agreed.
- Contacts are readable on a phone and can be chosen without finding a hidden hint.
- Links can be reached with a keyboard, and their names explain their purpose.
- The hours match the named channel, and visiting arrangements make sense without a map.
- An agreed test confirms receipt by the responsible person.
What to give the page developer
Make one working list: request type, public channel, recipient, hours, reply arrangements and area served. Agree it with the people handling enquiries. This avoids leaving a designer to invent opening hours or button copy.
Add current addresses and links, meeting arrangements, translations and an owner for updates. Separately agree a test scenario with safe data. Arrange any actual test call or message with the recipient; a technical check should not create unexpected enquiries.
For a wider review, use the guide to building trust in a new business. After launch, keep contacts in your first-month observation checklist.
Contact page FAQ
Does every website need a phone number?
For this editorial structure, a working reply method matters. A phone number is useful if the business takes calls. Check any specific legal requirements for the particular business separately.
Do I have to add a map?
Add one when it helps visitors reach a location. For remote work or an on-site service, the area served and meeting arrangements may be more useful.
Are footer contacts enough?
They may be enough for a short website if all necessary arrangements are clear. A separate page is useful when several channels, schedules or visiting conditions need explanation.
What if a channel temporarily stops working?
Update its label or remove it and show a working contact method. Also check the menu, service pages and all language versions that mention it.