Workflows
A workflow is a question-and-report template. Define the questions once; any engineer can run it any number of times.
Parts of a workflow
- Questions (inputs): what the engineer answers. Types: text, number, photo, voice note, yes/no.
- Report (output): the PDF generated from the answers.
- Trigger: manual by default. Scale plan adds scheduled sends.
Writing good questions
- Be direct. "Photo of the gas meter reading" not "Please take a picture once you've confirmed which meter is in use."
- Only ask what the report needs. Every extra question is friction on a phone screen.
- Use yes/no where you can. "Pass / fail" renders cleanly; freeform text often doesn't.
- Use photos. One clear photo beats ten lines of description, especially for compliance.
Limits by plan
| Plan | Workflows |
|---|---|
| Starter | 3 |
| Team | 5 |
| Business | 8 |
| Scale | 10 |
No cap on runs. Send each workflow to as many engineers on as many jobs as you like.
Editing
Change questions any time. Runs already in progress keep the version they started with; new runs pick up the changes.
Voice notes
Engineers can send WhatsApp voice messages in reply to any text question. Quickler transcribes them automatically and includes the text in the report.
Still stuck? Email [email protected] — we reply within one business day.