HomeCompare · Citibot
Serviceplane vs Citibot
Citibot is a resident-engagement chat and voice product for cities and 311 agencies. Serviceplane is a full service desk for public agencies: every channel on one case, answers only from approved knowledge, records behind identity verification, staff inboxes on Microsoft 365, and an audit trail an auditor can verify.
In their words
What Citibot says it is
Citibot | AI Resident Engagement Solutions for Government Agencies
“Citibot’s AI chat and voice tools empower government agencies to provide 24/7 multilingual support — ensuring equitable, accessible service through multichannel delivery.”
From citibot.io, 2026-09-22. Their words, not ours; we keep this current and will correct it on request.
Where Citibot is a good fit
Cities and 311 agencies that want resident-facing chat and voice with broad language coverage, from a vendor focused on municipalities.
What we built differently
Where Serviceplane is different, stated as facts about Serviceplane
Each row is something you can check in a walkthrough. None of it is a claim about how Citibot works inside.
One case across phone, text, chat, email and web forms
A phone call on the organization's own number, a text, an email to a shared mailbox, a chat and a web form all open or continue one numbered case. Voice is not a bolt-on: the assistant takes the call itself, texts a link mid-call, and a call-back inside a short window continues the same case.
ChannelsYour records, behind identity verification
A read-only replica of property or account records with a link back to your system of record; on public channels the assistant states record data only after the person proves identity with what the record already holds. Staff see records in their own workspace.
Records · IdentityAn audit trail the customer can verify, not just read
Every action by the assistant or a person is an append-only event, SHA-256 hash-chained to the one before. A read-only auditor role, filters and CSV/JSON export, a verification call that names the first bad event, and a nightly export to storage you own with a digest ledger. How the record is built.
AuditAnswers only from approved knowledge, and a gate before go-live
Retrieval is limited to content a person approved; an approved answer card is returned verbatim; no matching source means the assistant abstains and offers a person. Every channel starts in shadow mode and goes live only when reviewed accuracy clears the bar you set (95% by default). How grounding is enforced.
Grounded · Shadow modeBuilt for the public sector's constraints
Microsoft 365 shared mailboxes and SharePoint with their permissions, single sign-on and SCIM from your directory (no passwords stored), retention per channel with legal hold, one-file case export for records requests, WCAG 2.1 AA tested in CI, 60 languages detected automatically. For government.
GovernmentA person is one hand-off away, and then the assistant steps back
Hand-off routes to the least-recently-routed available colleague inside published hours, or files the case for the right team after hours with the resident told when staff are back. Once a person has the conversation the assistant stops answering on it — no two voices in one thread.
Hand-offShortlisting
Questions from teams comparing the two
We're a county, not a city. Does that matter?
What about languages?
Where does resident data go?
Can we bring our history over?
Do you integrate with it?
Is it cheaper?
Can we try it without switching?
Read next
The three things every comparison comes down to
Bring a real resident question. We'll answer it from your own pages.
A workspace built from your public site in an afternoon, a conversation with a hand-off to a named team, and the audit trail that went with it.