Customer support automation across every channel your customers use

Questions arrive by email, by WhatsApp and through the booking form. Three different people answer them, each with their own idea of the right reply.

Nothing connects. A customer who wrote on Tuesday tells the whole story again on Thursday, to someone who had no way of knowing.

A good share of it lands outside office hours, which is the part nobody counts.

This page is the roof over three systems that also work on their own. Each channel keeps its own tooling, while the customer record and the rules live in one place.

• The inbox. Messages classified, routed and drafted from your own documentation, described in email automation.
• The phone. WhatsApp on the official Business API, so the channel stops depending on one handset. That is WhatsApp automation.
• The diary. Bookings, confirmations and reminders handled end to end, covered in appointment automation.
• One history per customer. Every conversation lands on the same record, which is what stops the same question being asked twice.

An AI model reads what arrives and decides where it goes. n8n moves it, and your CRM holds the truth.

Complaints go to a person, always. Same with anything medical, legal or about money beyond a published price, because an apology from a machine is worth nothing.

The assistant says it is an assistant when asked. Customers forgive a bot that admits it, and they never forgive one that pretended.

Cancelling a service or closing an account waits for a human too. Speed is worth little on the one message that decides whether a customer stays.

What this looks like in an online shop is written up in the Pepper case.

Channel by channel, never all at once. Email classification is usually live in two weeks. WhatsApp depends on Meta approving your templates, and the diary is quicker than both.

The whole picture takes four to five weeks from the first call. Every channel is tested first against real past conversations in a controlled environment, as the process section explains.

Book the AI and operations audit. We count what arrives on each channel and how much of it repeats, then hand you a ranked plan two working days later with its fee credited against the first project.

Export a month of email and a month of chats, plus whatever help documentation exists. The out of date version still tells us what your team really says.

The system is yours the day it goes live. Workflows are documented, credentials sit in your accounts, and your team is trained to change them. Keeping it running afterwards is maintenance, which nobody is obliged to take.