HomeGovernment
Constituent service for counties, cities and utilities
Residents call, text, email, chat and fill in forms. Each one lands on a single case, is answered from the pages and documents your departments approved, reaches the right team the moment a person is needed, and leaves a record an auditor can verify. Built for public accountability from the first line of code.
What an agency gets
Everything a service counter needs, without a new system of record
Serviceplane sits beside what you already run — your CAMA or billing system, Microsoft 365, SharePoint, your identity provider, your phone carrier — and makes them answer as one desk.
One case for every resident, across every channel
A phone call, a text, an email to a shared mailbox, a chat on your website and a web form all open or continue one numbered case. A resident who calls back inside a short window continues the same case; a reply to a solved email reopens it. Nobody repeats themselves and nothing is filed twice.
Channels · CasesProperty and account records, with identity verification first
A read-only replica of your property or account records is kept in Serviceplane by a small on-premises agent that only ever makes outbound HTTPS calls — works with Postgres and SQL Server replicas or a CSV export. Every record links back to your system of record.
On public channels the assistant states record data only after the person proves who they are with what the record already holds (last name, ZIP, phone). Five failed attempts lock the session. Staff see records in their own workspace without the gate.
Records · IdentityMicrosoft 365 shared mailboxes and SharePoint, as they are
Each department's shared mailbox becomes an email channel through Microsoft Graph — no MX or forwarding changes, replies go out as the mailbox and thread correctly. SharePoint site pages and document libraries are indexed with their permissions: a page only certain groups can read only answers those groups.
Connectors60 languages, on every channel
Residents write or call in any of 60 languages. The language is detected on the first message, call or email and the assistant answers in it; hand-off wording, receipts and closure notices are set per language, the chat widget follows the resident's language, and a person's preferred language is kept on their contact record so staff see it.
60 languagesAccessibility is a test, not a claim
The public chat widget, the hosted forms and the staff workspace run WCAG 2.1 A/AA checks in continuous integration, and every colour pair is measured against the 4.5:1 and 3:1 bars. A VPAT is available. Text follows the reader's own font size; the chat panel works at 320 pixels wide.
WCAG 2.1 AA · Section 508Staff sign in through your directory
Entra ID, Okta or any OIDC provider. SCIM provisioning creates and removes staff from your identity provider; deactivation stops access at once and keeps every case attributable. Serviceplane stores no passwords for your staff.
SSO · SCIMRetention, legal hold and records requests
A retention policy per channel removes message content on schedule while the record of what happened — who, when, which case — is never touched. A case under legal hold is skipped by every purge. One call exports a whole case, chat turns, emails, texts, notes and its audit trail, as one file for a records request.
Retention · Public recordsAgent assist inside the contact center you already have
For utilities and larger agencies on Genesys Cloud: the same approved knowledge surfaces suggestions to the representative during the call, with a secure pause that drops audio and transcript while card details are read. After-call summaries and wrap-up codes are drafted for the rep to approve; nothing is written to your billing system without that approval.
Genesys · Agent assistShadow mode until your own numbers say go
Each channel runs silently first: the assistant answers every question to a private log, staff keep answering residents, and a reviewer compares the two. A channel goes live when reviewed accuracy clears the bar you set — 95% by default — and a go-live checklist derived from your actual configuration says what is still missing.
Go-live gateWhat it is worth
Estimate what your agency saves in a year
Two numbers you already know. The rest is arithmetic on stated assumptions, printed under the result.
Estimates based on a 65% AI deflection rate, 5-minute average resident call time, 7-minute average staff handle time, $5 average cost per resident interaction, and an 8-hour working day. Actual results will vary.
A conversation, end to end
What a resident sees, and what your staff see
The wording above is illustrative; a real answer comes only from the pages your Assessor approved.
Control
What your agency decides, and what Serviceplane will never do
Your agency decides
- Which pages, documents and SharePoint sites the assistant may answer from, and who approves them
- The wording of every greeting, hand-off and closure notice, per language
- Business hours, holidays and what residents are told after hours
- Which teams own which topics, and the plain-English policies that route or refuse
- Retention periods per channel, and which cases are on legal hold
- When each channel goes live, and the accuracy bar it must clear first
Serviceplane will never
- Answer from the open internet or a model's general knowledge
- State record data to an unverified caller or visitor
- Store a staff password, or merge two residents into one record on its own
- Edit or delete an audit event — the log is append-only and hash-chained
- Write to your CAMA, billing or contact-center system without a person's approval
- Send a marketing message; every outbound is a reply, a receipt or a notice you configured
Procurement questions
What evaluation committees ask
Does it meet Section 508 and WCAG 2.1 AA?
Can residents' records stay in our own system?
Do staff need new logins?
What happens after hours?
Can we see it work before it is public?
How is the audit trail kept honest?
Which languages?
Read next
How the answers and the record are kept honest
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.