Deployment Checklist
Use this page as your checklist for bringing Serval live in your organization. Work through the steps in order — each links to the detailed setup guide for that area.Have self-hosting requirements? Read the Self-Hosting Options page first.
Go-live checklist
Choose your front door
Decide where employees reach Serval — Slack
(channels and direct messages),
email, or
Microsoft Teams. A web portal is
available automatically. See Channels
for the full list.
Employees can reach Serval through at least one channel.
Connect your core integrations
Connect your identity provider, communication tools, device management, and any
existing ticketing or other systems you want Serval to work with. After
connecting each app, open its Settings → Sync History to confirm syncs are
completing cleanly.
- Browse integrations and review Sync History
- Connect your identity provider (Okta, Microsoft Entra, Google Workspace, Rippling)
- Device management — Jamf, Kandji, and Mosyle
Each core integration shows recent, successful syncs.
Configure ticketing
Set up the building blocks, then use them to route work:
- Categories, labels, priorities, and statuses
- Schedules and SLAs
- Assignment rules, built from the items above
New tickets are categorized, prioritized, and routed automatically.
Install workflows
Automate common requests. Install pre-built workflows
for your connected apps, or build your own.
Browse examples by integration
for ideas.
Your highest-impact requests have a workflow in place.
Populate the Knowledge Base
Give the agent reference material to answer from:
connect a documentation source
(Notion, Confluence, Google Drive, SharePoint, ServiceNow, and more) or add a
custom ingestion workflow.
Knowledge is what the agent knows; skills
are how it acts.
The agent can answer questions from your own content.
Test before launch
Send representative requests through your front door and confirm routing, answers,
and workflows behave. At a minimum,
submit a test ticket, verify user sync, and run a test automation.
An end-to-end request works, from submission through resolution.
Frequently asked questions
Why do some pages — or parts of a page — get stuck loading?
Why do some pages — or parts of a page — get stuck loading?
This usually means a security proxy or WAF on your network is buffering or
inspecting Serval’s streaming responses, so the live part of a page never loads.
See Streaming pages behind a WAF or proxy
for the fix.
See also
- Day 1 setup — the guided quickstart companion to this checklist.
- Self-Hosting Options — choose a delivery model if you’re running Serval yourself.