Sanka Bot · Sanka Desk

Every team's requests,answered in Slack and Teams.

Employees ask Sanka Bot where they already work. It opens a numbered ticket, answers from your own knowledge, makes routine changes with approval where it's needed and replies in the same thread.

$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

Daniel starts on Monday. Please make a Google account and add it to sales@.

1 reply

Lucas Meyer10:03 AM

I left my laptop on the train. Please sign me out of Google everywhere.

1 reply

Priya Nair10:14 AM

What's the status of #123?

1 reply

Requests as employees send them to Sanka Bot

What Sanka Bot does with Sanka Desk

Takes the request where it's asked

In Slack, people mention Sanka Bot in a channel or send it a DM. In Teams, where the app is called Sanka, they write to it in a chat or mention it in a channel. It opens a numbered ticket, replies in the same thread and gives a request's status when asked about its number.

Answers from your own knowledge

Answers come from your company's registered documents, with the source. Answering a question changes nothing.

Makes routine changes

Low-risk changes run at once, such as signing yourself out. Medium-risk changes wait for one approver and high-risk changes for two people at your company. Desk makes the change itself in Google Workspace, Okta, Microsoft Entra ID and Sanka Flow; in the other apps your IT environment lists, your own people do it from the ticket.

Brings the approval to the approver

In Slack, approvers get a DM with Approve and Reject buttons and an email, with reminders until they decide. Teams has no approve buttons, so approvals for Teams requests happen in the Desk console.

From a message to a finished request

  1. 01Employee

    In Slack or Teams

    Ask

    They write what they need in their own words, in a DM, a channel or a Teams chat.

  2. 02Sanka Bot

    Automatic reply

    Open a ticket and reply

    It opens a numbered ticket and replies in the same thread with an answer, or with the change it plans to make.

  3. 03Your approver

    When it's needed

    Approve

    Routine requests go straight through. Others wait for an approver, who decides from a Slack DM, by email or in the Desk console.

  4. 04Desk

    After any approval

    Finish and report back

    Desk makes the change or hands it to your own people, then reports in the same thread. In Slack the person confirms or reopens with a button; in Teams they reply.

How it works in each place

Slack and Teams take the same requests. Approvals and closing a request work differently in each.

Asking
Slack: mention Sanka Bot in a channel or send it a DM. Teams: write to Sanka in a chat or mention Sanka in a channel. Replies come in the same thread.
Approving
Slack: a DM with Approve and Reject buttons, plus email, with reminders. Teams: in the Desk console.
Closing a request
Slack: Confirm and Reopen buttons and a satisfaction rating. Teams: the person replies to confirm or reopen.
Ticket systems
Jira, Zendesk, Freshservice, Freshdesk, ServiceNow and HaloPSA. Desk reads the queue every minute and writes comments and status back.
Missed SLAs
Desk sends the person in charge a Slack DM when a request breaches its SLA.
Sanka Desk
The AI help desk behind Sanka Bot: tickets, approvals, your IT environment and knowledge in one console.

What to expect

  • Teams has no approve buttons. Approvals for Teams requests happen in the Desk console.
  • Teams and Desk's Microsoft Entra ID actions follow Microsoft's documentation and have not yet run on a customer's tenant.
  • Sanka Bot doesn't change Slack accounts or channels. The person in charge at your company does.
  • Where a person makes the change, there is no automatic read-back or rollback. They record what they did on the ticket.

Works with

  • Slack
  • Microsoft Teams
  • Google Workspace
  • Okta
  • Microsoft Entra ID
  • Sanka Flow

Sanka Bot for Sanka Flow

Members ask about deals, invoices and orders where they already talk, update records from chat and run workflows after a preview. In Slack, approvals and sales updates come to them.

Sanka Bot for Sanka Flow 

Sanka Bot for Sanka Migrate

Ask Sanka Bot where a migration stands, for its report or for what's waiting for review. For anything that needs a person, Sanka sets up a support channel with you, and Sanka's migration team answers there.

Sanka Bot for Sanka Migrate 

Sanka Bot for Sanka Monitor

On the days and at the time your admin sets, Sanka Bot posts what needs doing about your accounts, person by person, and mentions everyone listed. With Sanka Desk, a fix can be asked for in the same chat.

Sanka Bot for Sanka Monitor 

Sanka Bot for Sanka Cloud

Engineers ask Sanka Bot where a run stands, what it produced and what it used, and get the answer in the same conversation. Sanka Bot reads runs; it doesn't start, stop or deploy anything.

Sanka Bot for Sanka Cloud 

Frequently asked questions

Can approvers approve from Teams?

Not with a button. Teams has no approve buttons, so approvers use the Desk console. In Slack, they approve from a DM.

We already take requests in Jira or ServiceNow. Do we have to switch?

No. People keep filing there. Desk reads the queue every minute, answers on the ticket and writes the status back. This follows each vendor's documentation and has not yet run on a customer's site.

How does someone check on a request?

They ask about its number in the same chat, for example "What's the status of #123?", and Sanka Bot replies with where it stands.

What happens when Sanka Bot can't make the change itself?

It puts the request and the steps on the ticket for your own people, and says so to the person in the same thread.

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.