Sanka Bot · Ticket AI

Ask where you already work.Hear back in the same place.

Sanka Bot is one assistant that employees reach where they already work: Slack, Microsoft Teams, email, WhatsApp or LINE, ChatGPT or Claude, or the ticket system your company already uses. It answers from your company's own knowledge with sources, turns requests into tickets with the right approvals and reports back where the person asked.

$10 in free Sanka Credits to start, with no card. Then $1 for each action Sanka Bot runs on a system, with no base fee.

#it-help

Maya Chen10:02 AM

I need edit access to the Marketing shared drive.

1 reply

Lucas Meyer10:03 AM

Which of my deals close before the end of the quarter?

1 reply

Priya Nair10:14 AM

How far along is our HubSpot migration?

1 reply

What people ask Sanka Bot, wherever they work

What Sanka Bot does, wherever it's asked

Takes requests where people ask

In Slack, Microsoft Teams, email, WhatsApp and LINE, in ChatGPT and Claude, and in the ticket system your company already uses, such as Jira, Zendesk, Freshservice or ServiceNow. People ask in their own words and don't need to know which app a request touches.

Answers with sources

Answers come from the documents your company registers, and each one shows its source. A question none of them answers goes to the person in charge at your company. Answering a question changes nothing.

Approvals that follow the risk

Each request becomes a numbered ticket with a record. Low-risk changes run at once, medium-risk ones wait for one approver and high-risk ones for two people at your company. Desk makes the change itself in Google Workspace, Okta, Microsoft Entra ID and Sanka Flow; elsewhere your own people do it from the ticket.

Reports back, across every Sanka product

Results come back in the same thread, chat, email or ticket, and in ChatGPT and Claude people get the latest whenever they ask. Beyond service desk requests, Sanka Bot works with Sanka Flow, Sanka Migrate, Sanka Monitor and Sanka Cloud too.

From asking to hearing back

  1. 01Employee

    Wherever they work

    Ask

    They write what they need in their own words, in chat, in ChatGPT or Claude, or in your ticket system.

  2. 02Sanka Bot

    Automatic reply

    Answer or open a ticket

    A question gets an answer with its source. A request becomes a numbered ticket, and its record starts there.

  3. 03Your approver

    When it's needed

    Approve

    Low-risk changes go straight through. Others wait for one approver, or two people for high risk, who decide from a Slack DM, by email or in the Desk console.

  4. 04Desk or the person in charge

    After any approval

    Change and report back

    Whoever makes the change records it on the ticket. Chat, email and ticket systems hear back; in ChatGPT and Claude, the person asks for the latest.

Where Sanka Bot works

One row per place and per Sanka product. Each page says what Sanka Bot does there and what stays with people.

Slack
Ask in a channel or a DM and hear back in the thread. Approvers approve with a button
Microsoft Teams
Personal chats, channels and group chats. Approvals happen in the Desk console
Email
Answers by email with sources. Any change goes to the person in charge at your company
WhatsApp
Replies in the same chat. Approvals happen in the Desk console
LINE
Replies in the same chat, for staff in shops, on site and on the road
ChatGPT
A custom MCP server, where your plan and admin allow it. File requests, run Desk Actions after a preview and check your own
Claude
Connect Sanka under Connectors in Claude's Settings. File requests, run Desk Actions after a preview and check your own
Ticket systems
Jira, Zendesk, Freshservice and ServiceNow. Desk reads the queue every minute and answers on the ticket
Sanka Desk
Requests from every team, answers with sources and approvals that follow the risk
Sanka Flow
Ask about and update records, and run workflows after a preview
Sanka Migrate
Ask for a migration's status, its report and what waits for review
Sanka Monitor
A daily account security check, posted in a Slack channel
Sanka Cloud
Ask about a run's status, results, receipt and certificate

What to expect

  • Each place has its own limits, set out on its page. In Teams, approvals happen in the Desk console, and a request by email gets an answer while any change goes to the person in charge at your company.
  • Desk changes only what it is set up to change. The person in charge at your company does the rest from the ticket and records what they did.
  • In ChatGPT and Claude, people can't approve, answer Desk's questions or confirm a result, and aren't notified when a request changes. They ask again, or open the request in the Desk console.
  • Sanka Bot in Teams and the ticket system connections follow each vendor's documentation and have not yet run on a customer's tenant or site.

Works with

  • Slack
  • Microsoft Teams
  • Email
  • WhatsApp
  • LINE
  • ChatGPT
  • Claude
  • Jira
  • Zendesk
  • Freshservice
  • ServiceNow

Sanka Bot in Slack

Employees mention Sanka Bot in a channel or write to it in a direct message, and hear back in the same thread. When a change needs a decision, the approver gets it in a direct message and approves with a button.

Sanka Bot in Slack 

Sanka Bot in Microsoft Teams

Employees write to Sanka Bot in a personal chat, or mention it in a channel or a group chat, and hear back in the same place. Approvals happen in the Desk console. Sanka Bot in Teams follows Microsoft's documentation and has not yet run on a customer's tenant.

Sanka Bot in Microsoft Teams 

Sanka Bot by email

Employees write to your workspace's Sanka Desk address, or to the help address they already know, forwarded to it. Desk answers by email with its sources, and hands any change to the person in charge at your company, because an email can't prove who sent it.

Sanka Bot by email 

Sanka Bot on WhatsApp

For employees who already work in WhatsApp. They message Sanka Bot and hear back in the same chat, and each request goes through the same approvals and leaves the same record as one from any other channel.

Sanka Bot on WhatsApp 

Sanka Bot on LINE

For staff in shops, on site and on the road, who ask from their phone. They message Sanka Bot on LINE and hear back in the same chat, and each request becomes a ticket under the same rules as every other channel.

Sanka Bot on LINE 

Sanka Bot in ChatGPT

Employees add Sanka to ChatGPT once, as a custom MCP server, and sign in to Sanka in the browser. Then they ask ChatGPT to file a request, check one by its number or list the ones still open. Desk works each request like one from Slack, with the same approvals.

Sanka Bot in ChatGPT 

Sanka Bot in Claude

Employees connect Claude to Sanka once, with their own Sanka sign-in. Then they ask Claude to file a request in their own words, check one by its number or list the ones still open. Desk works each request like one from Slack, with the same approvals.

Sanka Bot in Claude 

Frequently asked questions

Do employees need a new app?

No. They ask in the chat, AI assistant or ticket system they already use. Your admin connects each place once, and in ChatGPT and Claude each person connects Sanka by signing in with their own Sanka account.

Which channel should we start with?

The one where employees already ask for help. If that's a ticket system, people keep filing there and Desk answers on the ticket. You can add places later, and every request lands in the same Desk console.

Is Sanka Bot the same in every channel?

The rules are. Answers come from the same knowledge, and every request gets the same risk rules, approvers and record. What differs is how people ask and approve: Slack has approve buttons, Teams approvals happen in the Desk console, email gets answers while changes go to the person in charge at your company, and ChatGPT and Claude can file and check requests but not approve them. Each place's page has the details.

What does Sanka Bot do beyond Sanka Desk?

It works with every Sanka product. Members ask about and update Sanka Flow records and run workflows after a preview, ask for a migration's status in Sanka Migrate, get Sanka Monitor's daily account check in Slack and read Cloud Runs in Sanka Cloud. Each product's page says where each part works.

Hand your L1 requests to Sanka Desk

Start now and ask your first question, or tell us how your employees ask for help today and we'll set Desk up with you.