How nabudesk sees the help desk
A help desk is not a place where tickets go to be counted. It is the workspace where a small team looks after its customers. Here is how that idea shapes what we build.
The nabudesk team2 min read
Ask ten people what a help desk is and you will hear about tickets, queues and dashboards. We think those are the parts, not the point. The point is a small group of people trying to look after customers well, day after day, without burning out.
A workspace, not a warehouse
Much help desk software is organized around the ticket as a record: something to store, count and export. We would rather organize around the person doing the work. What does an agent need in front of them right now? What does a supervisor need to see before the day goes wrong? The record matters, but it is a by-product of good work, not the reason for it.
That shows up in small, concrete ways: one shared inbox whose live counts filter the queue in a click, presence that tells you a colleague already has a ticket open, and a Page guide on every screen so a new agent can learn the product from inside it.
Email is where customers already are
Customers write to a support address, so nabudesk starts there. Forward the mailbox and every message becomes a ticket. Replies stay in the conversation and can leave from your own domain. Phone calls and walk-ins can be logged by hand. We would rather do the most common channel properly than claim every channel at once.
Built for teams of 2 to 50
We are not building for a twenty-thousand-seat operation, and we say so. The people we have in mind run support for a company of a few to a few dozen agents. They have outgrown a shared inbox, or a heavy legacy help desk, and they decide for themselves. So the pricing is public: per agent per month, no minimum number of seats, no setup fees, a free trial without a credit card, and every feature of every plan listed on one page.
Structure that stays out of the way
Service levels, automation and roles are powerful, and easy to over-build. We design them so you can begin with one policy and one workflow and add more once you trust them. Our own documentation says it plainly: start with one simple workflow.
AI on your terms
The AI assistant can draft a reply, refine one, or turn a solved ticket into a Help Center draft. It runs on your own AI vendor account, so usage is billed by that vendor rather than as a per-seat fee from us, and an agent reviews everything before it is sent or published. It stays off until an administrator switches it on.