fluctor

Every visit seen coming. Every part on the invoice.

Tallis Service is an example of a maintenance company with technicians on the road. Its people make the calls, its agents do the paperwork.

Autonomous transport vehicle carrying racks in a hall

How one case runs.

A planned visit that is coming due with nobody booked. Here is what fluctor does with it, step by step.

  1. 1Noticed

    On 22 June the quarterly visit to blast freezer BF-1 is eight days from its deadline, 30 June. fluctor raises a Due Soon signal, High, with page 4 of the Northgate service contract as its source.

  2. 2Traced

    Explore opens the machine and follows it to its last call-outs, the Northgate file, contract SC-2291 and clause 6.2: a missed visit means a €1,440 credit to the customer. In the job plan for week 26 the visit is marked not booked.

  3. 3Automated

    One click on Automate this opens the chat. The agent is described in a sentence: when a planned visit is due soon and nobody is booked, propose a day from the job plan and email the customer.

  4. 4Approved

    The first run stops before anything is sent. The email to Pat Hanley at Northgate proposes Thursday 25 June with Mairead Cole, notice attached. Approve this run sends this one; with Always allow for this agent, the next ones go out on their own. fluctor books no technician; people do that once Northgate has answered.

  5. 5Tracked

    A sentence in the chat builds the dashboard of service visits by machine. BF-1 shows as proposed for 25 June, the four other visits of the week as booked.

See it work, start to finish.

One planned visit, eight days out with nobody booked. Watch fluctor notice it, trace it, hand it to an agent and keep watch on all the others.

Two more agents for the service desk.

Unbilled parts

The problem
Parts fitted on a visit that never make it to the invoice.
It starts when
A service report is signed and lists parts
The result
Invoice 3318 to Northgate, €1,241 net
The agent “Unbilled parts” opened in the agent list: last run 22.06.2026, 08:02. Drafted invoice 3318 for the parts on report 0586, €1,241 net, and sent it to approval.

Contract reviews

The problem
A contract renews on old prices because the notice date passed.
It starts when
Every morning, against the contract dates
The result
Brief with 10 days to go
The agent “Contract reviews” opened in the agent list: last run 22.06.2026, 07:30. Northgate has a notice date in 10 days and a rising number of call-outs. The account manager got a brief with both.

What the service desk asks.

Every answer comes with the file it was read from.

  • On 30 June 2026, in 8 days. If a planned visit is missed, clause 6.2 credits 5% of the annual fee, €1,440, to the customer.

    Source: service_contract_northgate.docx

  • No. Report 0586 was signed on site on 12 June and lists two fan motors, a contactor and 8 kg of refrigerant. There is no invoice on file. Est. €1,241 outstanding.

    Source: service_report_0586.jpg

  • On 30 September 2026, for 12 more months at today’s prices. Notice has to be given by 2 July, in 10 days. Northgate had 9 call-outs this quarter, 3 is usual.

    Source: service_contract_northgate.docx

  • 9 times since 8 April, 7 of them for chiller CH-3. Its fan motors were replaced on 12 June.

    Source: Call-out log, Northgate

Your data stays yours.

Contracts, service reports and customer emails stay in-house: hosted in the EU or entirely on your own servers.

Security
  • EU hosting
  • Your own servers
  • GDPR & DPA
  • No training on your data
  • Every answer with its source
  • Activity log

See fluctor on your own documents.

A demo on your own contracts and service reports, with your real inbox and files, not on slides.