Product
Four things your customers start, finished on one screen
Shared inbox, live chat, knowledgebase and SLA automation, side by side in five zones — the module rail, your filters, the queue, the conversation, and everything known about the customer beside it.
14 days free · No card required
Shared inbox
Live chat
Knowledgebase
SLA automation
Shared inbox
One queue your whole team can actually read
Every message lands in a department queue grouped by day, so the team opens the desk and sees what happened since yesterday instead of a wall of undifferentiated rows.
Date-grouped queues — Today, Yesterday, then by week
Saved views keep your columns, filters and sort
Mass actions: assign, move, merge, set due, reply
Internal notes that the customer never sees
Live chat
Answer the visitor, then keep the thread
Chats queue by department and land with the operator who takes them. When a conversation needs a paper trail, one action turns the transcript into a ticket that carries on in the inbox.
Queued and active chats side by side
Convert any chat into a linked ticket
Canned responses and per-visitor notes
Visitor context: page, referrer, country, visit count
Knowledgebase
Answer it once, then stop answering it
Articles sit in nested categories with their own visibility rules, and each one reports how often it was read and whether readers found it useful — so you can see which answers are pulling their weight.
Nested categories with per-audience visibility
Helpful / not-helpful ratings on every article
View counts and a popular-articles report
Comments with approval before they publish
SLA & automation
Clocks that respect your opening hours
Due dates advance through working time, not wall time, so a Friday-evening ticket is not already breached on Monday morning. Inbound mail is filed by rule before anyone has to read it.
Working-hours due dates from a 7-day schedule
Plans matched by department and customer group
Escalation on overdue, resolution overdue or no reply
Mail parser rules set department, priority and owner
Three questions for every vendor
What this desk does that the others do not
Every helpdesk on your shortlist has an inbox and a chat widget. These three are where they differ, and all three are things you can make somebody prove in a demo.
01
Another customer cannot reach your data, and it is the database that says so
Every vendor tells you your data is isolated, and for most of them that means their code remembers to filter by your account on every query. Ours is a rule in the storage itself: every link between your records carries your account on it, so a record pointing at somebody else’s data cannot be written at all. Not caught by a check afterwards — unwritable, and we prove it against a real database on every build.
Ask the others whether their database would refuse that write, or whether their code simply has to remember not to make it.
02
Your customer hits reply, and it lands on the same ticket
Gmail, Exchange and most bulk senders rewrite the hidden identifier other desks thread on. When they do, a reply arrives as a brand-new ticket: the history sits in one place, the answer in another, and two of your people answer the same person. We thread on the reply address itself and look for it wherever the mail system put it — To, Cc, or the line it added on delivery.
Bring a conversation that split in two on your current desk. This is something to watch happen, not something to take our word for.
03
Your customers never have to see a ticket number
Most desks staple something like [#ABC-123456] onto every subject line, because without it their threading falls apart. Ours does not need one, so your replies read like mail from a person at your company instead of output from a system. Some customers do expect a reference — so it is a setting, and you decide.
Look at the last support e-mail you received from anybody. Count the brackets.
Everything included
And what the four are built on
No module tax. Every plan ships the whole suite; the tiers differ on volume, automation depth and governance.
Ticketing
Departments, statuses, priorities and labels, on every conversation the desk touches.
Saved views
Pin a filter, column set and sort order, then hand it to the rest of the team.
Mail parser
Rules that read inbound mail and set department, priority, owner and labels on arrival.
Self-service portal
A client-facing site where customers open tickets, track them and read your articles.
Teamwork
Shared calendar, tasks with progress, sticky notes and a contact book beside the queue.
Downloads & troubleshooter
Versioned file library plus guided fault-finding trees that end in an answer or a ticket.
Roles & permissions
Per-module access for every staff group, with presence visible across the desk.
Reporting
Ticket volume, response time, SLA compliance, department load and staff performance — plus article ratings and chat reports in their own modules.
Soon
Languages
Run the desk and the customer portal in parallel locales from the same content.
Soon
Campaigns
Outbound release notes and outage notices to the contacts you already support.
“The portal was the part we underestimated. Customers stopped mailing to ask where their ticket stood, because they could simply look — and the article we pointed them at answered the follow-up before they asked it.”
JH
Jasper Holt
Service Delivery Manager, Nordkap Marine
−28%
inbound volume
Start today
Put the whole queue on one screen
Fourteen days with your own mail, your own departments and your own SLA clocks running. Nothing to install.
No card required · Set up in an afternoon
Connect your own mailbox
Keep your existing mail addresses
No ticket numbers in your subject lines