Most teams reach for a help desk at a predictable moment. The shared support inbox stops coping, the same questions get answered five times, customers contact you on three channels and nobody sees the whole conversation, and nobody can say which tickets are slipping. A ticketing tool fixes the visibility problem. What it often doesn’t fix is the gap between how the vendor thinks support should work and how your business runs it.
I build custom help desk and ticketing software for UK businesses that have outgrown that gap. Instead of bending your routing, SLAs and escalation rules around an off-the-shelf product, you get a system built around your process, connected to the tools you already run, with no per-agent licence fee. Senior-led means the developer who sits in on your support queue is the one who builds the system.
If you need an internal IT service desk for staff, with incidents, changes and an asset register, IT service management software is the closer fit. This page is about supporting your customers.
When SaaS is enough, and when it isn’t
For a lot of teams, Zendesk, Freshdesk or Help Scout is the right call: standard workflows, a flat team, nothing proprietary to integrate, and a budget the subscription comfortably covers. These tools are quick to set up and well supported. Open-source options such as Zammad and osTicket suit teams who want to self-host without a build.
Building becomes worth considering when you recognise any of these:
- Per-agent pricing has become a real cost. The bill scales with every hire, and shared logins to dodge it break the audit trail.
- Your workflows don’t fit the vendor’s model. Multi-level escalation, approval chains for refunds or high-value tickets, SLAs that vary by customer tier or contract, and routing by customer value don’t sit comfortably in a generic automation builder.
- The help desk has to work with systems you already own. When it needs a legacy CRM, ERP, accounting or stock system, vendor APIs and Zapier-style connectors bring polling delays, rate limits and one-way sync.
- Compliance or data residency is fixed. Regulated sectors often need audit trails, retention rules and approval evidence beyond standard GDPR features, plus a clear answer on where data is hosted.
If two or three of these apply, the case for building gets stronger every year you stay on per-seat pricing.
Why off-the-shelf help desk software falls short
- The price keeps climbing. Per-agent fees rise with headcount, and advanced automation, full API access, AI assistance and decent reporting sit behind higher tiers. Phone channels and AI resolutions are often billed separately again.
- Hidden costs. Setup fees, paid integration work, overage charges when volume spikes, and sometimes a charge to export your own history when you leave.
- Omnichannel in name only. Chat, email and social often sit in separate queues, so agents keep switching between screens to see one customer’s history.
- The workflow is the vendor’s. You adapt escalation, routing and approvals to the tool, then keep spreadsheets for the parts it can’t do.
- Data stays siloed. With the help desk cut off from your CRM, accounting and operational systems, agents gather context by hand that the software could have shown them.
- Generic AI. Reply suggestions trained on everyone else’s tickets miss your terminology, so agents switch the feature off.
- Reporting answers the vendor’s questions. Custom reports often need SQL access or paid professional services.
- Lock-in. Proprietary field structures and export limits mean switching turns into a migration project of its own.
What I build instead
Your workflow first. I map how your team handles support today, including the escalations and approvals that live in people’s heads, and build software that supports them directly.
Full context when the ticket opens. With direct links to your CRM, accounting and operational systems, a ticket arrives already showing purchase history, account status, contract details or open orders, so the first reply doesn’t wait on a hunt through three other systems.
You own the result. No subscription and no per-seat pricing that creeps up at renewal. The software is a business asset, not a permanent line item.
Compliance in the build. UK GDPR and the Data Protection Act 2018 from the first release, with hosting in the UK.
A modular core. A solid first release, then channels, integrations and automation in phases, so growth is an addition rather than a rebuild.
Help desk features I build
Ticket management with the states, priorities, categories and custom fields your team uses (account IDs, contract values, SLA tiers), a clear queue, internal notes and @mentions, and a readable ticket reference.
One queue for every channel. Email with proper threading, web forms, live chat, phone through a provider such as Twilio, and Slack or Microsoft Teams for internal requests, with social or WhatsApp added where they matter. I build only the channels you use.
Routing and escalation by your rules: skills-based and load-balanced assignment, time-based escalation, and routing by customer tier, product, location or ticket value.
SLA management with response and resolution targets by priority, customer segment or contract, and warnings before a deadline is breached.
Agent tools. Macros and canned replies for common ticket types, bulk actions for assignment and closure, and actions inside the ticket, such as issuing a Stripe refund or checking an order in Shopify, instead of switching systems.
A customer portal and knowledge base, so customers raise and track tickets and find answers themselves, with articles suggested as they type.
A business rules engine for the logic SaaS tools struggle with: approval chains for refunds or credits, identity checks before account changes, branching workflows, and automation triggered by events in connected systems.
Reporting on volume, response and resolution times, first-contact resolution, CSAT, SLA compliance and agent performance, with scheduled exports.
Access and audit. Role-based permissions, single sign-on with Microsoft Entra ID, Okta or Google Workspace, and a log of who changed what and when.
Optional AI assistance: triage by intent, replies drafted from the ticket and your own knowledge base, and automatic tagging, added where it earns its place.
For MSPs, agencies and multi-brand businesses, I also build multi-tenant support, with isolated data, separate queues and client-specific SLAs and branding, without paying for a separate SaaS instance per brand.
How a project runs
- First Gear, five days, £495. I sit with your agents and team leads, map your processes, channels and integrations, and build a working prototype of your ticket flow. A one-page plan sets the fixed price of the first release, and the £495 comes off the build if you go ahead.
- First release, live within a month. Email and web-form intake, routing, SLA tracking, the customer portal and basic reporting, with regular demos as it takes shape.
- Testing, migration and rollout. Testing covers the awkward cases, such as bulk actions and complex routing, as well as the everyday flow. Migration and a team-by-team rollout keep the business running while people switch.
- Later phases and support. More channels, knowledge base, integrations and AI, each about a month and fixed-price. Every build has a 30-day fix guarantee and the first month of hosting free, then an optional monthly plan or a handover to your own IT team. Agents, team leads and admins each get their own training.
The risks to watch are scope creep and stakeholders disagreeing on the “right” workflow, so I pin the first release down tightly and add to it afterwards.
What it costs
A help desk build typically costs £2k to £10k, fixed at the end of First Gear rather than charged by the hour. Core ticketing for one or two channels usually fits in one build. Omnichannel intake, several integrations, complex approvals and stricter compliance are what add phases.
- SaaS scales with headcount. A build is a fixed cost plus a flat monthly plan, so cost doesn’t track headcount.
- You own the software, with no renewal increases and no vendor setting your price.
- No integration surcharges. Connections to your CRM, billing and other tools are part of the build.
For small teams with simple needs, the maths may favour staying on SaaS or an open-source tool.
Where this works
E-commerce and retail: order queries, returns and refunds with order history pulled from Shopify or WooCommerce, refund approvals with stock updates, and intake that copes with seasonal peaks.
Software and SaaS companies: product support, bug reports and feature requests, tied into Jira or GitHub, with account and usage data beside the ticket.
Financial services and insurance: identity checks before account changes, dispute and claims tracking, and complaint workflows that track the FCA’s response deadlines with a full audit trail.
Professional services: client and document requests, time tracking, and links to your accounting software.
IT services and MSPs: per-client queues, escalation workflows and time tracking for billing.
Property management: tenant maintenance requests with contractor assignment and status tracking, and landlord and tenant portals showing different views of the same job.
Healthcare and care providers: patient enquiries with strict access controls, audit trails, and complaint tracking that supports CQC expectations.
Hospitality and travel: booking changes and guest requests across properties, linked to your property management system.
Education: separate portals for students, parents and staff, with sensitive concerns routed to the right people.
Public sector: citizen enquiries, complaints and FOI requests on their own workflows, with the retention and reporting the sector requires.
Describe your channels, team size and the rule your current tool can’t follow, and I’ll say whether a build, a SaaS tool or an open-source help desk suits you.
Common Questions About Custom Help Desk & Ticketing Software
Should we just use Zendesk, Freshdesk or Help Scout instead? ›
Often, yes. With a small team, standard support workflows and no in-house systems to connect, a SaaS help desk is quick to set up and good value. If you'd rather own the software without a build, an open-source help desk such as Zammad or osTicket is worth a look. A custom build earns its place when per-agent fees become a serious cost, when your routing or escalation rules don't fit the vendor's model, or when the help desk has to work closely with systems you already run.
What does bespoke ticketing software do that a SaaS tool can't? ›
It follows your rules instead of the vendor's: SLAs that vary by contract, approvals before a refund or a credit, routing by customer value or product, and a ticket that opens already showing the customer's orders, invoices or account status from your own systems. You also stop paying per agent, so adding staff, departments or brands doesn't change the bill.
How does custom development cost compare to SaaS? ›
SaaS help desks charge per agent per month, and AI features, extra mailboxes, phone channels and advanced reporting often sit on higher tiers or cost extra. Most of my builds land between £2k and £10k, with the price fixed after First Gear, then an optional flat monthly plan. Teams that are growing, or paying for tiers they barely use, tend to see the numbers move in their favour, and I'll work it through on your figures.
What's the typical development timeline? ›
First Gear takes five days and gives you a working prototype of your ticket flow. The first release, usually email and web-form ticketing with a customer portal, routing, SLA tracking and basic reporting, then goes live within a month. More channels, a knowledge base, integrations and AI assistance follow in later phases, each about a month with its own fixed price.
What about data security and compliance? ›
Every build follows UK GDPR and the Data Protection Act 2018: audit trails on every change, role-based access, encryption in transit and at rest, configurable retention, and tools to export a customer's data for a subject access request, which you have a month to answer, or erase it. For financial services, complaint tickets can track the FCA's eight-week deadline for a final response.
How do you handle migration from our current help desk? ›
I import your contacts, historical tickets with their comment history, attachments, categories and custom fields, with timestamps preserved so the audit trail stays intact. Part of the planning is deciding how much history is worth bringing across. Dirty legacy data and attachments are the slow parts, so I clean and validate before cutover, then roll out team by team to keep the first-weeks slowdown short.