Automation by function

Routing WhatsApp and email support into one queue with n8n

Collect customer questions from WhatsApp, email and forms into one queue, answer the standard ones at once, route the rest by topic and language, flag delays.

By the RinooSol team Published Updated ⁨4⁩ min read

A support team with three inboxes and a phone answers the same questions all day and still misses some, because the question that fell between the inboxes belongs to nobody. One queue fixes the belonging. Every message from every channel becomes a ticket with an owner and a deadline; the questions with a standard answer are answered at once; the rest go to the right person with the full conversation; and anything that waits too long is flagged. This is how it is built on n8n, and what you decide.

The channels

  • WhatsApp, through a WhatsApp API: a private Evolution API instance for a single number replying to its own customers, or the official platform for a verified business line. The comparison says which.
  • Email, through a mailbox n8n watches (Gmail, Outlook or IMAP).
  • Website forms, through a webhook.
  • Facebook and Instagram messages, through their APIs, when those are real channels for you.

Each channel has a trigger; all triggers feed the same create ticket step.

The queue

A shared Google Sheet is enough to begin; a help-desk tool you already use (Zoho Desk, Freshdesk, HubSpot) can be the queue instead, and the workflow writes there. Each ticket records the channel, the customer, the first message, the time it arrived, a topic, a language, an owner, a status and the time of the first reply.

The topic and the language are set by the workflow: language from the message itself, topic from keywords you choose ("order", "delivery", "refund", "price") or, where the volume justifies it, a short AI classification step that labels the message and nothing else.

Standard answers, at once

A short list of questions with a fixed answer, kept in a sheet the team edits: opening hours, address, delivery times, return policy, how to pay. A matching message gets the answer immediately, in its language, signed as an automatic reply, with "reply here to reach a person" at the end. The ticket is closed as answered automatically and reopens if the customer writes back.

Order-status questions are the one dynamic case worth building early: the workflow looks up the order in the shop platform or the order sheet and replies with its stage. If no order matches, the question goes to a person.

Routing the rest

Everything without a standard answer is assigned:

  • By topic: billing questions to finance, delivery questions to operations, product questions to sales.
  • By language: an Arabic message to someone who answers in Arabic.
  • By load: round-robin within a team, skipping anyone marked away.

The assignee gets a WhatsApp message or an email with the ticket number, the customer and the conversation so far, and a link to the ticket. They reply through the same channel the customer used; the workflow logs the reply time and sets the status to in progress.

Nothing goes stale

Two timers run on every open ticket:

  • First reply. If no one has replied within the time you set (an hour in working hours, for most), the assignee is reminded and the customer is told someone is on it.
  • Resolution. If a ticket is open longer than a second limit, a manager is copied.

These two numbers are the service level you actually deliver, and they are measured by the queue itself.

The handover rule

When a person is handling a ticket, the automation stays out of that conversation until the ticket is closed. A customer in the middle of a real exchange never receives a standard answer because they happened to use a keyword. This single rule is what makes customers accept automatic replies at all.

The weekly numbers

A scheduled workflow sends a summary: tickets per channel, answered automatically versus by a person, median first-reply time, open tickets by age, and the questions that recur most. The last list is where the next standard answer comes from.

What to decide before building

  • Which channel carries most of your volume. Start there; add the others once it works.
  • The standard answers, written in your tone.
  • The topics and who owns each.
  • The two timers.
  • Whether the customer is told a reply is automatic. We recommend yes.

Where this fits

The customer support page shows this queue for an online shop with a two-person team, and the WhatsApp automation page the replies and confirmations it shares a number with. A free consultation is where we count your channels and write the first five standard answers with you.

Read next

Tell us what you do by hand today

Book a free consultation and we will design the automation with you.

We reply in Arabic or English

Last updated: