For dealer principals and service managers

AI on the service call

Pearl in the chat up front. FieldFlow and the manuals behind her.

Techs already live in their phones, so the assistant meets them in the chat. Every answer traces back to the manual it came from, and every fix a tech adds stays with the dealer.

How to ask

4
    • For example: “bizhub C450i throwing J-32. Where do I start?”
    • Pearl comes back with the manual page and the parts to check.
    • Name the model in the question and she uses it.
    • Ask again and she searches the manuals again, rather than reusing an earlier answer.
    • The keyboard mic turns your voice into words.
    • A recorded voice message from inside the chat app isn’t heard.
    • A good note is short: machine, code, what you did, what to watch for.
    • She files it so the next tech doesn’t start from zero. “Yes, that did it” marks a fix that worked.

Pearl in front, FieldFlow behind

One assistant, three doors: the chat for quick answers, FieldFlow for the full procedure, FlowView for the office.

  • No app to install. Techs ask in a chat app on any phone. She searches the service manual before she answers and shows the source.

  • Manual pages with cited page numbers, then the steps. A notes shelf to browse fixes by machine, by who wrote it, or by code. A shift pack keeps the codes the crew hits most on the phone for dead zones.

  • A staff view with Pearl alongside, so the office sees what the crew is working from without turning field knowledge into a black box.

What it needs before the truck rolls

A brief before every call needs the dealer’s own data, not just the manuals. Without it, an assistant answers from manuals and field notes only, and should say so.

  • The call ticket

    What the customer reported, and when.

  • The device’s own history

    When it was last serviced, and on which call.

  • What’s on the truck

    Parts checked against carstock before they’re suggested.

  • Live device data

    Panel messages, error codes and supplies, from the meter collector.

Questions to ask before you switch it on

  • Does every answer cite the exact manual page?

  • Does it say “not in my manuals” instead of guessing?

  • Does it mark a claim it can’t back as unverified?

  • Can a tech flag a wrong answer, and does someone review it?

  • Who can read the techs’ conversations?

  • Does it need your ERP connected before it can start?

The rules Pearl works under

  • Answers come from the service-manual passages she finds, with the source shown.

  • If the manual doesn’t cover it, she says so. “That code isn’t in the manuals I have” beats a guess.

  • A tech’s fix carries their name and is marked as from the field. Field knowledge is never presented as manufacturer documentation.

  • Only codes in the shift pack work offline. If a code isn’t cached, FieldFlow says so. It will not invent a fix.

Ask Pearl from the truck.

See how cited answers from your own bulletins fit the way your service team already works.

See Field