One address per workspace
Your workspace gets its own Sanka Desk address. Forward your existing help address to it, and employees keep writing where they always have.
Sanka Bot · 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.
$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.

Maya Chen10:02 AM
Where can I find the guide for the new expense tool?
1 reply

Lucas Meyer10:03 AM
Could you add me to the finance-team@ group?
1 reply

Priya Nair10:14 AM
The printer on the third floor keeps jamming. Who should I contact?
1 reply
Your workspace gets its own Sanka Desk address. Forward your existing help address to it, and employees keep writing where they always have.
Desk replies in the email thread, with the ticket number in the subject, so a reply finds its request even when a mail app loses the thread.
Desk leaves out the quoted thread and reads only what the person wrote this time. Automatic mail such as out-of-office replies and delivery reports is ignored.
By email
They write what they need, as they would to a colleague.
Automatic reply
A question gets an answer by email, with links to where it came from.
When it's needed
A request that needs a change reaches the person in charge at your company as a ticket, with the email and its files.
After any approval
They make the change, and their reply reaches the employee in the same email thread.
An answer needs no proof of who is asking. A change does, and an email can't give it.
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 SlackEmployees 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 TeamsFor 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 WhatsAppFor 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 LINEYes. Forward it to your workspace's Sanka Desk address. Employees keep writing to the address they know, and Desk's replies stay in the same thread.
Anyone can put someone else's address in an email's From line. So Desk answers questions by email, and a request for a change goes to the person in charge at your company, who can check with the employee first.
Desk replies to the address your directory holds for that person, never to a Reply-To address, so the answer reaches the real person. A forged email can't change anything.
Anyone can, but only people your directory knows get a ticket and a reply. Mail from anyone else gets no answer.
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.