Sanka Bot · ChatGPT

Any request,filed from 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.

$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.

ChatGPT

Maya Chen10:02 AM

Ask IT for a Zoom license. I start running webinars next week.

1 reply

Lucas Meyer10:03 AM

Aiko ([email protected]) leaves on Friday. Ask IT to remove her access.

1 reply

Priya Nair10:14 AM

Is #214 done yet?

1 reply

Requests as employees ask ChatGPT

What employees can do in ChatGPT

Files the request in the person's words

Access, accounts, a sign-in problem, a new hire or a leaver, an app setting or a how-to question. For a request about someone else, ChatGPT passes on that person's email. If the same request is sent again within the hour, Desk returns the first ticket instead of filing a duplicate.

Says where requests stand

Asked about a number such as #123, ChatGPT shows its state, who it waits for, any question Desk is asking and the latest messages, with a link to the request in the Desk console. It also lists the person's own requests, open ones by default.

Runs a Desk Action after a yes

For a change Desk can make itself, ChatGPT first previews the Desk Action: what will change, its risk, who approves and the Sanka Credits it uses. It files the ticket only after the person says yes. When no Action fits, it files an ordinary request.

Works as the person who connected

ChatGPT reaches Sanka with that person's own account, workspace and permissions. It reads only the requests they filed and the approvals waiting for them, and it can't approve or reject anything.

From a ChatGPT chat to a finished request

  1. 01Employee

    Once

    Connect Sanka

    In ChatGPT, they add Sanka as a custom MCP server with the address https://mcp.sanka.com/mcp, then sign in to Sanka in the browser and choose the workspace. Your ChatGPT admin may need to allow custom MCP servers first.

  2. 02Employee

    In ChatGPT

    Ask

    They ask ChatGPT to file the request, in their own words. ChatGPT files it with Desk and replies with the ticket number.

  3. 03Desk and your approvers

    After filing

    Work the request

    Desk handles it like a request from Slack or Teams. Low-risk changes run at once, medium-risk ones wait for one approver and high-risk ones for two people at your company. Approvers decide in Slack or in the Desk console, as usual.

  4. 04Employee

    Any time

    Check back

    ChatGPT isn't told when a request changes, so they ask again or open the request in the Desk console. Answering Desk's questions, confirming and reopening happen there.

What happens where

ChatGPT files and reads the person's own requests. Approving, answering and closing them stay in Sanka Desk, and the same connection also reaches Sanka Flow, Migrate and Cloud.

Approvals
The approver decides in Slack or in the Desk console, under the same risk rules as every other request
Desk's questions, confirming and reopening
In the Desk console, from the link to the request
Desk Actions
Every Action, and which ones Claude and ChatGPT can preview and run
Sanka Flow
Read and update records such as deals, contacts and companies, within the person's own permissions
Sanka Migrate
Read a migration's status, its report and what waits for review
Sanka Cloud
Read a run's status, results and receipt. Nothing starts, stops or deploys from chat
Sanka MCP guide
The hosted address, browser sign-in and permissions for AI clients
Sanka for ChatGPT
What each Sanka product does in ChatGPT
Integrations
Which apps Desk changes itself, and which your own people change

What to expect

  • ChatGPT can't approve, answer Desk's questions, confirm a result or reopen a request. Those happen in the Desk console, or where your approvers work.
  • ChatGPT isn't notified when a request changes. The person asks again or opens the request in the Desk console.
  • Only people your directory knows, with their own Sanka account in the workspace, can file requests this way.
  • In a workspace without Sanka Desk, the answer says clearly that Desk is not enabled, and nothing is filed.

Requests also come in by

  • Slack
  • Microsoft Teams
  • Email
  • WhatsApp
  • LINE
  • Claude
  • The Desk console

Sanka Bot

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.

Sanka Bot 

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 

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 

Frequently asked questions

What can ChatGPT see of our requests?

Only the requests the connected person filed and the approvals waiting for them, in the workspace they chose, within their own Sanka permissions. Other requests can't be found.

Can ChatGPT approve a request?

No. The connection has no way to approve. An approver can ask ChatGPT for the approvals waiting for them, each with a link to its approval page, and decides in Slack or in the Desk console under the same risk rules as every other request.

What happens when someone disconnects?

Sanka checks the connection on every call, so disconnecting takes effect at once, and ChatGPT can no longer file or read requests. Requests already filed stay in Desk, and the person can follow them in the Desk console.

What does our ChatGPT admin need to do?

Make sure custom MCP servers are available on your ChatGPT plan, and allow them if your settings require it. Each person then adds Sanka with the address https://mcp.sanka.com/mcp and signs in to Sanka in the browser. No API key goes into ChatGPT.

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.