Built Logic

See what AI can do

Reactive fault call to first-time fix and invoice

We take off your hands: logging fault calls at any hour. Suggesting the right engineer. Watching response times. Finding unbilled extras on each call-out.

You get: each fault logged. A suggested engineer for your controller to confirm. A warning before a response time is missed. Each call-out checked before you bill.

Get a price for this

Or check first: Are we ready for AI?

The problem

We breach response times. We send engineers back twice for the same fault.

How the steps join up

It starts when: a client reports a fault by phone, email or portal.

  1. Answer out-of-hours fault calls, log them and wake the right on-call engineer

  2. Read reactive job requests from emails and client portals and log them ready for dispatch

  3. Suggest the right engineer for each job using skills, accreditations, location and van stock

    Your team checks and decides at this step.

  4. Warn the service team before contract response and fix times are breached

  5. Answer engineers' fault-finding questions from manuals and past jobs

  6. Turn engineer notes into customer-ready service reports

  7. Code each finished repair to the schedule of rates before it is invoiced

  8. Find unbilled call-outs, overtime and materials on completed reactive jobs

  9. Find why reactive jobs need a second visit

What you end up with: Faults are logged at any hour, the right engineer is sent before the SLA is breached, engineers get help finding the fault, and every call-out is billed and learned from.

Who signs it off: Your controller confirms who goes to each job. Your service manager signs off any exception on billing.

What it needs to work

  • Engineer skills and location data
  • A job history

If those aren’t in place yet, you’ll hear that before anything gets built.

Who it’s for

  • Specialist subcontractors

What would this cost for your team?

Answer questions about your company and how this work runs today. You see an indicative estimate of the hours back, what that time is worth and the price when you send your details.

Get a price for this

Or check first: Are we ready for AI?

How it runs, before and after

Reactive fault call to first-time fix and invoice

Before, by hand

Take the call

Send and fix

Report, bill and learn

01Answer out-of-hours fault calls, log them and wake the right on-call engineer

  • Answer the call
  • Find the site and contract
  • Apply the emergency rules
  • Log the job
  • Call the on-call engineer
  • Decide whether to attend

02Read reactive job requests from emails and client portals and log them ready for dispatch

  • Read each email and portal job
  • Match it to the contract and SLA
  • Check for duplicate jobs
  • Draft the job record
  • Approve the job and priority
  • Escalate anything unsafe

03Suggest the right engineer for each job using skills, accreditations, location and van stock

  • Filter engineers who are in date
  • Rank by travel and van stock
  • Show the reasons
  • Warn when nobody fits
  • Decide who goes

04Warn the service team before contract response and fix times are breached

  • Work out time left on each job
  • Alert with the likely cause
  • Log breach reasons
  • Act on the alerts
  • Agree reasons with the client

05Answer engineers' fault-finding questions from manuals and past jobs

  • Search manuals and past jobs
  • List likely causes and checks
  • Log each question for training
  • Judge the fix on site

06Turn engineer notes into customer-ready service reports

  • Write up the voice note
  • Pull out readings, parts and defects
  • Link the photos
  • Draft the report in your format
  • List defects to quote
  • Confirm the report and readings

07Code each finished repair to the schedule of rates before it is invoiced

  • Read job notes and photos
  • Suggest codes and quantities
  • Compare with the order
  • Flag what doesn't match
  • Approve the codes
  • Build the claim file

08Find unbilled call-outs, overtime and materials on completed reactive jobs

  • Apply each contract's rate rules
  • Compare jobs with invoices
  • List items not billed
  • Show the value and evidence
  • Decide what to bill

09Find why reactive jobs need a second visit

  • Link first and repeat visits
  • Read notes for the reason
  • Rank the causes
  • Sum up patterns with examples
  • Decide actions on training and stock

48tasks, all by hand

After, with automation and AI

AutomatedAI reads and draftsYour team decides

Take the call

Send and fix

Report, bill and learn

01Answer out-of-hours fault calls, log them and wake the right on-call engineer

  • AI reads and drafts: Answer the call
  • AI reads and drafts: Find the site and contract
  • Automated: Apply the emergency rules
  • Automated: Log the job
  • Automated: Call the on-call engineer
  • Your team decides: Decide whether to attend

Passes on: the out of hours call logged, and the right engineer woken

02Read reactive job requests from emails and client portals and log them ready for dispatch

  • AI reads and drafts: Read each email and portal job
  • AI reads and drafts: Match it to the contract and SLA
  • Automated: Check for duplicate jobs
  • AI reads and drafts: Draft the job record
  • Your team decides: Approve the job and priority
  • Your team decides: Escalate anything unsafe

Passes on: each request from email or portal, logged and ready to send out

03Suggest the right engineer for each job using skills, accreditations, location and van stock

  • Automated: Filter engineers who are in date
  • AI reads and drafts: Rank by travel and van stock
  • AI reads and drafts: Show the reasons
  • Automated: Warn when nobody fits
  • Your team decides: Decide who goes

Passes on: the best engineer for the job, by skills, location and van stock

