IT · Colleague: Ivy

The service desk that gets smarter every week

Auto-resolve routine requests, route the rest with full context, and turn every approval into an automation for next time.

Phase 2 · Q1
Capability 01

One inbox for every channel

Slack, Microsoft Teams, employee portal, email, embeddable widget. Every request lands in one queue with a consistent shape, whether it started as a chat DM, a form submission, or a forwarded email. Duplicates dedupe on the requester + subject.
grounded answer · sources
answer

Priya’s Okta lockout can be cleared via self-serve MFA challenge — no IT intervention required. If MFA fails, escalate to IT on-call.

cited from
01
IT · Okta account lockout policy
runbook · updated 4d ago
02
HR · Emergency access procedure
policy · updated 2w ago
03
Ticket #48211 · priya · resolved
past ticket · similar match
Capability 02

Rich context on every ticket

The Context Graph enriches each ticket the moment it arrives — user, device, licences, groups, recent access history, current incidents. The Assistant sees the operational picture before it decides how to respond; the human agent sees it beside every reply.
approvals · pending 4
unlock okta account
priya.sharma · self-serve · read-only
denyapprove
refund $128.40
stripe · ord_A4b2c · manager approval
denyapprove
revoke prod IAM role
aws · role/analyst · step-up MFA
denyapprove
reset zoom SSO
kiran.mehta · self-serve
denyapprove
Capability 03

Learns from your team

Every human decision — categorise, route, approve, resolve — becomes a candidate playbook. Ivy suggests promotions when a pattern recurs (three similar tickets same day, same team lead approves each). Approve the pattern once; the fourth ticket runs on autopilot.
context · priya.sharma
priyateamon-calloktagithubworkday
Capability 04

Enforces your policy

Every write goes through your approval matrix — routed to the right reviewer per action type, with step-up MFA where the policy demands, escalation on deadline, delegates when the primary is out. Configure once in Approval Policies; reference from any playbook.
reports · this week
Auto-resolved
78.4%
+4.1 pt
Avg. loop time
11.4s
-2.1s
Approvals pending
12
-3
Coverage
94%
+1.2 pt
monsun
Capability 05

See how your service desk is performing

Live dashboards for automation rate, response time, resolution time, SLA compliance, workload per agent, first-time-fix rate, backlog trend. Slice by team, requester group, or ticket category. Weekly digest to leadership; monthly board-ready roll-up.
grounded answer · sources
answer

Priya’s Okta lockout can be cleared via self-serve MFA challenge — no IT intervention required. If MFA fails, escalate to IT on-call.

cited from
01
IT · Okta account lockout policy
runbook · updated 4d ago
02
HR · Emergency access procedure
policy · updated 2w ago
03
Ticket #48211 · priya · resolved
past ticket · similar match
Capability 06

Ivy, your IT Colleague

Named persona, avatar in Slack, signature on every reply. 20 pre-built IT playbooks ready to install (password resets, JIT access, device unlocks, group management, on-call escalation, license reclamation). Ivy speaks your runbook and reads your live directory.
approvals · pending 4
unlock okta account
priya.sharma · self-serve · read-only
denyapprove
refund $128.40
stripe · ord_A4b2c · manager approval
denyapprove
revoke prod IAM role
aws · role/analyst · step-up MFA
denyapprove
reset zoom SSO
kiran.mehta · self-serve
denyapprove
The BeforeQuery method

Visibility. Reasoning. Action.

Every playbook, every action, every answer follows the same three-beat rhythm — one that keeps every write behind evidence and every decision behind policy.

01

Visibility

Read the full context — who is asking, what they own, what they can access, what breaks if we touch it. Nothing acts on incomplete signal.

02

Reasoning

Match the request to a grounded answer or a playbook. Cite the source paragraph, weigh the risk tier, and route to the correct approver where policy demands it.

03

Action

Execute the write on your systems with an audit-log id, an entity list, and a rollback path. Confirm the outcome with the requester in the same thread.

How every request flows

From ask to resolution in one loop

Six stages every request travels. What changes is how many stages policy lets the agent execute without waiting on a human.

01
Request

In Slack, email, widget, MCP, or the helpdesk. Same voice, same context.

Slack · Teams · Zendesk · Widget · MCP
02
Retrieve

Grounded lookup against your knowledge with source paragraphs held aside.

Knowledge Studio
03
Reason

Read the Context Graph — who, what they own, what breaks if we touch it.

Context Graph
04
Approve

Route to the correct approver per policy. Reversible writes gated, destructive step-up.

Approval matrix
05
Execute

Act on Okta, Stripe, Workday, GitHub, or your own systems. Logged and attributable.

Actions runtime
06
Verify

Confirm the outcome with the requester. Feed the result back into future decisions.

Feedback loop
Watch it work

Password reset in the ticket queue → resolved in 8 seconds

Zendesk ticket, Jira Service Management ticket, direct Slack ask — same loop, same outcome.

slack · #it-help
live
$zendesk · #48211:I can't log into Salesforce, password reset please
·
ivy identify user: kiran.mehta · Engineer · SSO via Okta context.graph
·
ivy check policy: Salesforce SSO reset self-service allowed with MFA policy.matrix
·
ivy issue MFA challenge + trigger Okta password reset okta.reset#a4b2c
ivykiran:Reset link sent to your recovery email. Ticket closed. If stuck, I'll page IT.
resolved · 8.1s · zero human touches·audit#a4b2c · reversible

Same mechanism inside Slack, MS Teams, the widget, and MCP. The channel is a detail; the loop is the product.

Enterprise-grade by default

The controls your security team is going to ask about

SOC 2 Type II
audited annually
GDPR
EU data residency
HIPAA-ready
BAA available
SSO / SAML
Okta · Entra · Google
SCIM 2.0
auto-provision
Audit log
every write, traceable
Bring your key
AES-256-GCM at rest
Bring your model
Anthropic · OpenAI · self-host
Zero training
your data stays yours
Rollback
every write reversible
TLS 1.3
in transit
99.9% uptime
SLA on Enterprise

Frequently asked questions

Common questions about AI Service Desk

It can — many customers migrate off. It can also coexist: BeforeQuery handles the daily-driver ticket queue while ServiceNow stays as the CMDB and change-management system of record. Two-way sync keeps ticket state consistent.
Two things. First, the Assistant reads the Context Graph before it responds — it knows what the requester owns, what they have access to, and what breaks if it acts. Second, it actually executes: JIT elevations, group changes, device unlocks. Not a router, an operator.
Console's benchmark is 75-87% for IT tickets after 6-12 weeks of learning. Our early customers land in the 60-80% range on ITSM at 90 days with a well-covered Knowledge Studio and playbooks for the top-20 request types. Depends heavily on your handbook quality and how comfortable your team is with autopilot on writes.
Yes — that's the default. Every write action ships with an approval mode: autopilot for read-only, manual for writes, step-up MFA for destructive. Flip a specific action to autopilot only after you've watched it perform in Copilot mode. Simulation lets you rehearse against past tickets.
The unified inbox, Context-Graph enrichment on tickets, Ivy Colleague with 20 IT playbooks, approval chain support, live analytics dashboards. Change requests (P14) ship alongside. Broadcasts and whitelabel portal in Phase 3.

Run it on BeforeQuery

Book a demo and see what AI Service Desk does on your own data — usually within 45 days.