Spaces

Hand-over notes from the agent to a licensing or regulatory officer

These hand-over notes show what an AI agent should tell an officer when it passes a chat from a regulated business, so the officer can act without asking the sender to repeat themselves.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

A handover is only as good as its note. If the officer receives "customer has a question", they must start again, and the sender feels ignored. A good note gives the sector, who wrote, what they asked, what the agent already said and what is time-sensitive. It should be short enough to read in a minute.

Fill in the officer or team and the sector, and use the notes as a pattern for your agent's instructions. Each one is written for a different kind of case. The agent should include only what the sender chose to share, and it should not add opinions about the case or its outcome.

Ruling question

For the [officer] at [business]: a sender asks whether they need a permit for a new vehicle under [sector]. I gave the published steps only. Please advise them directly.

Deadline at risk

To the [officer]: a sender on [sector] says their filing date is tomorrow and a document is missing. I explained the published process. Please contact them today if you can.

Complaint about a decision

For the [officer] at [business]: a sender is upset about a decision on [sector]. I acknowledged their frustration and said nothing about the outcome. Please reply personally.

Safety concern

URGENT for the [officer]: a sender reports an unsafe situation linked to [sector]. I gave our emergency instructions. Please respond straight away. Their words are in the chat below.

Breach or notice mentioned

To the [officer] at [business]: a sender mentions a notice about [sector] and asks what happens now. I did not comment. Please contact them with the right information.

What every handover note should contain

Five things make a note useful: who the sender is as they gave it, the sector, the question in their words, what the agent said, and any date that matters. Add urgency if there is a safety risk or a close deadline. Leave out guesses, and leave out any view of whether the sender is right.

The note also protects the office. It shows exactly what the agent told the sender, so an officer can correct anything wrong at once. Review a few notes each week and ask the officers whether they could act on them without going back to the sender.

A quick test for a good note

Read the note as if you had never seen the chat.

  • Can you tell who wrote and which sector it concerns?
  • Do you know what was said and what is still open?
  • Is it clear how urgent it is, and by when?

FAQ

How long should a handover note be?

A few lines. The officer can read the full chat if they need more. The note should answer who, what sector, what was asked, what was said and how urgent, and nothing beyond that.

Should the note include the sender's licence number?

Only if the sender chose to share it. It helps the officer find the file quickly, but the agent should not press for it where the question does not need it.

Can the agent mark a handover as urgent?

Yes, and it should for safety risks and close deadlines. Agree with your officers what counts as urgent, so the label stays meaningful and is not used for everything.

More free tools for economic program and regulatory offices

Read the guide: Answer licence, filing and inspection questions in chat, and leave every ruling to your staff.