The responsible officer keeps the decision; AI takes on the enquiries and paperwork that come before it.
Whichever route the entity takes, the responsible officer keeps the decision. The routes are those Sheba uses with enterprise clients: ChatSheba for questions from the public, Sheba Enterprise Platform entered through an evaluation, or a custom system built to the same standards as Sheba's products. ChatSheba and a custom system can run on the entity's own premises.
Everything this page describes is work Sheba performs for the entity that contracts it. None of it gives Sheba an official capacity, accreditation or mandate from any government.
The operating challenge in public administration
A transaction can pass through several departments before it is complete, while the same public questions return every cycle. Staff need knowledge spread across regulations, circulars and systems, and much of it may not leave the entity’s premises.
From the first enquiry to a signed-off transaction
- Public enquiries about procedures and required documents, answered from information the entity approves.
- Intake of requests and routing to the responsible department
- Internal regulations and circulars, searched by staff within their permissions.
- Routine correspondence, drafted for review and sign-off.
- Knowing where a transaction stands at each step as it moves between departments.
What the system can take on
- Answers public enquiries on procedures, requirements and documents from information the entity approves.
- Records the details an applicant gives, then routes the request to the department responsible for it.
- Lets staff search internal regulations and circulars within their permissions.
- Prepares drafts of routine documents and correspondence for review and sign-off.
- Refers anything that needs a decision or judgement to the responsible officer, with full context.
How Sheba delivers for public-sector entities
Running inside the entity’s own premises no longer decides the route: ChatSheba can be delivered there, and so can a custom system. What decides it is the process — where no existing product covers it, the route is a custom solution, built with the same Sheba technology, standards and implementation discipline as the products.
- See ChatSheba
Public-facing service: ChatSheba
Anything needing a decision goes to an officer. Before that, it answers public enquiries on procedures and documents in the entity’s approved terms.
- See Sheba Enterprise Platform
An AI environment for staff: Sheba Enterprise Platform
Entered through an evaluation. Staff reach the entity’s circulars and past decisions there, and agents prepare repeat work for review.
- See how AI agents work
Agents for administrative steps
An agent can prepare a draft reply, or confirm that a request has everything it needs, with the tools the entity grants.
- Explore custom AI engineering
A custom system on the entity’s premises
Able to run inside the entity’s own premises and infrastructure, it is built for one entity around its own process, to the standards of Sheba’s products.
Government routes and the Sheba products and layers they use
- ChatSheba, for the public-facing service.
- AI agents that work within the tools and approvals the entity sets.
- Enterprise knowledge, searched within each person’s permissions.
- Custom engineering that can run inside the entity’s own premises.
Data boundaries and human control
Every deployment has its limits written down first: what the system reaches, who can see its records, and when a case passes to an officer. Sheba claims no certification or accreditation.
- Per-deployment data boundaries
- On-premises delivery for ChatSheba and custom systems
- Access agreed at scoping
- Human escalation as a control
Delivery pattern
The route is chosen last. First comes the one task the system should take on, then the data it may reach and the officer who receives whatever exceeds its limits. Only then does it become clear whether a public-facing service fits, or an environment the entity’s staff work in, or a custom system on its premises.
How this pattern is set up
- Channels
- Public-facing channels or internal staff tools, depending on the route
- Systems it reads and writes
- the entity’s internal systems, by category
- Escalates to
- the responsible officer or the team the entity designates
FAQ