Applications complete before they reach an officer.
The agent checks each licence application, permit or citizen request against the rule set, pulls registry data and asks the applicant for missing items. Officers see complete cases with the checks done.
What comes in
- Licence applications
- Permit applications
- Citizen requests
- Supporting documents
Decisions it makes
- Approve
- Request info
- Refuse
- Refer to inspector
What comes in
- Licence applications
- Permit applications
- Citizen requests
- Supporting documents
What the agent does
- 1Checks completeness against the rule set
- 2Pulls registry data
- 3Compares the application with the registry
- 4Requests missing items from the applicant
Decisions it makes
- Approve
- Request info
- Refuse
- Refer to inspector
A fixed list you define. The agent picks one, or hands over.
A worked example
Licence applications and citizen requests, checked for completeness.
Illustrative. In shadow mode, nothing executes until you switch the decision type on.
Arrives
A food-stall licence application arrives through the portal.
Look up
Pulls the business registration: active, address matches.
Check
Food-handling certificate expired last month.
Request
Asks the applicant for a current certificate.
Hand over
Certificate received. Sent to the officer, complete, with the checks done.
Writes to
Every connection also works as a tool the agent uses mid-case.
REST API and webhooks
Channels in · In and out
Direct database read/write
Always available · In and out
SharePoint
Channels in · In and out
Your case system and citizen portal.
What we measure
Four numbers, measured on your cases.
Measured in shadow mode on your data, before anything is switched on.
Share of cases handled without a person
Error rate on those cases
Time saved
Cost per case
Talk to us about this process.
Thirty minutes on one process and its numbers. If it fits, the next step is Discovery or two weeks in shadow mode.