Your operations, run by an agent.

An AI agent on the systems you already run. It answers and acts for your customers, states only what your system says, and keeps a record of everything it does.

Talk to a live agent Talk to us

Wherever your customers already are.

What changes

The asking comes off your people.

Most of what an office answers all day is a question the system already knows the answer to. The agent answers it, and does the next thing, without anybody in the middle.

Answers at nine at nightA parent asks what they owe on WhatsApp and gets the balance from the ledger.
Applications finished, not abandonedA prospect applies in a conversation. Admissions receives a complete record.
A busier term with the same officeStaff find a student, the arrears list or this week's fees by asking from a phone.
A record a board can readAsked, looked up, done, refused - every turn on the trail. Months later it is a document.

Why it is safe to say yes

Three promises, kept by the system, not by the model.

It states only what your system says.A figure it did not get from your records is refused on the way out. It says so rather than guess.
It acts only with a person's yes.Anything that changes a record is read back in exact terms, and happens once, on one confirmation.
It forgets nothing it did.Every question, lookup, action and refusal is a run your operator can open.

How it is used

One agent, on every door your customers use.

On your website

A visitor asks in their own words and gets the answer, the right page, or the demo booked - by the agent, not a form.

edu.britelink.io/talk →

On WhatsApp

People message the number they already have. The agent knows who is asking, and answers from the register.

Inside the portal

A student asks for the timetable, the exams, the work due - then studies: the agent teaches from the course's own chapters and marks the attempt.

school.britelink.io/student →

In your team's tools

The same agent from a script, a terminal or an AI assistant, on keys you issue and revoke. One wire, one set of rules.

What it is made of

Rules at the bottom, doors at the top.

Five layers. The one that decides what is allowed depends on nothing and is tested on its own; everything above it adds a way in, never a way around.

The kernel

Pure rules, no dependencies. What exists, who may ask, what a write must read back.

The service

Runs a turn: the cheap answer first, the model only where it is needed, every call through the kernel.

The wire

Five operations, described once, so nothing drifts between the ways in.

Your system

Answers four questions: who is this, what would this do, do it, send a code.

The surfaces

Website, WhatsApp, portal, your team's tools. Thin on purpose: the next one is a week.

Connecting

Your system does not need replacing, or a secret pasted into it.

It answers four questions and knows Mandate's address. Mandate signs every call with a key it publishes, so there is nothing to paste per deployment and nothing to rotate by hand.

Your records stay where they are. Four endpoints, no migration.

Where it runs today

Our own schools first.

BriteEducation books its own demos. The School of Technology takes applications in a conversation, answers on WhatsApp, and tutors inside the student portal. Every claim here is one of those deployments doing it.

Run your operations in a conversation.

Connected to your own systems, bounded by what you authorise, accountable for every action it takes.

Tell us what your team spends its day answering. We will tell you what an agent can take and what it would cost.

Talk to us Talk to a live agent