FieldQuo

How AI troubleshooting works: from a code to a callback

The assistant helps with something minor, says it will book a tech call if it persists — and when the customer writes back, the callback is booked without asking them again.

Sa ngayon, available ang artikulong ito sa Ingles, Pranses at Espanyol. Binabasa mo ang bersyong Ingles. Français · Español

This is what your Tech support employee does with “my washer stopped mid-cycle”, step by step — and what lands in front of your team at the end.

The conversation

  1. It reads the client's equipment on file, if the conversation belongs to a known client: make, model, install date and the warranty date on the record. It never sees prices, invoices or balances, and never reads a serial number out.
  2. It asks only for what is missing, then looks the code up and gives at most two or three safe steps from your manual or FieldQuo's references, naming where they come from.
  3. It notes what it suggested, and the reply ends with: If the problem persists, send us another message and we'll find you a time with one of our techs. — added by FieldQuo, in the client's language, so it is there every time. (With Offer real times with a tech switched off, it says …we'll book a call with one of our techs. instead.)
  4. If they write back that it's still happening, it offers real times from your booking calendar straight away — the same free times your booking page shows — and books the one they pick, as a call with a tech or a visit. Only when nothing is free (or real times are switched off) does it book a callback instead; the note says what the equipment is, the code, and what was already tried. If it now sounds urgent, that comes first — see Urgent problems and safety.

What your team sees

  • A known client gets a ticket on their record — type Warranty when the warranty date on file hasn't passed, otherwise Repair — linked to the job that installed the equipment, priority Urgent when the assistant marked it so. See Client tickets.
  • Anyone else becomes a lead with the Call back requested through your AI assistant badge on the Leads board, with Urgent in front when it is.

The assistant never promises a time, and never says what is or isn't covered — a warranty date on the record is something it mentions and notes for the team; the team decides.

The reply limit

Most replies in one conversation still applies. The one exception: when the assistant told the customer to write back if the problem persists, their next message is answered once even if the limit was reached — and that reply can only book a time with a tech, book the callback or hand the conversation to a person. A limit of 0 (paused) is never overridden.

Nakatulong ba ito?