Your Plymouth agent attached a controlled drawing to a Zendesk reply, and nobody could prove who else then saw it
Custom helpdesk and ticketing software for a Plymouth marine or defence firm typically costs £30,000 to £80,000 over 3 to 5 months. Zendesk, Freshdesk, and Intercom handle general support superbly; they aren't built to keep export-controlled attachments off the wrong reply, gate tickets by clearance, or prove who saw a sensitive document, which defence-adjacent support requires.
Most helpdesk tools are designed to share information freely and fast, which is exactly wrong for defence-adjacent support. An agent helping a customer with a marine component can attach a controlled drawing to a ticket reply, and Zendesk will send it without a second thought, to a contact who may not be cleared to receive it, with no way afterward to prove exactly who could see it. That's a controlled-data exposure born from a tool doing its normal job.
The deeper issue is that these platforms host your data on their cloud, with their access model. For tickets carrying clearance-sensitive content, your security officer can't easily sign off where it sits or how access is logged. So support either avoids touching sensitive matters in the system, fragmenting it into email, or quietly takes a risk nobody's comfortable with.
The problems nobody warns you about
- Controlled attachments sent on ticket replies to contacts who may not be eligible
- No clearance gating on tickets that carry sensitive technical content
- No defensible record of exactly who could view a controlled document
- Sensitive support data hosted on a cloud your security officer can't sign off
The case for owning your helpdesk & ticketing
Custom helpdesk software treats controlled content as controlled: attachments are checked against the recipient's eligibility before they send, sensitive tickets are gated by clearance, every view is logged defensibly, and the whole thing can run on infrastructure you control. You keep efficient support workflows while closing the exact gap, free sharing of controlled data, that off-the-shelf helpdesks create by design.
Budgeting a helpdesk & ticketing build in Plymouth
| Project scope | Typical cost | Timeline |
|---|---|---|
| Helpdesk core with attachment eligibility and clearance gating | £30,000 to £48,000 | 3 to 4 months |
| Added audit logging and self-hosting | £48,000 to £66,000 | 4 months |
| Full helpdesk integrated with CRM (Customer Relationship Management) and ERP (Enterprise Resource Planning) | £62,000 to £80,000 | 4 to 5 months |
What your build should include
What we build under helpdesk & ticketing in Plymouth
The engagements Plymouth teams bring us most often: ticketing system, customer support software, live chat integration, Zendesk alternative, Freshdesk alternative and Intercom.
Exactly what you get
You get a helpdesk that respects the realities of defence-adjacent support: controlled attachments checked before they send, sensitive tickets gated by clearance, every document view logged defensibly, and the option to host it where your security officer accepts. It keeps the SLAs, queues, and reporting good support needs, and integrates with your CRM and ERP so agents see the full customer picture.
How to choose a developer in Plymouth
Pick a team that understands controlled-data handling, not just ticket queues. Ask how an attachment is checked against recipient eligibility, how a sensitive ticket is gated, and how you'd prove who saw a document. Confirm self-hosting is an option for the sensitive data, and keep genuinely general support on Zendesk or Freshdesk where it's better value.
- !A vendor who treats attachments as a non-issue; ask how a controlled file is blocked from an ineligible reply
- !No clearance gating; ask how a sensitive ticket is restricted
- !No audit log; ask how you'd prove who saw a document
- !Cloud-only for sensitive data; ask how it passes a security review
- !No CRM or ERP integration; ask how agents get full customer context
If helpdesk & ticketing is on the roadmap, booking & scheduling, internal tools, website usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why can't Zendesk handle our defence support securely?
Zendesk is built to share information fast, which is the wrong default for controlled data. It will happily attach a controlled drawing to a reply for an ineligible contact, can't gate tickets by clearance, and hosts data on a cloud your security officer may not accept. Those are exactly the gaps a custom helpdesk closes.
How are controlled attachments protected?
Before an attachment sends, the system checks it against the recipient's eligibility and blocks a controlled file from reaching someone who isn't cleared to receive it. Every view is also logged, so you can later prove exactly who could see it.
Can the helpdesk be self-hosted?
Yes, and for clearance-sensitive support that's usually the point. Running it on infrastructure you control, with a full audit log, is what lets a security officer sign off handling sensitive tickets in the system rather than scattering them into email.