Sanka Desk · AI-native help desk

The AI-native help deskthat resolves your IT issues.

Employees ask in Slack, Teams or email, and AI takes the request first. It answers from your own documents, finishes routine requests itself and previews every change before it runs. Changes with real impact wait for your approver, and what the AI can't finish goes to your IT team with the full context.

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

AI-native

AI takes every request first. Your team keeps the decisions.

In Sanka Desk, AI is not a feature added to a ticket queue. It is the first line: it reads every request, answers or acts within a fixed catalog of operations, and brings people in only where a decision is needed.

01

Every request answered first

The AI replies around the clock in Slack, Teams or email, from your own documents and with the source cited. No one waits for someone to be free.

02

Work done, not just logged

Routine changes such as group access, sign-outs and new accounts are made by Desk itself in Google Workspace, Okta and Sanka Flow, then read back from each system.

03

Rules the AI can't step outside

The AI only picks from a fixed catalog. Risk levels come from rules, approvals happen in chat, and most changes can be rolled back.

04

People where judgment matters

What the AI can't finish goes to your IT team with the full context, so nothing is asked twice.

What it takes on

The L1 requests that fill an IT team's week

Desk covers the whole first line, not one kind of ticket. Your IT team keeps the decisions; Desk does the work around them.

  1. 01

    Accounts and access

    Desk changes Google Workspace and Okta groups once the owner or a manager approves. Your IT team applies Slack channels and shared drives from the ticket.

    See how it works 
  2. 02

    Login recovery

    Desk signs people out of every session and lifts suspensions itself. Your IT team does two-step resets and passwords from the ticket. Desk checks who is asking, and a manager approves what needs it.

    See how it works 
  3. 03

    Joiners and leavers

    Accounts and groups for new hires; suspension and record hand-over for leavers. Your IT team adds licenses and Slack accounts from the ticket.

    See how it works 
  4. 04

    How-to questions

    Answers from your own documents and your environment, with the source cited in every reply.

    See how it works 
  5. 05

    App settings

    Roles, saved views and lists in Sanka Flow, and failed syncs retried. Licenses and settings in your other apps go to their admins from the ticket.

    See how it works 
See every action Sanka Bot takes, with prices 
#it-help

Maya Chen10:02 AM

Daniel joins Sales on Monday. Can you set up his account and add him to the sales groups?

Sanka DeskAPP10:03 AM

Here is the change. A new account needs your IT team's approval.

New joiner: Daniel ParkMedium
Google Workspace
Create account
Groups
sales@, sales-apac@
Sanka Flow
Invite · Staff role

Ken Ito10:14 AM

Approved.

Applied and read back · Undo available

One request, previewed before it runs and recorded after.

ITSM

Tickets, changes and knowledge in one place

Your IT team works here too. They can assign and resolve tickets and plan changes, with a record of who did what.

01

Free ITSM

Tickets, change management and knowledge for free, with 1,000 Sanka Credits to start and no card.

See how it works 
02

IT service desk

One queue for every request, where your IT team assigns, resolves and plans changes.

See how it works 
03

Change management

Previews, risk levels and approvals on every change, and rollback where it can be undone.

See how it works 
04

Knowledge management

Answers that name their source, from your documents and IT environment.

See how it works 

RevOps

Requests from your revenue teams, in the same place

Sales and marketing ask where they already work. Desk changes lists and owners in Sanka Flow itself, and your CRM admin does the work in HubSpot or Salesforce from the ticket.

01

RevOps Desk

What Desk takes on for revenue teams, who does the work and what stays in Sanka Flow.

See how it works 
02

Lead sourcing

Desk's AI builds the list, your sales lead checks it, and the leads are saved in Sanka Flow. Off until Sanka turns it on for your workspace.

See how it works 
03

Workflow building

Automations in HubSpot or Salesforce, agreed with your CRM owner, then built and tested.

See how it works 
04

CRM settings

Fields, pipelines, users, roles and seats, and bulk fixes such as duplicates.

See how it works 
05

Sales lists and owners

Who holds a company, a rep's list and a weekly check, run by Desk in Sanka Flow.

See how it works 

How it works

From a message to a verified change

  1. 01Employee

    In Slack, Teams or email

    Ask where they already work

    No portal to learn. Employees ask from the chat or email they already use.

  2. 02Desk AI

    Automatic reply

    Match it to the catalog

    The AI maps the request to an operation in a fixed catalog and previews exactly what would change.

  3. 03Your approver

    One tap in Slack

    Approve only what matters

    Access grants and higher-risk changes wait for the right person. Routine requests do not.

  4. 04Sanka Desk

    After any approval

    Apply, check, report

    Changes apply all at once or not at all, are read back from each system, and the employee hears when it is done.

Built not to break things

AI that can only do what the catalog allows

What you are buying is an IT desk that does not break things and cannot be talked into the wrong change. So the safeguards are the product, not an add-on.

What Desk does

  • Previews every change before it runs
  • Sets the risk level from fixed rules for each operation; the AI can raise it, never lower it
  • Applies all of a change or none of it
  • Keeps a tamper-evident record of every step

