Automate
Automation for the work that happens between the tools.
Most operational time is not lost inside a system. It is lost in the gaps between them: re-keying an enquiry into a CRM, remembering to follow up, assembling a report by hand. That is the work this addresses — with AI used where judgement or language genuinely helps, and not otherwise.
- Capability group
- Automate
- What that group is for
- Save time and run your business better
- Who it is for
- Businesses losing time or enquiries in the manual work between systems — an inbox that acts as a queue, a follow-up that depends on somebody remembering.
- Where it stops
- Automating and connecting processes across tools you already run. When the process needs a system of its own rather than a connection between existing ones, it is a Custom Software & Digital Platforms project.
Automate the process, not the mess
An automation inherits whatever process it was pointed at, including the parts that were already wrong — so the first pass is always the process itself: what has to happen, who does it, what the exceptions are, and which steps are genuinely rule-based. Frequently a step turns out to be unnecessary rather than automatable, which is the cheapest possible outcome.
The second decision is where AI belongs. Routing an enquiry by service type and value is a rule, and a rule is more reliable, cheaper and easier to audit than a model. Reading a paragraph of free text to work out what someone is actually asking for is a language problem, and that is where a model genuinely earns its place. Treating everything as an AI problem produces systems that are expensive to run and impossible to debug.
Everything built this way is designed to fail visibly. A queue that silently drops work is worse than no automation at all, because nobody notices until a customer does.
Common signals
- Enquiries arrive in a shared inbox and are triaged by whoever sees them first.
- Response time depends on the day of the week and who is on duty.
- The same customer detail is typed into two or three systems.
- Follow-up depends on someone remembering, so some of it does not happen.
- Reporting is assembled manually, so it is always late and rarely trusted.
Interactive demonstration
Follow one enquiry through the rules
Pick a sample enquiry, or change one condition. Every stage shows the rule that fired and what it produced.
Synthetic scenarios and deterministic rules. No real customer data is used, and nothing you select is stored or sent.
Qualified lead, routed to Project lead. Follow-up produces: appointment hold, task, message draft.
Enquiry
Changed- What happened
- Captured as a structured record before any other step
- Why
- E1Any enquiry, on any channel
- Produced
- RecordWebsite form · New project · details complete · business hoursSample record · not stored
Qualify
Changed- What happened
- Marked as a qualified lead
- Why
- Q3Details are complete and the enquiry is a new project or a pricing question
- Possible results
- Qualified lead (taken)
- Existing client
- General enquiry
- Needs details
- Produced
- ResultQualified leadRecorded on the enquiry
Route
Changed- What happened
- Assigned to Project lead
- Why
- R1Qualified lead about a new project
- Possible results
- Project lead (taken)
- Sales desk
- Client support
- General inbox
- Intake queue
- Produced
- AssignmentProject leadOwner for every next step
Follow-up
Changed- What happened
- Consultation slot held; the owner is asked to confirm it
- Why
- F2Qualified lead, during business hours
- Produced
- Appointment holdConsultation slotHeld · awaiting confirmation
- TaskConfirm the held slotAssigned to Project lead
- Message draftAcknowledgement with the proposed slotEmail draft · not sent
Report
Changed- What happened
- Counted once, under its result and route
- Why
- P2Every other enquiry
- Produced
- Report tallyQualified lead · Project lead +1Business hours column
Show all rules
Each stage takes the first rule whose condition holds. Nothing else decides the path.
Enquiry
| Rule | When | Then |
|---|---|---|
| E1Fired | Any enquiry, on any channel | Captured as a structured record before any other step |
Qualify
| Rule | When | Then |
|---|---|---|
| Q1Fired | Required details are missing — this overrides every intent | Held until the missing details arrive |
| Q2Fired | Details are complete and the sender is an existing client | Marked as an existing client, not a new lead |
| Q3Fired | Details are complete and the enquiry is a new project or a pricing question | Marked as a qualified lead |
| Q4Fired | Details are complete and the enquiry is a general question | Marked as a general enquiry |
Route
| Rule | When | Then |
|---|---|---|
| R1Fired | Qualified lead about a new project | Assigned to Project lead |
| R2Fired | Qualified lead with a pricing question | Assigned to Sales desk |
| R3Fired | Existing client | Assigned to Client support |
| R4Fired | General enquiry | Assigned to General inbox |
| R5Fired | Needs details | Assigned to Intake queue |
Follow-up
| Rule | When | Then |
|---|---|---|
| F1Fired | Needs details, at any time | Missing details requested; nothing is scheduled until they arrive |
| F2Fired | Qualified lead, during business hours | Consultation slot held; the owner is asked to confirm it |
| F3Fired | Qualified lead, after hours | Acknowledged; no slot is held, because nobody is available to confirm one |
| F4Fired | Existing client, during business hours | Support task opened; the request is acknowledged |
| F5Fired | Existing client, after hours | Acknowledged; the task is queued for business hours |
| F6Fired | General enquiry, during business hours | Task created to answer it |
| F7Fired | General enquiry, after hours | Acknowledged; the answer is queued for business hours |
Report
| Rule | When | Then |
|---|---|---|
| P1Fired | Needs details | Counted once, as open and awaiting details |
| P2Fired | Every other enquiry | Counted once, under its result and route |
Every enquiry should follow a path you can read.
Tell us how enquiries reach you today, and where they stall.
What we can help with
These are the recurring shapes. Most engagements start with one and extend once it is genuinely working.
- Enquiry handling and routing
- Form and message submissions captured as structured data, classified, and routed to the right person or queue automatically, with an acknowledgement the sender actually receives.
- Lead qualification
- Enquiries scored or sorted against criteria you set, so a serious enquiry is not sitting behind a supplier newsletter in the same inbox.
- Messaging and WhatsApp automation
- Conversational channels wired into the same process as the website form, so an enquiry is handled the same way regardless of how it arrived.
- Follow-up and reminders
- Scheduled, conditional follow-up that stops when a human replies. The value is in the sequence being reliable, not in it being clever.
- Appointment and scheduling workflows
- Booking, confirmation, reminders and rescheduling handled without a back-and-forth thread, including the awkward cases like cancellations and no-shows.
- CRM and internal workflows
- Records created and kept current automatically, with stages, ownership and handovers reflected in the system instead of in a person’s memory.
- Reporting automation
- The recurring report assembled from the systems that own the data, on schedule, so the time goes into interpreting it rather than building it.
- Integrations
- Connecting website, CRM, messaging, calendar, accounting and internal tools — with retries, error handling and visibility when something fails, not a script that quietly stops.
How an automation engagement usually runs
One process at a time, in production, before the next. A large automation programme built all at once is a large automation programme nobody trusts.
Process mapping
What happens today, including the exceptions people handle informally. Produces a short written description both sides agree is accurate.
Decide what to automate
Which steps are rule-based, which need judgement, which need a person, and which should be removed instead of automated.
Design the flow
The path, the data, the failure modes and the escalation. Deciding what happens when something goes wrong is most of the design work.
Build and run in parallel
Built, then run alongside the existing process until it is demonstrably reliable. Nothing is switched over on the strength of a demonstration.
Monitor and extend
Visibility into what ran, what failed and what was retried — then the next process, once the first is genuinely trusted.
Where it connects
Automation depends on the enquiry arriving as structured data, which is a decision made when the website form is built. It is the reason the site and the automation are worth designing together rather than sequentially — a form that emails a free-text blob makes everything downstream harder than it needs to be.
It also connects to paid campaigns. What a paid enquiry meets on arrival — how quickly it is answered, how consistently, and whether the handling is logged at all — is part of what that spend buys, and is worth examining alongside the campaign itself rather than after it.
Where the process needs a system of its own rather than a connection between existing tools, the honest answer is a platform project, and we would say so rather than building an increasingly fragile chain of automations.
What to expect from us
- A recommendation to fix or remove a process step before automating it, where that is the right answer.
- AI used where language or judgement genuinely helps, and rules everywhere else.
- Systems that fail visibly, with retries and alerting, rather than silently.
- Documentation of what runs, when, and what to do when it breaks.
Proof
Work behind this service
Related
Work that usually sits alongside this
Losing time — or enquiries — in the gaps between your tools?
Describe what happens after someone contacts you today. You will get a straight view of which parts are worth automating and which are better simply removed.