Answers to the questions that come up most often about how Quetix works.
Quetix connects to one or more email inboxes and, every minute, pulls new messages and converts them into structured tickets. For each email, it uses Claude to extract a priority, category, contact, company, sentiment, product area, a one-sentence summary, and a routing suggestion. Those fields are editable and used to populate your dashboard, filter views, and route work.
The storage is local. Your tickets, source credentials, and configuration live in a SQLite database on the machine running Quetix. The only external call is to Anthropic's Claude API when you have an API key configured โ this sends the email content to Claude for extraction.
Anything that speaks IMAP. Presets are provided for:
outlook.office365.comSlack, webhook, and Gmail/Outlook OAuth sources are on the near-term roadmap.
Claude Haiku (the default) hits roughly 95% field accuracy on typical support email. Sonnet does a few points better on ambiguous cases and is a drop-in swap via the INTRAY_MODEL env var. Every extracted field is editable on the ticket, and future versions will use corrections to fine-tune routing.
For critical routing (outage, security), don't rely on the confidence score alone โ scan the raw email.
With Claude Haiku and prompt caching on the system prompt, extraction runs roughly $0.02โ$0.05 per 1,000 emails. Sonnet is ~5ร that. You can cap costs with MAX_MESSAGES_PER_SYNC in .env.
In the local SQLite database at server/data/intray.db. This is suitable for a trusted machine with full-disk encryption. Moving credentials into the system keychain (macOS Keychain / Windows Credential Manager / libsecret) is on the roadmap.
No. Quetix only reads INBOX since the last sync. It does not send, mark as read, move, or delete messages. You can verify this in the source โ see server/src/imap.ts.
Click the refresh icon in the top bar. It calls POST /api/sync, which runs every active source immediately regardless of the normal 60-second cadence.
Yes โ the SQLite file at server/data/intray.db is standard SQLite3. Export with sqlite3 intray.db .dump or any GUI tool (TablePlus, DBeaver). A one-click CSV export is available on the Tickets page.
Yes. On first boot, Quetix seeds three demo tickets so the dashboard is populated. You can also use the New ticket button to paste an email and see the full extraction pipeline without connecting a mailbox.
Quetix ships as a desktop app for macOS and Windows (Electron), as an iOS companion app (bundle ID net.quetix.souriapps), and as a self-hosted repo you can run from source with Node 20+.
Email support@souriapps.net โ we aim to respond within one business day.