Request arrives
A customer reports a fault. Tourfold creates the “Fault report” record.
Record createdTourfold · Dispatch Software
Coming soon.
The new Tourfold website is currently under construction.
Product · Workflows
From a fault coming in to the published route: triggers, actions, approvals and AI steps in the visual editor, without programming.
01One process, end to end
A fault report comes in. What happens next is a workflow: create the task, plan the route, get approval if needed, publish.
A customer reports a fault. Tourfold creates the “Fault report” record.
Record createdA visit with an address, linked to the customer and asset.
Create taskThe task goes into the right route as a stop.
Update routeOnly if you want it: the shift lead confirms in their task list, with a deadline. Without this step the process simply carries on.
Request approvalThe route is published and the report is set to “Scheduled”.
Publish routeExample. Every step is a configured building block; for “Rejected” and “Expired” you define your own paths.
Which process costs your team the most time?Sketch it together in 30 minutes →
02Tasks
Tasks are the shared place for operational work and for human decisions.
Simple task, visit with a fixed destination, multiple-choice question and free-text question from a workflow.VisitApprovalChoice questionFree-text question
Approvals, choice questions and follow-up questions from the AI appear in the normal task list, with the question, options and deadline.
Customers, orders or assets are attached directly to the task. The access rights of the records stay in place.
A task belongs to one route at most and stays findable in the overall list, with a fixed reference such as Task-2318.
03Triggers and actions
A trigger starts the workflow. After that come actions, conditions, wait times and questions to people. Every step uses fixed values, data from the trigger or results from earlier steps.
04Publish and trace
You can save drafts even when unfinished. Only on publishing does the workflow become active and its version frozen.
05AI and scripts in the workflow
Both are steps in the workflow, with clear limits. They are published with the workflow and visible in every run.
Tourfold checks the result before it is accepted.
Inputs are fixed, and the editor recognises the output types without running the script.
Ask Rob is the interactive assistant in Tourfold and is separate from the agents in workflows. It also helps with building workflows.
Where would AI or rules take work off your team?Look at it together in 30 minutes →
No. Workflows are built in the visual editor. JavaScript is optional, for calculations that go beyond the standard building blocks.
Today up to 20 executable actions. Paths run one after another, without loops or parallel branches. Wait times of up to 30 days are possible.
Yes. The preview shows the process without changing anything. Scripts and AI agents do not run in the preview.
After the deadline passes, the workflow takes the “Expired” path. What happens there is up to you.
No. AI agents read only what you explicitly allow and deliver a result. Changes are made by the workflow actions that follow.
Nothing. Every run keeps the version it started with. New runs use the new version.
Under review are further triggers, branches with several cases, loops over records, reusable sub-processes and parallel paths. Scope and timing are not yet fixed.
07More modules
01Dispatch
Live map, skill matching and conflict check: the right job with the right person.
Learn more02Route planning
Bundle tasks into routes and stops, plan weeks, generate recurring routes from templates.
Learn more03Customisation
Your own objects and fields, your own terms and your own look: configured, not programmed.
Learn more04Tourfold Chat
Team, customer and partners communicate directly on the case, by app or SMS, everything stored.
Learn more08Demo
In 30 minutes we sketch together how one of your recurring processes looks as a workflow in Tourfold.
Prefer to write? To the contact form