A Helpdesk and Ticketing System You Own Instead of Rent
SLAs, WhatsApp and email intake, assignment rules, escalations and a knowledge base, deployed on your infrastructure with no per-agent meter running.
Per-agent helpdesk pricing has a strange property: it punishes you for the exact thing it claims to support. Hire three more support people and your software vendor gets a raise too, forever. We build the opposite arrangement: a ticketing system that runs on your own server, with SLA timers, WhatsApp and email intake, routing rules, escalation chains and a bilingual knowledge base, delivered for a fixed build cost agreed in writing before work starts. Ten agents or forty, the invoice does not move. We have built business systems from Cairo since 2014, delivering remotely to Saudi and UAE teams with written acceptance criteria and payments released in stages you approve.
No per-agent meter
The price covers the build and is fixed in a written scope. Your headcount is your business; it never appears on our invoice.
Your infrastructure
Deployed to your VPS, your cloud account or a machine in your office. Ticket data, customer contacts and attachments stay on hardware you control.
Intake where your customers already are
WhatsApp Business API and email feed the same queue, so agents stop juggling a shared support phone next to an overflowing inbox.
Arabic and English throughout
Agent screens, customer portal and knowledge base in both languages, with RTL layout done correctly rather than bolted on at the end.
What goes into the build
SLA timers with real business hours
First-response and resolution clocks per priority level, paused outside your working calendar, Friday-Saturday weekends and public holidays included.
WhatsApp and email ticket intake
Inbound WhatsApp messages and parsed mailboxes become tickets automatically, with the full conversation thread attached so agents see history, not fragments.
Assignment rules and escalations
Round-robin or skill-based routing sends tickets to the right agent, and an SLA clock running low escalates the ticket up the chain without anyone watching for it.
Knowledge base that deflects tickets
Articles in Arabic and English, suggested to customers before they open a ticket and shown to agents while they answer one, so the same question stops being retyped.
Customer portal
Customers log in, see ticket status and reply in place, which quietly removes the daily "any update?" emails from your queue.
Reporting and CSAT
Volumes, response times, SLA breach counts and satisfaction scores broken down by agent, team and channel, exportable for your monthly review.
What it costs, once
| Scope | Price range | Typical timeline |
|---|---|---|
| Core helpdesk: tickets, email intake, SLAs (2-3 modules) | from $3,000 | typically 8-12 weeks |
| Full system: WhatsApp intake, routing rules, escalations, knowledge base | $4,500-8,000 | 12-20 weeks in most projects |
| Large integrated: customer portal, CRM/asset integrations, multi-brand queues | from $8,000 | 20+ weeks |
The figure is fixed in the written scope after we review your intake channels, and it does not change when your team grows. After launch, the recurring cost is a modest server, not a seat count.
How a helpdesk build runs
- Intake walkthrough: a video call on your working hours where your support lead shows us how tickets arrive today; an NDA can be in place before you show us anything internal.
- Fixed offer: you receive a scope document listing every module, the price and written acceptance criteria, with payment split into stages that release only when agreed work is delivered.
- Iterative build: the system runs on a test server your agents log into while we build, filing practice tickets so routing and escalation rules get corrected before launch, not after.
- Data migration: we import open tickets, customer records and knowledge base articles from your current tool, then run a parallel period where both systems receive traffic until you sign off.
- Transfer: with the last payment, the source code, database, server credentials and admin documentation move to you, and the contract states that ownership plainly.
Frequently asked questions
What actually happens when we hire more agents?
Someone creates another user account, and that is the whole event. There is no license tier to move up to and no invoice change. Hosting cost only moves if traffic grows enough to need a bigger server, which is rarely the same moment headcount grows.
We already pay for a SaaS helpdesk. Is switching worth it?
Do the arithmetic on your own renewal: seats times monthly fee, projected three years out, against a one-time build starting at $3,000. For a two-person team, staying on SaaS is often the right answer and we will tell you so. Past a handful of agents, ownership usually wins.
Who fixes things after launch?
The build includes a defect warranty period, and after that you choose: a monthly support agreement with us, or your own developers, since the full source code and database are in your hands. Nothing in the system requires us to stay involved.
How does the WhatsApp side work in practice?
We connect your WhatsApp Business API number so inbound messages open tickets with the conversation attached, and agents reply from inside the helpdesk instead of a shared phone. Approved template messages handle notifications such as status updates outside the 24-hour reply window.
Where does it run, and who can see our data?
On servers you control: your own VPS, your cloud account, or a machine inside your office. We hold access during the build and afterwards only if you keep us on for support, and you can revoke it at any time. Support tickets carry customer data, which is exactly the material many teams prefer not to place in a third-party SaaS.
Stop renting your support desk
Tell us how tickets reach you today (email, WhatsApp, phone) and how many people answer them. We will give you a straight opinion on whether a self-hosted build makes sense at your size, and a written figure if it does.
