For anyone evaluating Lingo
How Lingo turns a manual into a guide
What happens between uploading a manual and an installer getting the right step on their phone.
Lingo
2 min read
Many technical support questions are already answered in a manual. The difficulty is finding the right page, on site, in the middle of a job. This is how Lingo turns the documentation you already have into something an installer can follow one step at a time.
In short
- Lingo reads your manuals and drafts guides: sequences of questions and fixes.
- Your technical team reviews and approves every path before an installer sees it.
- An installer can ask for a person at any point, and your team can write their answers into the guide.
Start with the documents you have
Manuals, service bulletins, commissioning guides and parameter tables go in as they are. There is nothing to rewrite or reformat first.
From document to guide
Lingo converts each document into guides. A guide is a sequence of questions and fixes: it asks what the installer can see, then gives the next step based on the answer.
- Upload. Add the documents for a product.
- Generate. Lingo drafts step-by-step guides from them.
- Validate. Your technical team checks each draft against the manual, corrects it where needed and publishes it.
- Deploy. Installers message a WhatsApp number and follow the published guide.
One path through a guide
A question, the answer given, and the fix it leads to
Restoring factory settings
PublishedQUESTION
Is the display fitted?
ANSWERS
- 1.Yes, I have the display
- 2.No, reset without the display
FIX
1. Open the advanced menu. 2. Scroll to DEFAULTS. 3. Choose YES and exit. Calibration is kept.
Nothing reaches an installer until your team approves it
This is the step that separates a guide from a generated answer.
Your technical team sees every path before it goes live, so the installer gets the answer you would have given on the phone.
When the guide has no answer
An installer can ask for a person at any point, and a guide can end by passing them to your technical team, who reply in the same WhatsApp conversation. Once they have answered, someone on your team can write the fix into the guide as a new branch and publish it.
- The installer is not left guessing.
- Your team sees what has already been tried.
- The next installer with the same question gets the answer from the guide.
The answer was always in the manual. The guide gets it to the installer at the moment they need it.
Questions people ask
What documents can Lingo turn into a guide?
Manuals, service bulletins, commissioning guides and parameter tables, as they are. There is nothing to rewrite or reformat first.
Who checks the guide before installers see it?
Your own technical team. They check each draft against the manual, correct it where needed and publish it. Nothing reaches an installer before that check.
What happens when a question is not covered by the guide?
The installer can ask for a person at any point. Your team is notified by email and replies in the same WhatsApp conversation. Someone on your team can then write the answer into the guide and publish it.