04Warn the service team before contract response and fix times are breached

  • Automated: Work out time left on each job
  • AI reads and drafts: Alert with the likely cause
  • Automated: Log breach reasons
  • Your team decides: Act on the alerts
  • Your team decides: Agree reasons with the client

Passes on: a warning before the response or fix time is breached

05Answer engineers' fault-finding questions from manuals and past jobs

  • AI reads and drafts: Search manuals and past jobs
  • AI reads and drafts: List likely causes and checks
  • Automated: Log each question for training
  • Your team decides: Judge the fix on site

Passes on: answers to the fault from manuals and past jobs

06Turn engineer notes into customer-ready service reports

  • AI reads and drafts: Write up the voice note
  • AI reads and drafts: Pull out readings, parts and defects
  • Automated: Link the photos
  • AI reads and drafts: Draft the report in your format
  • AI reads and drafts: List defects to quote
  • Your team decides: Confirm the report and readings

Passes on: a service report the customer can read

07Code each finished repair to the schedule of rates before it is invoiced

  • AI reads and drafts: Read job notes and photos
  • AI reads and drafts: Suggest codes and quantities
  • Automated: Compare with the order
  • Automated: Flag what doesn't match
  • Your team decides: Approve the codes
  • Automated: Build the claim file

Passes on: the repair coded to the schedule of rates, and the claim checked

08Find unbilled call-outs, overtime and materials on completed reactive jobs

  • Automated: Apply each contract's rate rules
  • Automated: Compare jobs with invoices
  • Automated: List items not billed
  • Automated: Show the value and evidence
  • Your team decides: Decide what to bill

Passes on: any call-out, overtime or parts not yet billed

09Find why reactive jobs need a second visit

  • Automated: Link first and repeat visits
  • AI reads and drafts: Read notes for the reason
  • AI reads and drafts: Rank the causes
  • AI reads and drafts: Sum up patterns with examples
  • Your team decides: Decide actions on training and stock

Ends with: why jobs needed a second visit, and what would fix them first time

18automated19by AI11decided by your team

Before, by hand

Take the call

1Answer out-of-hours calls
2Log the reactive jobs

Send and fix

3Pick the right engineer
4Warn before a breach
5Answer fault questions

Report, bill and learn

6Draft the job report
7Code the repairs
8Find unbilled work
9Find repeat visits

48tasks, all by hand

After, with automation and AI

AutomatedAI reads and draftsYour team decides

Tap a step to see each task and what it passes on.

Take the call

1Answer out-of-hours calls

AI reads and drafts: Answer the call

AI reads and drafts: Find the site and contract

Automated: Apply the emergency rules

Automated: Log the job

Automated: Call the on-call engineer

Your team decides: Decide whether to attend

Passes on: the out of hours call logged, and the right engineer woken

2Log the reactive jobs

AI reads and drafts: Read each email and portal job

AI reads and drafts: Match it to the contract and SLA

Automated: Check for duplicate jobs

AI reads and drafts: Draft the job record

Your team decides: Approve the job and priority

Your team decides: Escalate anything unsafe

Passes on: each request from email or portal, logged and ready to send out

Send and fix

3Pick the right engineer

Automated: Filter engineers who are in date

AI reads and drafts: Rank by travel and van stock

AI reads and drafts: Show the reasons

Automated: Warn when nobody fits

Your team decides: Decide who goes

Passes on: the best engineer for the job, by skills, location and van stock

4Warn before a breach

Automated: Work out time left on each job

AI reads and drafts: Alert with the likely cause

Automated: Log breach reasons

Your team decides: Act on the alerts

Your team decides: Agree reasons with the client

Passes on: a warning before the response or fix time is breached

5Answer fault questions

AI reads and drafts: Search manuals and past jobs

AI reads and drafts: List likely causes and checks

Automated: Log each question for training

Your team decides: Judge the fix on site

Passes on: answers to the fault from manuals and past jobs

Report, bill and learn

6Draft the job report

AI reads and drafts: Write up the voice note

AI reads and drafts: Pull out readings, parts and defects

Automated: Link the photos

AI reads and drafts: Draft the report in your format

AI reads and drafts: List defects to quote

Your team decides: Confirm the report and readings

Passes on: a service report the customer can read

7Code the repairs

AI reads and drafts: Read job notes and photos

AI reads and drafts: Suggest codes and quantities

Automated: Compare with the order

Automated: Flag what doesn't match

Your team decides: Approve the codes

Automated: Build the claim file

Passes on: the repair coded to the schedule of rates, and the claim checked

8Find unbilled work

Automated: Apply each contract's rate rules

Automated: Compare jobs with invoices

Automated: List items not billed

Automated: Show the value and evidence

Your team decides: Decide what to bill

Passes on: any call-out, overtime or parts not yet billed

9Find repeat visits

Automated: Link first and repeat visits

AI reads and drafts: Read notes for the reason

AI reads and drafts: Rank the causes

AI reads and drafts: Sum up patterns with examples

Your team decides: Decide actions on training and stock

Ends with: why jobs needed a second visit, and what would fix them first time

18automated

19by AI

11decided by your team

An example of how this workflow usually happens. We would tailor it to your company and add or remove tasks based on how you work.