Follow-up map
A written workflow covering where enquiries come from, what information is needed, who owns the response and when automation should stop.
Practical enquiry routing, email and SMS workflows, and booking handoffs. We help your team keep track of who needs a reply and what should happen next.
Talk through your projectEnquiries arrive through forms, inboxes and messages, then depend on someone remembering to respond. A prospect can receive a generic reply, wait for the right person or disappear between the first conversation and a booking.
We map the journey from a new enquiry to booked work and build the agreed follow-up around it. That can include an acknowledgement, a team notification, useful questions, a booking link and reminders. Your team keeps control of conversations that need judgment.
Your proposal confirms the deliverables, responsibilities and costs before work begins.
A written workflow covering where enquiries come from, what information is needed, who owns the response and when automation should stop.
Approved email or SMS copy, internal notifications and assignment rules for the channels included in your proposal.
Connections to an agreed CRM, form, inbox or booking tool after checking its capabilities and access. We identify any custom integration work before committing to it.
Test enquiries through the agreed routes, including replies and stop conditions, followed by instructions for your team. Monitoring and ongoing changes can be scoped separately.
Clear decisions, a defined build and a handover your team can use.
We look at the tools you use and how your team currently responds, qualifies prospects and books work.
We define the messages, timing, ownership and handoff rules. You review the customer-facing copy before anything is enabled.
We run test enquiries, check that notifications reach the right place and confirm how your team pauses or changes the workflow.
An illustrative example of the work, not a client result.
For example, a quote request lands in a shared inbox. Nobody is clearly assigned to it, and the next action depends on someone checking the inbox at the right time.
The proposed workflow acknowledges the request, notifies its owner and records the next action. Approved follow-up can continue until the prospect replies, books or reaches an agreed stop condition.
We first check whether your current tools can support the workflow. We use the existing stack where it fits the agreed scope. A replacement or custom connection is a separate recommendation with its own costs.
Only the tasks you approve are automated. Routine acknowledgements and routing may need simple rules. If an AI-assisted response is useful, we define its information, boundaries and human handoff before including it.
We design the workflow around those events where the connected tools expose them. Reply, booking and opt-out handling are checked during scoping and testing so the sequence suits your actual process.
Your quote separates our setup work from software subscriptions and message charges. Any ongoing monitoring, support or workflow changes are also listed explicitly.
We quote after mapping the channels, systems and workflows involved. A single form-to-inbox handoff is a different scope from a CRM with qualification, booking and multiple follow-up sequences.
Tell us where things get stuck. We'll help define a useful first piece of work.
Let's talk about your business