Jess Hartley
Feature review
What Kantan Desk appears to do.
A practical support desk with strong attention to ticket intake, email, team controls, GDPR compliance workflows, integrations, and administrative oversight.
Ticket work
Structured support queues.
Kantan Desk centres the work around tickets that can be routed, followed, discussed, closed, and recovered.
- Create tickets from staff screens, requester portal, public submission form, email, API, or CLI tools.
- Track status, formal closure, priority, type, tags, assignee, team, client, and requester.
- Use public replies for requesters and internal notes for staff-only collaboration.
- Attach files, record time, follow tickets, lock tickets, and use templates.
- Restore removed tickets, comments, clients, and user accounts through trash workflows.
CRM and customer context
Customer records sit beside the support queue.
Kantan Desk includes customer/client records that behave like a lightweight CRM layer for support work, not just a flat ticket list.
- Named owner, next-action note, due date, and tags on every client record.
- Multiple contacts per client with primary-contact state, title, phone, and notes.
- Client list shows ticket count, contact count, and last interaction at a glance.
- Create a ticket directly from the client profile to keep it linked.
- Scoped to teams; recoverable through trash; privacy workflows cover all CRM fields.
Marcus Osei
Technical lead
Priya Nair
Billing
Acme Industries
Active
Owner
Sophie Clarke · 4 open tickets
Next action
Follow up on contract renewal — due in 3 days
Tags
Enterprise Renewal Priority
Teams and routing
Route and assign work automatically.
Teams scope access across mailboxes, clients, and tags. Default assignment rules land tickets with the right people from the start; transfer workflows keep every handoff traceable.
- Define teams with admin and member roles; scope mailboxes, webhooks, tags, and client records per team.
- Set default assignment so incoming tickets reach the right team or agent without manual triage.
- Transfer tickets between teams and agents with a full audit trail of every handoff.
- Mailbox change requests queue for approval, keeping configuration changes reviewed before they take effect.
- Time tracking, knowledge-base articles, and client records can each be scoped to team-level visibility.
Requester portal
Support access for customers and requesters.
Registered requesters can submit tickets, review open and closed requests, and reply. Public-form requesters can use secure email-based access without creating an account first.
Knowledge base
Documentation alongside tickets.
Staff can create, manage, and publish knowledge-base articles and document views. Access is permission-controlled; content can be team-scoped or shared across the desk.
Email handling
Email becomes support work.
The email model is unusually detailed: inbound IMAP polling, reply detection, mailbox-specific sending, deduplication, and deliverability visibility are all part of the product surface.
Inbound mailboxes
One or more IMAP mailboxes can be polled on a schedule and converted into tickets or comments.
Reply matching
Email replies are matched back to existing tickets using ticket references and requester checks.
Outbound controls
System SMTP handles account and notification mail; per-mailbox SMTP handles reply-bearing ticket mail.
Queue processing
BullMQ and Redis keep email work out of the immediate web request path.
Attachment policy
Attachment rules can allow or block file types, enforce size limits, and record blocked files as internal ticket comments.
Reputation signals
Bounces and complaints can be tracked against email reputation, tickets, and user email health.
Digest emails
Configurable digest schedules deliver periodic summaries of open and active ticket work to staff and requesters.
Privacy and GDPR
Data subject requests are handled inside the product, with a full record of every action taken.
Kantan Desk includes verified export and deletion workflows built directly into the admin area — covering every table that holds personal data. Every step, from search through confirmation, is recorded in the tamper-evident audit log, giving operators a defensible compliance history without external tooling.
Data export
Full record export by email address.
The export workflow locates all records associated with a given address — tickets, comments, files, sessions, customer contacts, client relationship fields, and audit log references — and packages them for review and dispatch. A confirmation email is sent through the system relay on completion.
Anonymization and erasure
Controlled deletion across all linked data.
The erasure workflow anonymizes matching users, tickets, comments, files, and CRM fields in a controlled sequence. Client tags, next-action notes, and linked contact records are cleared where a match is found. The requester's address is suppressed to prevent re-engagement after erasure.
Audit trail
Every privacy action leaves a signed record.
Export requests, erasure workflows, suppression events, and verification steps are all captured in the tamper-evident audit log. Operators have a complete, unforgeable compliance history independent of application logs that could be cleared or altered.
Request intake
GDPR requests route as first-class tickets.
A dedicated GDPR/legal ticket type routes data subject requests to the right team through the standard assignment and escalation model. Internal staff notes keep deliberation private; requester-visible replies confirm that action has been taken.
Optional assistance
AI stays internal.
When enabled by administrators, Kantan Desk can run internal ticket discussion through configured providers.
- Supported provider options include Anthropic, OpenAI, DeepSeek, OpenRouter, or a compatible custom provider.
- AI questions and answers are stored as internal comments.
- Requester-facing comments are kept separate from staff-only discussion.
- Administrators should assess provider data-handling requirements before enabling the feature.