Built around your business
Services, approved prices, hours, tone, FAQs and handover rules. We test common cases and exceptions before enabling each workflow.
AUTOMATION FOR YOUR BUSINESS
Enquiries waiting.
Follow-ups forgotten?
An unanswered WhatsApp, an unconfirmed booking, a contact recorded somewhere else. Build a connected workflow around how your business operates.
Request an AI agent quoteYOUR AI AGENT FOR WHATSAPP
A connected service workflow.
From enquiry to follow-up.
Your business needs information to move: from enquiry to conversation, from conversation to calendar, and from calendar to a recorded outcome.
- 01
An enquiry arrives
From a Meta form, your website or another enquiry. Keep the source when available.
- 02
It enters your CRM
Name, service, status and owner. Make or n8n connects the selected tools; both are not required.
- 03
The agent responds
Answers service questions using approved information, gathers context and hands over when it cannot resolve a request.
- 04
A booking is arranged
Checks availability, service duration, breaks and opening hours. Confirms only after the booking is recorded.
- 05
Follow-up is organised
Reminders and next actions follow agreed rules. Outbound messages require the channel’s configuration and permissions.
- 06
The outcome is recorded
Attended, missed, rescheduled or bought. Attendance must be confirmed by the business or a reliable record; a calendar event does not prove attendance.
Learn from what happens afterwards
As an advanced module, we can assess sending eligible conversion events to Meta. This requires integration setup, permissions and data matching; it does not guarantee improved optimisation or attribution of every event.
EXAMPLE CONVERSATION
Respond with context.
Know when to hand over.
A simulation explaining the service. Not a real chat or a demo connected to your calendar.
Hi, do you have any availability on Friday afternoon?
Hi, I’m the virtual assistant. Which service are you interested in? I can then check its duration and the available times.
I need something different. Can I speak to a person?
Of course. I’ll pass your enquiry to the team so they can help.
You stay in control
The agent must not invent prices, availability or guarantees. Sensitive decisions, incidents and out-of-scope requests go to a person.
Implemented in stages
Start with the task taking most of your time. Calendar, follow-up and Meta feedback are added according to scope; they are not presented as live features of this website.
DOES THIS SOUND FAMILIAR?
Five different problems.
Five practical approaches.
Illustrative scenarios to explain the service. Not testimonials or promised outcomes.
ILLUSTRATIVE CASE01 / 05
Maintenance team
Two people call one lead. Another gets no reply.
Enquiries arrive through several channels and each team member keeps a separate list. Nobody has the full picture.
HOW WE WOULD APPROACH IT
- 01Shared inbox record
- 02Assigned owner
- 03Visible next action
Explore the solution and questions +
What we would propose
Connect available sources to a shared record with owner, status and next action. Check duplicates using the data available.
You may be wondering
We already use Google Sheets.
We can assess keeping it and connecting the inputs. A useful tool does not need replacing.
Will everything have to change?
Start with one workflow, test it with the team and expand only where it helps.
Hypothetical scenario. Not a review or a real client result.
Discuss a similar situationILLUSTRATIVE CASE02 / 05
Psychology practice
Appointment changes take up the time between sessions.
An independent practice spends time confirming slots, managing changes and checking availability between appointments.
HOW WE WOULD APPROACH IT
- 01Administrative request
- 02Checked availability
- 03Confirmation or change
Explore the solution and questions +
What we would propose
Limit automation to administration: scheduling requests, confirmations and changes, with a human handover. Do not use it for clinical assessments or emergencies.
You may be wondering
I do not want a machine caring for my patients.
Limit it to administrative tasks and keep personal contact available.
What about sensitive data?
Define minimal data and access before connecting tools. Booking forms should not request clinical details.
Hypothetical scenario. Not a review or a real client result.
Discuss a similar situationILLUSTRATIVE CASE03 / 05
Training packages
You find out too late that a client has used every session.
Attendance is recorded in different places. Reconstructing remaining sessions and renewals takes time each week.
HOW WE WOULD APPROACH IT
- 01Attendance logged
- 02Balance updated
- 03Renewal review
Explore the solution and questions +
What we would propose
Use attendance records to update the session balance and create an internal renewal task at an agreed threshold.
You may be wondering
My packages have exceptions and make-up sessions.
Document these rules first and retain a manual correction path.
I do not want annoying automated messages.
Use internal alerts so you decide when to contact each person.
Hypothetical scenario. Not a review or a real client result.
Discuss a similar situationILLUSTRATIVE CASE04 / 05
Renovation team
The quote was sent. Nobody knows when to follow up.
The team moves on to the next site. Following up proposals depends on memory and open quotes are hard to track.
HOW WE WOULD APPROACH IT
- 01Quote recorded
- 02Next action
- 03Status-aware follow-up
Explore the solution and questions +
What we would propose
Record owner, date and status for each quote. Remind the team when a follow-up is due and stop when it is accepted or closed.
You may be wondering
My team will forget to update statuses.
Keep updates simple and assign an owner. The system cannot know changes nobody records.
What if a message goes out after they accept?
Test stop conditions and start with manual approval before outbound messages if needed.
Hypothetical scenario. Not a review or a real client result.
Discuss a similar situationILLUSTRATIVE CASE05 / 05
Event catering
You copy the same details into three places. They do not always match.
Event details live in chats, a sheet and a calendar. A change to the date or guest count leaves one version out of date.
HOW WE WOULD APPROACH IT
- 01Structured request
- 02Main record
- 03Controlled update
Explore the solution and questions +
What we would propose
Define a main record, connect compatible tools and flag important changes so the team can confirm resources.
You may be wondering
What happens when a tool fails?
Agree error detection and a manual fallback. Monitoring and maintenance are specified in the proposal.
Will there be hidden subscriptions?
Itemise setup, maintenance and third-party tools before contracting. They are not automatically included in the €500 ad package.
Hypothetical scenario. Not a review or a real client result.
Discuss a similar situationCase 1 of 5