Chat automation · Lead qualification · Respond.io · Routing

Respond.io Chatbot: Enquiry Handling Across Four Channels

A Respond.io chatbot connecting WhatsApp, Instagram, Facebook and the website widget — a welcome flow, FAQ answers, qualification questions before a human replies, and routing to the right market's sales agent.

Client
PI Startup Advisory
Period
2025 — present
Role
Automation & Reporting Lead
Status
Ongoing · employer engagement
Typographic cover card for the Respond.io chatbot project — four channels, one welcome flow.
Four channels, one welcome flow, one handover rule set.

Results at a glance

Channels
4

WhatsApp, Instagram, Facebook, web

First response
Automated

Before any agent replies

Qualification
Before handover

Market and service

Platform
Respond.io

The problem

PI Startup Advisory takes enquiries across four different places: WhatsApp, Instagram, Facebook and the form on the website. Each one landed in a different inbox, and a person had to notice it, read it, work out which market and service it belonged to, and then find the right agent for that market.

Two failures followed from that. The first was response time — an enquiry that arrived outside working hours waited, and a lead comparing company-formation providers does not wait long. The second was consistency: the same six questions came in every day, and every agent answered them slightly differently, in their own words, from their own inbox.

There was also no structure to the handover. An agent picking up a conversation often started with the same clarifying questions the customer had already answered somewhere else.

Why we decided to solve it

The enquiries were already arriving; the problem was what happened in the first ten minutes. That window decides whether a B2B formation lead stays in the conversation, and it was being spent on triage rather than on the sale.

The group also operates across Bahrain, Saudi Arabia, Oman, Turkey, Qatar and Europe. Without a routing rule, a Bahrain enquiry could be answered by someone whose service knowledge was built for another market, which is worse than a slow reply.

How we did it

Connect the channels into one inbox

WhatsApp, Instagram, Facebook and the website widget were all connected to a single Respond.io workspace, so every conversation arrived in one place with a channel label instead of four separate inboxes being watched by four different people.

Write the first response

I designed the welcome flow: what the bot says when a conversation opens, how it presents the services, and the FAQ answers for the questions that arrived daily — formation cost, timeline, documents required, visa and bank account, renewal. The answers were written to the group’s own service definitions rather than left to each agent’s phrasing.

Qualify before a human replies

Before any handover, the bot asks the qualifying questions that decide the rest of the conversation: which market the company will be formed in, which service they need, and whether they are starting fresh or renewing. That gives the agent context on the first message instead of the fourth.

Route by market and service

Routing rules assign the conversation to the sales agent who owns that market and service, so a Bahrain formation enquiry reaches the Bahrain team and a renewal reaches whoever handles renewals. Outside working hours the flow holds the conversation, answers what it can and tells the person when an agent will pick it up.

Keep the human in the loop

The bot is a filter, not a replacement. Anything outside the defined flows — pricing negotiation, an unusual structure, a complaint — goes straight to an agent, and every automated conversation can be taken over mid-thread.

The result

One entry point for four channels, a first response that no longer depends on someone being at a desk, enquiries that arrive with market and service already known, and a consistent set of answers to the questions that used to be answered differently by every agent.

Conversation volumes and lead figures are not published here: they belong to the employer. What this project changed is the shape of the enquiry pipeline — automated intake, structured qualification, routed handover — and that structure is visible in the flow rather than in a dashboard.

All projects

Cleared · No conversation content, contact details, agent names or account identifiers are published. The flows are described, not reproduced.

Contact

Want to talk through a project like this?

I am open to remote SEO, web design and performance roles. If you need more detail on a specific project, ask — I will share what the client allows.