An IT support company website that's precise about what you cover
Small businesses choosing IT support want to know what you look after, how fast you respond, whether you cover their area and what it costs per user or device. An IT support company website earns trust by being exact about those, never vague or inflated. Here's what to publish, how Anticode builds it, and why your ticketing system still sits alongside it.
Who's reading, and what's gone wrong
Two kinds of visitor arrive. The first is an office manager or owner whose current provider is slow, or who has just outgrown the person who "does the computers". They're comparing two or three firms and want to understand plans and coverage. The second is an existing client with a problem right now, looking for the fastest way to report it. Serve both from the header: a "Get support" link for clients, and a route to plans and an audit for prospects.
Be precise, never promise what the contract doesn't
IT support is bought on trust and governed by contracts. A site that claims "24/7 instant support" when the service agreement says "next business day for low priority" creates a dispute waiting to happen. Write the website from your service terms, not the other way round.
| Vague | Specific |
|---|---|
| Fast response | Response targets by priority: critical within an hour in business hours, normal within four, low by next working day (use your real targets). |
| Round-the-clock support | Support hours, what out-of-hours cover includes, and whether it costs extra. |
| We cover everything | The systems you support (Microsoft 365, Google Workspace, Macs, networks, printers, phones) and what you don't. |
| Bank-grade security | The services you provide: patching, backups, endpoint protection, multi-factor rollout, staff training. |
| Local | The towns or postcodes you visit on site, and remote-only areas. |
Avoid security guarantees in particular. You can describe what you do to reduce risk; you can't promise a client won't be breached, and saying so can cause real problems later.
Plans, services and proof
- Support plans side by side: per user or per device, what's included (helpdesk, on-site visits, monitoring, backups), and project work billed separately. A "from" figure helps businesses budget.
- Service pages for the things people search for: managed IT, cloud migration, cyber security, backups and recovery, network installs, hardware procurement.
- Onboarding: what happens in the first month, from audit to documentation to handover from the old provider.
- Sectors: if you specialise in accountants, schools or medical practices, say so and explain why it matters.
- Certifications and partner status you genuinely hold, named exactly.
Support requests and audit bookings
Most providers already run a ticketing or PSA system, and clients should keep using its portal or email address for anything urgent. The website's support page should link to that portal first and give the phone number for critical issues. A website form is a fallback for clients who can't reach email, or for occasional requests from non-contract customers.
On Anticode, the standard contact form asks for name, email and a message. You can route those messages into the right place with connectors: a webhook to your ticketing system, if it accepts incoming webhooks, a post to a Slack or Discord channel, or a row in Google Sheets. Each submission is sent once without retries, so keep email notification on. If you want structured fields such as company, priority and affected device, use a custom form tied to a site function (up to 30 plain-text fields) or have the request form built as an app; their submissions use the same pipeline.
For prospects, the booking calendar suits a free IT audit or discovery call: visitors pick a service, day and time, and give name, phone and email. It offers six fixed times a day over the coming days (Mondays skipped), takes one booking per slot and doesn't sync with your calendar, so block the time in your diary and confirm each booking yourself. The online quote request process is a useful pattern for project enquiries.
A site that practises what you preach
Prospects will judge your security advice by your own site. Anticode publishes pages with no scripts, and its Sentinel runs twelve security checks on the exact HTML that ships, including the content security policy, form targets and anything that looks like a secret. Each published site has a security report at /.well-known/anticode-security, and because the site collects data, it won't publish until the account owner and the person publishing have two-factor sign-in on. The security checklist guide explains the checks. Pick the Technical (IBM Plex Sans) or Swiss (Inter Tight) design system for a clear, engineered look, and a blue or teal action colour.
Limits
Anticode isn't a helpdesk. There's no client login, ticket status or knowledge base search on published sites, no live chat, and forms can't take file uploads such as screenshots of an error. Booking slots can't be assigned to different engineers. Keep your PSA or helpdesk tool for support itself and use the website to explain, reassure and capture new business.
Questions people ask
Can clients log tickets through the website?
They can send a message that reaches you by email and, through a webhook connector, your ticketing system's intake. For urgent issues, point clients to your phone line and portal.
Should an IT support company publish prices?
A per-user or per-device starting figure and what it includes helps small businesses budget. Note that project work is quoted separately.
Can prospects book a free audit online?
Yes. The booking calendar offers six fixed times a day and takes one booking per slot; you confirm each one yourself. It doesn't sync with your calendar or assign engineers.