WABusinessConnect

What it is

WABusinessConnect answers a trade business's WhatsApp messages automatically: a menu on the number customers already use, an assistant that captures the enquiry from a facts sheet the business writes, and a console where the people who actually answer do the answering. It runs on the business's own WhatsApp number, through Meta's platform, under the business's own name.

What the customer sees

A customer taps a button on the website, a link in an e-mail or a printed code, and lands in a WhatsApp chat with the business. A menu asks what they need: Sales, Track an order, Admin. For a sales enquiry the assistant asks what a good counter assistant would ask — the engine, the part, the quantity, where it is going — answers from the facts sheet, and never guesses: anything it does not know goes to a person. The customer gets a reference number the business's own price sheet knows, and a person replies on the same thread. Typing "delete me" erases everything the business holds about them, within ten minutes.

What the representatives get

One page per representative with every thread that needs an answer, oldest first. A reply typed there goes out on WhatsApp as if from the phone; a quotation typed as five fields (part, price, currency, lead time, carriage) becomes a PDF the customer can open. A dashboard shows every customer as one row. A rehearsal mode plays the customer in-process, so a new member of staff practises on the real console with no real customer on the other end. Message templates are held in code and checked against the account, so the day Meta or Twilio has to be started again is a command, not a rebuild.

How a customer arrives: every button, link and code goes through one redirect on the business's own domain, so a number change never breaks a printed thing

Node diagram: three doors, a button, a link and a QR code, lead through one redirect on the business's own domain to the WhatsApp thread under its number; inside the thread come the main menu, the assistant that captures the enquiry, and a person who answers
Node diagram: three doors, a button, a link and a QR code, lead through one redirect on the business's own domain to the WhatsApp thread under its number; inside the thread come the main menu, the assistant that captures the enquiry, and a person who answers
Node diagram: three doors, a button, a link and a QR code, lead through one redirect on the business's own domain to the WhatsApp thread under its number; inside the thread come the main menu, the assistant that captures the enquiry, and a person who answers

The customer's path: 28 states, 127 transitions, every live one walked by a test before a customer walks it

State diagram: from the main menu a conversation takes one of three routes. Sales goes from new or existing customer to the assistant to a quote sent; tracking asks for the PI number and hands to a person; admin goes straight to a person. Every route ends at inquiry complete
State diagram: from the main menu a conversation takes one of three routes. Sales goes from new or existing customer to the assistant to a quote sent; tracking asks for the PI number and hands to a person; admin goes straight to a person. Every route ends at inquiry complete
State diagram: from the main menu a conversation takes one of three routes. Sales goes from new or existing customer to the assistant to a quote sent; tracking asks for the PI number and hands to a person; admin goes straight to a person. Every route ends at inquiry complete

The dashboard, rendered from sample data: every customer as one row, every representative's queue

The representatives' dashboard rendered from sample data: one row per customer with reference, team, representative and status
The representatives' dashboard on a phone, rendered from sample data: one row per customer, longest wait first, with the journey and the standing request.
The representatives' dashboard on a phone, rendered from sample data: one row per customer, longest wait first, with the journey and the standing request.

"Delete me": erasure by command across every store, within ten minutes; "my data" returns a summary and a one-hour link

State diagram, two lanes: a customer who types "delete me" is asked to confirm with DELETE, then every store is erased and the data is gone within ten minutes, Twilio's copy too; a customer who types "my data" gets a summary and a machine-readable link good for one hour
State diagram, two lanes: a customer who types "delete me" is asked to confirm with DELETE, then every store is erased and the data is gone within ten minutes, Twilio's copy too; a customer who types "my data" gets a summary and a machine-readable link good for one hour
State diagram, two lanes: a customer who types "delete me" is asked to confirm with DELETE, then every store is erased and the data is gone within ten minutes, Twilio's copy too; a customer who types "my data" gets a summary and a machine-readable link good for one hour

Measured, not promised

The numbers on the About page are from the first business running it: 119 of 119 live conversation paths walked by a test, 270 of 274 messages read within seven days, 31 message templates held equal to the account, a 730-day retention policy enforced every night, one small server at $6 a month. They are dated, and they go stale; we would rather show you a stale number than a promise.

Where your customers' data lives

Each business runs on its own small server in London, described in code, watched around the clock and backed up every night. Customer numbers never appear in the logs; retention is a policy the server enforces, not a habit; "delete me" is a command a customer can type. Every company that processes the data on the way — the messaging network, the model, the hosting — is listed on the Privacy page with what it sees and for how long.

Talk to us

Tell us what you sell and which number your customers already use. The first conversation is about your facts sheet — what a good counter assistant at your business needs to know — because that is what the assistant answers from. Write to info@connectionsphere.co.uk. The case studies on the Work page show every part of this running for the first business that uses it.

©

2026

ConnectionSphere Ltd

Registered in England and Wales, No. 16412374

©

2026

ConnectionSphere Ltd

Registered in England and Wales, No. 16412374

©

2026

ConnectionSphere Ltd

Registered in England and Wales, No. 16412374

Create a free website with Framer, the website builder loved by startups, designers and agencies.