Your support tools, finally read as one
Kobal connects your helpdesk, CRM, billing and product notes, then sends what it finds to Slack, your tracker or back into the helpdesk. Nothing to migrate: your team keeps working where it works today.
Start with the tools you have
Connect your helpdesk first. Every tool you add after that gives Kobal more of the picture, and more places to send what it finds.
Helpdesks
Where your tickets live. Kobal reads them there, and nothing moves.
- ZendeskTickets in, tags and internal notes back on your rules.
- IntercomConversations and tickets in, notes back on your rules.
- HubSpotHelp desk tickets and inbox conversations, side by side.
- FreshdeskTickets in, with the SLA due dates your team works to.
- GorgiasTickets with the orders and refunds behind them.
- CSV importAny other helpdesk, read from an export.
Customers & revenue
Who is affected, and what they’re worth to you.
- HubSpot CRMPlans, revenue and renewal dates, with risk flagged on the record.
- SalesforceAccounts and renewals, with risk flagged on the record.
- StripePlans, payments and refunds, read as context.
- ShopifyThe orders and refunds behind e-commerce tickets.
Knowledge
What your customers are told, and what your team knows.
- Zendesk GuideHelp centre articles, checked against what customers ask.
- Intercom ArticlesHelp centre articles, with fixes drafted for your yes.
- NotionInternal docs and wikis. Also a place to send reports.
- ConfluenceInternal wikis, read as answers and context.
- Google DocsThe documents your team actually works from.
- Files and websiteUploads, links and your public site.
Product & engineering
What changed, and where the fix is tracked.
- LinearHand-offs as issues with the tickets attached. Kobal notices when they close.
- JiraHand-offs as issues with the tickets attached. Kobal notices when they close.
- GitHubReleases, lined up against when the tickets started.
- Release notesWhat shipped and when, so a spike can be tied to a release.
- Status pageKnown incidents, read as context for a spike.
- Product analyticsHow customers use the product, beside what they report.
Calls
What customers said out loud.
- AircallCall transcripts, read beside the tickets.
- GongCall recordings, read as context.
Where your team works
Where Kobal’s findings land. Slack first, and wherever else your team reads.
- Tickets
- 44 since Fri
- Accounts
- 12 on Pro
- Renewing
- 3 this month
- Trend
- Rising
“We were charged twice for the renewal, and the workspace still says our plan expired.”Review evidenceHand offAsk Kobal
- SlackAlerts with their evidence and buttons to act. Reply to ask Kobal.
- Microsoft TeamsAlerts in the channels your team already reads.
- EmailReports for the people who never open Slack.
- AsanaHand-offs as tasks, with the tickets attached.
- Helpdesk side panelShows agents the bigger problem behind the ticket they’re on.
- WebhookSend findings to anything that takes a webhook.
Your own agents
Kobal’s answers, for the tools and AI your team builds with.
- MCPAI assistants ask Kobal, and get the evidence with every answer.
- ClaudeAsk Kobal from Claude, through MCP.
- APIRanked problems, at-risk accounts and answers, as data.
- Command lineAsk Kobal from the terminal.
Connect it once. It keeps up.
Sign in to your helpdesk and Kobal sets up the rest, including the feed that brings new tickets in as they’re written. Every hour it checks again for anything the feed missed, so the counts you see are counts you can trust.
You decide what each source is for
Every connected tool gets its own row, with a switch for each job Kobal could give it. A call library can explain a spike without ever being quoted as an answer.
- ContextBilling, calls and release notes explain what changed.
- AnswersAsk Kobal only quotes the sources you let it quote.
- Write-backOff until you switch it on, and only where the tool accepts changes.
31 of 44 tickets about double charges mention Friday’s update. Kobal can’t read what changed in it.
- #8436“It started right after your update on Friday.”
- #8440“Since the new version, renewals charge twice.”
It asks for what it’s missing
When your tickets keep pointing at something Kobal can’t read, like release notes or a billing system, it suggests that connection. Each suggestion comes with the tickets that prompted it, so every tool you add closes a real gap.
Your own AI can ask it too
Kobal answers over an API, a command line and MCP, the way AI assistants call tools. Every answer carries the same evidence you see in the app, so nothing gets repeated without its proof.
Every connection, in plain sight
Each tool shows what Kobal can reach, when it last synced and whether it needs attention.
- AccessYour tools’ own sign-in.You connect through each tool’s sign-in, never a shared password, and Kobal stores the access encrypted.
- ChangesIt writes only where you’ve allowed it.A change in your helpdesk follows the rule you set for that kind of action, and is marked as coming from Kobal.
- StorageYour tools stay the source.Kobal keeps a working copy to read from, never the original. Retention, export and deletion are yours to set.
- Outside toolsThey can suggest, never approve.Every call uses a key with its own scope and limits, and shows up in a full log.
Questions, answered
Can't find what you're looking for?
Visit our Help Center.
Keep your tools. Add the answers.
Tell us your helpdesk, your CRM and where your team talks. We’ll show you what Kobal would read, and where it would send what it finds.
Get early accessWorks on top of the helpdesk you already use. No migration.