Log inBook a walkthrough
Book a walkthrough
English

Point installers to the documented setting for their variant.

A guide asks which variant is fitted and what the installer wants the product to do, then gives the setting your manual documents for that case. Your team checks and publishes each guide.

Book a walkthroughSee how it works

Lingo

Online

Installer: Need to change a setting on a Model A
Lingo: Which variant of Model A is fitted? 1. Standard 2. With expansion module
Installer: 2
Lingo: What do you want it to do? 1. Change a timing 2. Change how an input behaves 3. Something else
Installer: 1

EXAMPLE GUIDE · WHAT IT HAS ASKED

Product
Model A
Variant
With expansion module
Wanted
Change a timing
Next
The documented setting, as numbered steps

The one setting an installer needs, out of a whole programming chapter.

A programming chapter lists every setting for every variant. A guide asks two questions and gives the one case in front of the installer.

  1. 1

    Which variant is fitted

    Settings differ between variants, so the guide asks first. Your team words the question so an installer can answer it by looking at the product.

  2. 2

    What the product should do

    The installer picks from numbered choices. Your team writes them, so they can be worded as results an installer would recognise.

  3. 3

    The documented setting

    The guide gives the setting your manual documents for that variant and that result, as numbered steps. If no choice fits, the installer can ask for a person.

Your team decides which settings installers are given.

Lingo drafts the guides from your programming manual. Your technical team checks each one against the source and publishes it.

Your team decides

  • Which settings get a guide at all
  • Whether a safety-related setting is given, left out, or handled by a person on your team
  • The wording of every question and step, checked against the manual before it is published

Installers and your team get

  • The documented setting as numbered steps on WhatsApp, Teams, web or email, at any hour
  • A person on request, who replies in the same conversation with the earlier messages visible
  • Every conversation kept with the installer’s name and number, the product and the guide used

If the right setting depends on a value already in the product, the guide asks the installer to read it first. If a setting is one step in a longer procedure, it goes in that procedure’s guide: see commissioning and setup. A person on your team is always one message away.

Questions manufacturers ask about settings

What if the installer knows the result they want but not what the setting is called?

A guide offers numbered choices, and your team decides how they are worded. They can describe what the product should do in the installer’s terms, with your manual’s name for the setting given in the steps that follow.

A setting moved between firmware versions. How is that handled?

By asking. Where the answer depends on the version, your team adds a question the installer can answer from the product, such as what a label or a screen shows, and the guide branches on the reply.

How do guides get made from a programming manual?

You upload the manual. Lingo drafts guides from it, and your technical team checks each one against the source, edits it and publishes it. Send us one programming manual and we will go through its draft guides with you in a 15-minute walkthrough.

Industry pages

Send us one programming manual.

We’ll convert it and show you your own guide in a 15-minute walkthrough.

Book a walkthrough