The Public sector pack

Everything in the pack,
and everything it will not do.

The CRM fields and stages that follow every call, what it connects to, and what it never says. Why any of it matters is on the Public sector page.

Public sector — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

This trade pack is built to order. Below is the design we switch on for you: the fields, stages and never-say list are drafted, so with your price list and hours it can be switched on within days.

Inquiry type and responsible teamThe question, word for wordIn person or by proxyDocuments listedTransferred or callback loggedPreferred callback time

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Public sector.

Logged→Classified→Answered from guidance→Routed to the team→Outcome reported
PipelinePipelineLogged4Classifie3Answered 2Routed to1Outcome r1

What it will not do

Not a setting you switch on and off. These are blocked when the Public sector answering is built; anything that touches them goes to a person instead of being answered.

  • It never predicts a ruling.Whether a permit is granted or an allowance is paid is decided by the responsible team after checking the requirements. The relocation-allowance question goes to the residents’ team.
  • It never interprets the regulations.How a rule applies to a resident’s case is the department’s judgement, not the AI’s.
  • It never looks up personal records.Anything that requires identity verification is not done on a phone call.
  • It never answers for another department.If it does not know, it says so and routes the call. Sending a resident the wrong way is worse than not answering.

This page is the list; the argument is on the other one. What kind of call comes in at night, what a missed one costs, and why a machine must not say certain things are written on the page this pack came from.