What Desk never does

  • Runs an operation that is not in the catalog
  • Resets someone else's password or MFA without their manager's approval
  • Follows instructions hidden in emails, records or documents
  • Uses your data to train AI models

Rollback built in

Desk records the earlier state before a change runs, so most changes can be undone from the ticket. Some cannot, such as signing someone out. Protective steps for leavers are never rolled back on their own.

Approvals in Slack or the console

Approvers see the previewed change and approve it with a button in Slack or from the console. An approval covers that exact change and expires after two business days.

Stop switches

A workspace admin can stop automatic changes for your company and restart them. Sanka can also stop them per operation, for your company, or everywhere at once.

Knowledge base

Answers that cite your own documents

Desk keeps a knowledge base for your company: a map of your systems and how your team does things. Every answer names its source, and drafts from resolved tickets are reviewed before they are used.

Your environment first

When a document disagrees with how your systems are actually set up, the system map wins and the conflict goes to review.

Kept to your company

Each company's documents, map and history are separate. Nothing is searched across customers.

Grows from real tickets

Requests your IT team resolves by hand become reviewed drafts, so the next one can be answered.

Getting started

Connect a chat channel and your directory

Desk works on its own. Connect where employees ask (Slack, Teams or email) and your directory (Google Workspace, Okta or Microsoft 365), then add business apps as you need them.

Works with

  • Slack
  • Microsoft Teams
  • Google Workspace
  • Okta
  • Microsoft 365
  • Sanka Flow
  • HubSpot
  • Salesforce
  • CloudTalk
Who makes the change in each app 

Nothing new for employees

Employees keep asking in the tools they use today. Your IT team works tickets in the Desk console.

Least-privilege access

Google Workspace, Okta and Microsoft 365 connect with only the permissions each operation needs. Changes in Sanka Flow run under a named admin and are all on record.

Every change on record

Search the change history, export it as CSV, and see what was resolved and why in the console.

Moving systems with Sanka

Desk knows your new setup from day one

If Sanka migrates your apps, Desk starts from the migration's map of your environment, so questions after go-live are answered from what was actually built. Desk does not require any other Sanka product.

See app migrations 

Questions

Which systems does Desk work with?

Requests come in from Slack, Microsoft Teams and email. Teams follows Microsoft's documentation and has not yet run on a customer's tenant. An email can't prove who sent it, so a request by email can get an answer, and any change goes to your IT team. Desk makes changes itself in Sanka Flow and, once your directory is connected, for accounts, groups, suspension and sign-out in Google Workspace and Okta. It also makes them in Microsoft Entra ID, where its actions follow Microsoft's documentation and have not yet run on a customer's tenant. In Slack, HubSpot, Salesforce and CloudTalk, your own admins make the changes from the ticket. More actions move to Desk in order of demand.

Does Desk handle laptops and devices?

Desk keeps an IT asset ledger of PCs and other equipment and who holds them, entered by hand or from Sanka Monitor's agent. It does not manage devices: there is no MDM, remote lock or wipe. Networks, on-site support and security incident response are outside Desk.

Do we need another Sanka product?

No. A Desk contract covers everything from taking a request to resolving it. Sanka Monitor, app migrations, Sanka Flow and Sanka Cloud are optional connections.

How is Desk different from Sanka Flow?

The line is the system the work touches. Work outside Sanka, such as in HubSpot or Salesforce, and every account or permission belong to Desk. Changing a rep's list or an owner in Sanka Flow can go through either: Desk with people and approvals, or Sanka Flow by your team or Sanka AI. Sanka Flow's own definitions, processes and plans, such as how revenue is defined, stay in Sanka Flow, as do finance and procurement requests such as a supplier's bank details.

Can employees ask Desk to buy software or a laptop?

Desk does not make purchases. Software and hardware purchases go from request to approved purchase order in Sanka Flow's IT Purchasing.

Who handles what the AI cannot finish?

Your IT team. A ticket the AI stops goes to the least busy person who can work every ticket, your IT approvers first, with the full context so nothing is asked twice. Sanka's staff don't work your tickets. The AI replies around the clock.

How is Desk priced?

Only for the work Sanka Bot finishes, paid in Sanka Credits. Every workspace starts with $10 in free credits, with no card. After that, each action that changes a system is $1 per person, and a request with several actions, such as onboarding a joiner, pays the sum. An answer from your knowledge that resolves the request, or an account check, is $0.10. There is no base fee and no seat fee. Actions that change nothing, fail or are rolled back, and work your IT team does, cost nothing. These are the standard prices. Enterprise is quoted.

What data does the AI see?

Only what the operation needs, with personal field values masked. Desk uses AI providers under contracts that neither train on nor retain your data.

Which languages does Desk support?

Japanese and English. A request in Japanese gets a reply in Japanese, and a request in any other language gets a reply in English.

Hand your L1 requests to Sanka Desk

Start now and ask your first question, or tell us how many employees you support and which tools they use, and we will show you Desk on your own setup.