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 →