Sanka Bot · Slack

Ask in Slack,and approve there too.

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.

$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

Please add me to the finance-team@ group.

1 reply

Lucas Meyer10:03 AM

How do I connect to the office Wi-Fi?

1 reply

Priya Nair10:14 AM

Please add me to #project-alpha.

1 reply

Requests as employees send them in Slack

How Sanka Bot works in Slack

Answers in the thread

Desk replies under the message it was asked in, so a request and everything about it stay in one thread. The person who asked can follow up there without mentioning Sanka Bot again.

Approvals with a button

The approver gets a direct message with what changes, why it needs approval and when the approval expires, and taps Approve or Reject. The approval covers only that exact change.

Private replies for sign-in problems

A reply about someone's sign-in goes only to them, as a message nobody else in the channel sees.

From a Slack message to a finished request

  1. 01Employee

    In a channel, thread or DM

    Ask

    They mention Sanka Bot and write what they need. They don't have to know which app it touches.

  2. 02Sanka Bot

    Automatic reply

    Answer or plan

    A question gets an answer with its source. A change gets a ticket number, and the thread says who needs to approve it and by when.

  3. 03Your approver

    When it's needed

    Approve in Slack

    The approver taps Approve or Reject in a direct message from Sanka Bot, or decides in the Desk console.

  4. 04Desk or the person in charge

    After any approval

    Make the change

    Whoever makes it records it on the ticket. The thread hears when it's done, and the employee can confirm it or reopen it with a button.

Where each Slack request goes

Desk answers and plans in the thread. Who makes a change depends on the app, not on Slack.

Every action in Slack, and who makes each change 
How-to questions
Desk answers in the thread from your registered documents, with the source
Access to groups and drives
The owner or the manager approves, with a button in Slack or in the console
New hires and leavers
One message from HR or the manager. Each change waits for the approval it needs
Sign-in problems
Replies go only to the person asking
Slack accounts and channels
The person in charge at your company, from the ticket
Integrations
Which apps Desk changes itself, and which your own people change

What stays with people

  • Accounts and channel changes in Slack are made by the person in charge at your company, from the ticket.
  • Where your admin allows people to approve their own requests, they do it in the Desk console with a typed reason, never with a Slack button.
  • By default an approval expires after two business days. Desk reminds the approver before then, and an expired request can be sent again with a button.

Requests also come in by

  • Microsoft Teams
  • Email
  • WhatsApp
  • LINE
  • The Desk console
  • Your own AI

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 

Frequently asked questions

Do employees have to use one channel?

No. Your admin can set up a channel such as #help. A request that mentions Sanka Bot in another channel or in a direct message also becomes a ticket, in its own thread, unless your admin turns that off.

Who can approve from Slack?

The approvers your IT environment names. Slack tells Desk who tapped the button, and Desk matches them by email address. The person a change is about can never approve it.

Can Desk add people to Slack channels itself?

Not today. A channel request becomes a ticket, and the person in charge at your company makes the change after the approval it needs.

What happens to files people send?

They stay on the ticket for the people who work it. Desk's AI reads only their names.

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.