One AI toolkit forcustomer success managers
Call notes into follow-ups. Slack and Gmail pulled into one memory per account. Escalations filed in Jira or Linear without leaving your keyboard. One menu-bar app, one shortcut, and the account history stays on your machine.
Twenty accounts, five tools,
and the context lives in your head
A customer success day is the same loop on repeat: the account talks in Slack and email, you talk to them on calls, the problems have to reach engineering as tickets, and the whole story has to be retold at every QBR and renewal. The record of all that is scattered across an inbox, a Slack sidebar, a ticket tracker, and a CRM field nobody fills in. A browser chatbot doesn't know which account you're on, and pasting a customer's email thread into one is a conversation with your security team waiting to happen.
Khint keeps the loop behind one shortcut, inside the tools you already use. Select text anywhere and run a saved AI Action on it in place: call notes become a follow-up, a complaint becomes an engineering-ready ticket, a rough draft becomes a send-ready email. One Memory session per account absorbs the Slack pulls, the Gmail threads, and every ticket you file, so drafts come out account-aware, and the history never leaves your machine.
One account,
handoff to renewal
Every stage below is a shipped feature, not a roadmap slide.
- HandoffOpen a memory session for the accountNew account lands from sales? Start a Memory session with the customer's name and make it active. From now on every thread you pull, every call you process, and every ticket you file through Khint is logged into that session and compacted into one account context, kept local on your machine. The handover notes themselves get the first pass: select them, run a summarize Action, and the session starts with a clean picture instead of a forwarded email chain.
- PulsePull the account's channels into one placeThe account's reality is scattered across a shared Slack channel and a Gmail thread. From the palette, Pull channel brings the recent Slack messages into the session; Pull thread does the same for the email conversation. Each pull lands as an entry the account's compacted context absorbs, so the next thing you draft already knows what the customer said this week, without you re-reading either tool.
- CallCall notes → structured follow-upAfter the check-in call, select your raw notes and run a follow-up Action in place: what was agreed, who owns what, what the customer is still waiting on. Because the session context rides along, the summary knows that the export bug they mentioned is the same one they escalated last month, not a new report.
- Follow-upSend the recap where the customer reads itFrom the same palette, Send email opens a Gmail flow that gathers the recipient and subject, shows you a preview, and sends only after you confirm. Not ready to send? Create draft parks it in your Gmail drafts instead. Either way the body is the text you selected: the follow-up your saved Action already shaped, in your voice, not a chatbot's.
- EscalateVague complaint → engineering-ready issueWhen the problem is real, select the customer's own description and file it: Create issue in Jira or Linear from anywhere, with an Action drafting the summary and structure first, or your text passed through as-is if it is already clean. Add comment and Change status on the Jira rows keep an existing escalation moving without opening a browser tab. Every write is logged into the account session.
- RenewalQBR prep from the record, not from memoryWhen the QBR or renewal conversation comes around, Copy recap turns the whole account session, summary plus every logged entry, into paste-ready markdown: the raw material for the deck is the actual history of the account. Need one number off the customer's usage dashboard? Capture & ask lets you draw a region on the screen and question the screenshot directly.
Customer data needs boundaries
a chat tab doesn't have
In Khint the boundaries are structural, not policy. An Action only ever sees the text you selected, plus the active account session's compacted summary if you opted that Action in, and nothing else on your screen or disk. Account sessions live in a local database on your machine and are never synced to a server; what your CRM or your team gets is what you choose to paste from Copy recap. Gmail sends always show a preview behind a confirm step, so no AI-drafted email leaves without you reading it. And for actions that routinely touch customer text, a per-Action switch replaces email addresses, phone numbers, SSNs, and IBANs with placeholders before the model ever sees the text. What leaves is a choice you make per action, visible every time.
The four pieces of the toolkit
Account workflows, one page each
The parts of the loop, in depth: how each one works with real Khint features.
Common questions from customer success teams
What can a customer success manager actually do with Khint?
Select any text (raw call notes, a customer's angry paragraph, a half-written check-in email), hit Cmd+Shift+K, and run a saved AI Action on it in place: notes become a structured follow-up, a vague complaint becomes an engineering-ready escalation, a rough draft becomes an email in your voice. From the same palette you can pull a Gmail thread or a Slack channel into the account's memory session, send or draft the reply in Gmail with a preview before anything goes out, and file the escalation as a Jira or Linear issue. One shortcut, inside whatever app you were already in.
Does Khint integrate with my CRM?
Not directly. The connected tools are Jira, Confluence, Linear, Notion, Slack, and Gmail. For the CRM there is Copy recap: one click copies the account session, its compacted summary plus every logged entry (the pulls, the calls, the tickets filed), as clean markdown on your clipboard. Paste it into the account record, a QBR doc, or a handover note. It is plain text, so it works in any tool you can paste into.
How do I keep twenty accounts from blurring together?
One Memory session per account. Only the active session's compacted context is injected into the Actions you opted in, so a renewal email for one customer is never informed by another customer's escalation history. Sessions live in a local database on your machine, are never synced to a server, and switching accounts is one click on the Memory page. The app's sidebar shows a pale indicator while a session is active, so you always know which account context you are writing into.
Customer emails are full of personal data. What does the AI see?
Only what you explicitly act on: the text you selected, plus (only if you tick the option on that Action) the compacted summary of the active account session. Khint does not read your inbox, your other windows, or your files. For actions that routinely touch customer text you can also flip a per-Action redaction switch that replaces email addresses, phone numbers, SSNs, and IBANs with placeholders before the model sees the text. It is a pattern-based safety net, not a DLP product, but it keeps the obvious identifiers out of the request.
Is there a free plan?
Yes. The free tier includes 10 AI actions per day and 5 screen captures per day, no credit card. Paid plans start at €7/month: Pro at €29/month gives 100 AI actions a day, and every plan includes all the work integrations. Khint runs on macOS 13+ and Windows 10 22H2+.
Bring it to your next check-in call
Free with 10 AI actions and 5 captures per day. No credit card; it runs on your own machine, next to the inbox and the Slack sidebar you already live in.