Answer the citizenwithout sending them back to the queue.
A birth certificate, a tax notice, a procurement file: the agent finds the request, checks the documents, says where it stands and prepares what comes next. The decision stays with the public officer, on a trail your ministry and your auditors can read back.
Agents are written bythe people who know the file.
If every process has to go through a central technical team, the queue moves to a different desk — it does not go away.
The autonomy covers the substance of the work. Permissions stay declared and approved.
The department describes, Studio assembles
A department head explains what needs to happen, in their own words. Studio turns it into a readable process — the steps, the sources consulted, the approvals — without a line of code.
The supervising body keeps control
What an agent may read and do is declared, then approved before it goes live. A department can write its own process; it cannot grant itself an access right.
IT connects it once
The connection to the civil registry, to public finance or to mobile money is made once by your technical teams, then reused by every entity. They are not called back for each new process.
The processeswe take on first.
Citizen desk, revenue, procurement and internal requests.
One service put into operation with its approvals and its audit trail, then the next.
Citizen desk
Answers requests for certificates, attestations and appointments, says what the file is missing and where it stands, in French and in the languages your citizens speak.
SMS
Revenue and collection
Finds a notice, explains an amount, reconciles a mobile money payment and chases what is still owed. The posting waits for the accountant's approval.
Wave
Procurement and suppliers
Answers bidder questions on the tender documents, follows execution and flags payment delays that are drifting.
SharePoint
Internal staff requests
Answers questions on procedure, status and payroll by citing the applicable text or circular, with each person's access rights respected.
Wired into whatyou already run.
Connect a source once. Agents read, act and write according to the access rules you define, including in line-of-business applications with no public API.
MTN MoMo
SharePoint
Connections to your systems are defined with your teams and your supervising ministry before the first deployment.
See all integrationsWhat we putin front of those processes.
The foundation is the same for everyone. Your procedures, your systems and your approvals are what make the difference.
Jen Works
Internal requests from public officers, resolved on the spot or passed on with their context.
See the productJengo Studio
The specification that declares what an agent is allowed to do, approved before it goes live.
See the productThe questionswe get asked.
01Can citizen data stay inside the country?
Yes. Deployment happens in your sovereign cloud, in your data centres or in the region you name, and the keys stay yours. Your data is never used to train a shared model. See sovereignty
02What about citizens without a smartphone?
The same agent answers by SMS and on the phone, not only on WhatsApp or the web. A public service cannot require a data plan to be reachable. See channels
03Who is answerable if an agent gets it wrong?
The digital agent prepares, the public officer decides. Acts that bind the administration go through the approvals you define, and every step is logged with its author, replayable months later.
04How does this fit a public procurement process?
The platform is installed on your side and operated with your teams: scope, hosting, reversibility and training are defined during scoping, before the tender, so the specification describes what you actually want.
Public servicethat answers first time.
Thirty minutes to scope the process, the systems and the approvals. Or write to us at [email protected]