- Industry
- Insure AI
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Facilities Manager
- Code
- MGT-11
It logs workplace requests at the insurer's offices, claims centres and branches (repairs, cleaning, moves, access, equipment, safety hazards), sets their type and priority, and routes each to the right team or contractor with a target response time. Safety hazards go straight to the safety contact, and requests touching the secure areas where claim files, health records and payment cards are handled go to security first.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the facilities management system: the open tickets for the site, the contractor rota and the secure area register..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Facilities Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the facilities management system: it creates the ticket and routes it to the team or contractor. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The facilities guide: request categories and priorities, response times, contractor rota and spend limits, the safety reporting route, and the access rules for secure claims, records and payments areas.
Reads from
the facilities management system: the open tickets for the site, the contractor rota and the secure area register.
Acts in
the facilities management system: it creates the ticket and routes it to the team or contractor.
Hands back
An object with category, priority (urgent or routine), location, route_to (team, contractor or contact), respond_by (a date and time), secure_area (true or false), estimated_cost (or null) and note.
Asks a person when
A contractor job is above 750, off is false and a contractor is needed, or the request involves a secure area.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Urgent response (hours) | 4 | Urgent requests get a response within this. |
| Routine response (days) | 3 | Routine requests get a response within this. |
| Contractor job that needs approval (USD) | 750 | A contractor job above this needs the approver. |
| Dispatch contractors automatically | Off | When off, every contractor job waits for the approver. |
| Safety contact | Site Health and Safety Officer | Safety hazards go straight to this person. |
| Secure area contact | Information Security Officer | Access or contractor work in secure areas goes to this person first. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Route any safety hazard to Site Health and Safety Officer at once; it is never queued behind routine work.
- Any access request or contractor visit in a secure records, health claims or payments area goes to Information Security Officer first, and contractors are escorted.
- Set urgent requests to respond within 4 hours and routine ones within 3 days; anything stopping a claims centre taking FNOL calls is urgent.
- Dispatch contractors only when off is true and the job is at or below 750; otherwise ask the Facilities Manager.
- Never record health or claim details in the ticket.
See the Facilities Requests Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.