FAQ
A first-look FAQ based on the current project source and documentation.
Kantan Desk is a private support desk for teams that manage requests through tickets, email, portals, and controlled automation. It combines ticket queues, requester access, mailbox handling, team permissions, audit trails, integrations, and operational controls.
Kantan Desk is a product of Sector Processing LTD. It is not presented as its own company.
No. It is private support software, but the server must be able to read ticket content to provide ticketing, email, portal, search, automation, and administrative workflows. Protected stored credentials and integration secrets are encrypted where the original value must be recoverable.
Tickets can be created from the staff interface, requester portal, public submission form, email, API, or CLI tools.
Kantan Desk can poll one or more IMAP mailboxes, create tickets from new messages, match replies back to existing tickets, send reply-bearing ticket email through per-mailbox SMTP, and use a separate system SMTP relay for account email and one-way notifications.
Yes, the email documentation references Gmail OAuth for mailbox access, alongside username/password support for other mailbox providers.
Yes. Registered requesters can submit, review, and reply to tickets. Public-form requesters can use secure email-based access without first creating an account.
Yes. It includes customer/client records, multiple contacts, primary contact details, notes, owner assignment, tags, next action and due date, linked ticket history, open/resolved counts, last interaction, and team-scoped customer access.
Very detailed. The source defines permissions for issues, users, roles, teams, clients, knowledge base, documents, time entries, webhooks, email queues, settings, MFA management, audit, logs, monitoring, privacy, storage, statistics digests, email suppression, and AI chat.
Kantan Desk supports TOTP-based MFA with authenticator apps, single-use backup codes, voluntary user setup, admin-required setup, admin reset, rate limiting, and audit logging. It does not currently support WebAuthn/FIDO2.
Yes. SuperAdmins can create restricted API keys for inbound ticket creation. Requests require an API key, timestamp, HMAC signature, team assignment, and IP or CIDR allowlist.
Yes. It can send signed webhook deliveries for ticket-created and ticket-status-changed events. Receivers should verify the raw body with the v2 HMAC signature and reject stale or repeated delivery IDs.
Yes. It can record reputation signals such as bounces and complaints from inbound mailbox parsing or supported mail-service reputation hooks, then surface those signals against addresses, tickets, and users.
The documented runtime requirements include Node.js 22.19+, Yarn 4.2.2, PostgreSQL 12+, Redis 7+, SMTP/IMAP services for email, and a production reverse proxy such as nginx or Caddy.
No. Optional AI assistance is stored as internal ticket comments and is not shown to the requester. When enabled, ticket and conversation content is sent to the selected provider, so administrators should assess that provider’s data handling before use.
Questions should go through Sector Processing LTD.