Owner describes a process. AI builds the automation.
Coming soon: type what you want in plain English, and the IBIOS Workflow Builder will interpret it, propose the steps, and wait for you to review it and click Activate. It is not live yet; today your team carries out these steps from the quote and job records.
Why do manual processes in a trade business rely on someone remembering?
Every bathroom company has the same post-acceptance sequence: someone needs to send the customer a confirmation, someone needs to create the job record, someone needs to tell the installer. In a small operation, these steps happen because the owner or a senior staff member remembers to do them. On a busy day, one of them gets missed.
The usual solution is to build a workflow in a dedicated automation tool, which means learning a new interface, mapping data fields manually, testing trigger conditions, and handling errors when they occur. For a business owner who wants to automate a 3-step process, this is disproportionate effort.
The IBIOS Workflow Builder (coming soon) starts from the opposite position: describe what you want in the words you would use to explain it to a member of staff. The AI is designed to handle the interpretation and the field mapping, and the owner reviews and activates.
How do you build a workflow automation in plain English?
Coming soon, not live yet. This is how the IBIOS Workflow Builder is designed to turn a plain-English requirement into an active automation.
Owner types the requirement in plain English
The owner opens the IBIOS Workflow Builder and types: “When a quote is accepted, send the customer a confirmation email, create a job record, and notify the assigned installer by SMS.” No form builder. No dropdown configuration.
AI interprets and proposes the automation
The AI parses the requirement and proposes a 3-step workflow: (1) trigger on quote status change to Accepted, (2) send confirmation email to customer contact, (3) create linked job record and send SMS to installer field. Each step is shown with the mapped data fields.
Owner reviews and adjusts if needed
The proposed workflow is shown as a visual flow. The owner can modify any step — for example changing the email subject line or adjusting the SMS wording — without touching the trigger logic. Changes are plain text, not code.
Owner clicks Activate
The workflow is activated. From this point, every quote acceptance in IBIOS triggers the automation. The first live execution is logged in the audit trail with a timestamp and the data values used at each step.
Execution monitored and logged
Every workflow execution — successful or failed — is recorded in the IBIOS audit trail. The owner can view a history of executions, see which steps ran, and inspect any failures. Alerts are sent if a step still fails after its retries.
What will the outcome be when it launches?
Plain English
input turned into a proposed workflow you review before it goes live
No code
no manual field mapping, no scripting, no developer
Templates
built-in workflow templates to start from for common business processes
Coming soon: built-in templates for common processes in a trade business, such as quote follow-up, payment thank-you and review requests, with the plain-English builder for anything a template does not cover. Neither is live yet.
Questions about the AI Workflow Builder
What types of triggers can a custom workflow use?
Record events such as a quote accepted, a payment received, a job status changed or a new customer created, plus a scheduled time; the Workflow Builder is coming soon and not live yet. The full list of triggers will be confirmed when it launches.
Can a workflow send messages via SMS, email, and in-app simultaneously?
That is the plan, but both are coming soon: the Workflow Builder and customer and installer SMS are not live yet. When they launch, one trigger such as a quote being accepted is designed to send an email, an SMS and an in-app notification, each with its own wording.
What happens if a workflow step fails — does it retry, alert the owner, or skip?
It is designed to retry and then alert the owner; the Workflow Builder is coming soon, so this is not live yet. If the retries fail, for example because an email bounces, the owner will see which workflow and step failed and why.
Can workflows involve conditional logic — for example only notify the installer above a set job value?
Yes, when it launches; the IBIOS Workflow Builder is coming soon. You will be able to describe a condition in plain English, such as “only notify the installer if the job total is over a set amount”, and the AI will turn it into a conditional step.
Is there a limit to how many active workflows a tenant can have?
Limits will be confirmed when the Workflow Builder launches; it is coming soon and not live yet. Paused workflows are not planned to count as active.
Related features
When they launch (coming soon), workflows will act on records in the IBIOS CRM, order management and Boards. See also the quote-to-cash guide for trade businesses. IBIOS (Integrated Business Intelligence & Operations System) is made by IBIOS Limited (NI743167), Northern Ireland. Access is by waiting list; there is no free trial.
The plain-English Workflow Builder is coming soon.
Describe a process and IBIOS will propose the automation for you to review. Join the waiting list to hear when it launches.