These workflow automation examples are the ones that earn their keep in a services firm with flat revenue: they recover enquiries you are already paying for, protect booked time and keep the pipeline honest. Each example below states the trigger, the steps, why it works and where it goes wrong. The question this article answers is which workflows to build first, and in what order, when you automate your workflow for the first time on the levelpartner.ai platform.
How to read each example
Every example has the same four parts. The trigger is the event that starts it. The steps are what the platform does, in order. The reason it works is the commercial logic. The failure point is the thing that usually breaks it in practice. If you cannot name the failure point for a workflow you are about to build, you have not finished designing it.
The order matters. Start at the top of the funnel, where a few minutes of delay costs the most, and work down towards retention and reviews.
Example one: instant reply to a new enquiry
Trigger: a form is submitted on your website or a lead arrives from an ad. Steps: send a text within a minute that names the person and confirms what they asked about, send an email with a booking link, create a task for the owner of the lead, and notify them in the app.
Why it works: the first firm to respond usually gets the conversation. A text that arrives while the prospect still has your page open feels attentive, not automated. The failure point is a generic message. "Thanks for your enquiry" reads as a robot; "Thanks, Sam, we have your question about remortgaging and can call today" reads as a person. The automated text response guide covers the wording in detail.
Example two: missed call to text
Trigger: an inbound call goes unanswered. Steps: wait two minutes, send a text saying you missed the call and asking how you can help, and open the conversation in the unified inbox so whoever is free can reply.
Why it works: many callers who reach voicemail hang up without leaving a message and try the next firm on their list. A quick text keeps the conversation with you. The failure point is sending it to existing clients who rang their account manager directly. Add a branch that skips contacts tagged as active clients.
Example three: booking confirmation and reminders
Trigger: an appointment is booked on any of your calendars. Steps: send a confirmation by email and text, wait until a day before, send a reminder with the option to reschedule, wait until an hour before, send a short final reminder.
Why it works: people forget, and a reschedule link turns a no-show into a moved meeting. The failure point is reminders that continue after a cancellation. Make sure the workflow ends when the appointment status changes.
Say the brokerage books 120 first appointments a month and 25 are no-shows. Suppose two reminders with a reschedule link brought no-shows down to 14, and nine of the missed slots were rebooked. Assume an illustrative £600 of fee income per completed case and one case for every three appointments. Nine recovered slots would then be three cases, or about £1,800 a month. Change any input and the answer moves, so run the sum with your own figures.
Example four: stale opportunity alert
Trigger: an opportunity has sat in the same pipeline stage for longer than your normal cycle allows. Steps: create a task for the owner, send them an internal notification, and if nothing changes after three more days, alert the sales lead.
Why it works: deals rarely die in a single moment. They go quiet in a stage nobody looks at. The failure point is setting the threshold too tight, so the team gets so many alerts that they ignore them all. Base the number of days on your real average, not an aspiration.
Example five: review request after delivery
Trigger: an opportunity is marked won and the work is delivered, or a project tag is added. Steps: wait a few days, send every client the same short message with your review link, and create a task for the account owner to call anyone who replies with a concern.
Why it works: you ask at the moment of satisfaction, and a person follows up on any problem the client raises. Do not filter who receives the link based on how happy they seem. Google's review policy forbids that kind of review gating, and it forbids offering incentives for reviews too. The failure point is asking too early, before the client has seen the result.
How to build your first one on the platform
Every example starts the same way: a new workflow, a trigger and the actions. Templates exist for several of these patterns, but writing your own trigger and messages teaches you how the workflow behaves before it touches a client.
- Go to Automation and select Workflows.
- Click Create Workflow, then click Start from scratch.
- Click Add New Trigger and select the trigger for your example, such as Form Submitted for the instant reply.
- Add trigger filters so the workflow only starts for the right form, calendar or pipeline.
- Click Add Action and select the first action, such as Send SMS.
Run it with a test contact that uses your own phone number and inbox, read each message where a client would read it, then publish.
How to switch on missed call text back
Example two does not need a workflow at all. The platform has a built-in setting for it, which is the simpler option when one message is enough.
- Click Settings in the bottom-left corner.
- Click Phone System in the left-side menu, click Voice in the top navigation, open Voicemail & Missed Call Text Back and click Missed Call Text Back in the side panel.
- Select the Enable Missed Call Text Back checkbox, then click Customize.
- Type your text in the Enter message field.
- Choose a number in the test message field to preview the message, review it and click Save.
The incoming call timeout slider sets how long the phone rings before the text goes. Somewhere between ten and twenty seconds is a sensible range. If you need the branch that skips active clients, build the workflow version instead.
How to build the stale opportunity alert
- Go to Automation and select Workflows.
- Click Create Workflow, then click Start from scratch.
- Click Add new Trigger and select Stale Opportunities.
- Name the trigger so you can find it later, for example "Stale proposal alert".
- Click Add Filters.
- Set Duration in Days to the number of days a deal can sit in the stage before it counts as stale.
- Select the pipeline under In Pipeline.
- Choose the stage under Pipeline Stage.
- Click Save Trigger.
Each trigger covers one pipeline and one stage, so a five-stage pipeline needs a trigger per stage you care about. The count starts when the trigger is added, not retroactively, and moving or updating the opportunity resets it.
What this replaces and the time it takes
These five workflows replace the sticky notes, shared inbox rules and memory that most firms rely on to follow up. Building all five takes two to four days of focused work for someone who knows your process. After that, expect an hour a week to read the replies they generate and tune timings.
The mistake most people make
They build ten workflows in the first week, often straight from templates. Each one is half-tested, several overlap, and a new lead receives three welcome emails. Build one, run it for two weeks, then build the next. The workflow process automation guide shows how to test one workflow end to end before you publish it.
When not to automate
Leave it manual where the message depends on judgement: a complaint, a pricing negotiation, a sensitive change in a client's circumstances. And do not automate a follow-up you have never sent by hand, because you will not know which wording works. For keeping a growing set of workflows tidy over time, see marketing automation best practices.
Troubleshooting
A lead got two welcome messages. Two workflows share the same trigger. Search Automation for that trigger and merge or retire one.
Texts are not delivering. The number is missing a country code or the contact has opted out. Check the contact's phone format and their subscription status.
Alerts arrive for closed deals. The stale opportunity workflow does not check status. Add a condition that only open opportunities qualify.
Frequently asked questions
Which example should a consultancy build first?
Usually the instant reply. Consultants often take hours to respond because they are in client meetings, and that delay loses more work than any other gap.
Can these examples work for real estate teams?
Yes. Swap the wording for property enquiries and valuation requests. The structure of trigger, steps and exits stays the same.
How many workflows does a 60-person firm need?
Fewer than people expect. Start with the five here and add another only when a real gap shows up, giving each one a single clear job.
Should I copy a template or write my own?
Start from the structure here, then write every message yourself. A template saves building time, but borrowed wording sounds like everyone else.