Demand
CRM, websites and omnichannel
A customer writes on WhatsApp, fills in a form, then calls. In most companies those are three different customers. Making them one record is unglamorous and it is where the leaks are.
WhatsApp lives on someone's phone and does not exist in the CRM.
The website form goes to an inbox that one person checks.
Sales reply in hours because the enquiry has to be found before it can be answered.
You cannot say what a lead costs, because the channel and the sale are recorded in different systems.
- 01
One customer record
Identity resolution across channels so a phone number, an email and a chat handle collapse into one person with one history — the precondition for every other number you want to trust.
- 02
Unified inbox
WhatsApp, Telegram, email, web chat and calls arriving in one place with assignment, response times and ownership. Channels are added because customers use them, not because a vendor supports them.
- 03
CRM that reflects the actual sale
Pipeline stages that match how deals really move in your business, automation on the steps that are genuinely mechanical, and no field that exists only because the template had it.
- 04
Website as part of the system
The site stops being a brochure and becomes the front of the pipeline: forms that write to the record, availability and pricing that are real, and handover to a human without repeating anything.
- 01
An integrated CRM with a single customer record across channels
- 02
A unified inbox with ownership, SLAs and response measurement
- 03
Website and forms wired into the pipeline, with attribution that reconciles
- 04
Documentation and training so the team runs it
Invariant
One customer, one record. Every metric downstream depends on it.
- Which CRM do you work with?
- The one you have, if it can do the job — most can. Where a platform genuinely cannot support the model, we say so and price the alternative. We take no vendor commissions, which is why the recommendation is worth reading.
- Can you connect WhatsApp properly?
- Through the official Business API, with the number, templates and history owned by the company rather than by an employee's handset.
- How long does an integration take?
- A focused integration runs four to eight weeks. The variable is never the software; it is how many places the customer record currently exists in.
Each one carries what it is good for, what it is proven on here, and the point at which it stops working. We take no vendor commissions on any of them.
- Respond.io
- An omnichannel inbox that puts WhatsApp, Telegram, Instagram, web chat and email behind one conversation record.
- WhatsApp Business API
- Meta's official programmatic channel for businesses on WhatsApp, rated by how many conversations a number may start per day.
- Supabase
- Managed PostgreSQL with an authentication service, file storage and a generated HTTP API in front of it, addressable directly from a browser.
- Telegram Bot API
- Telegram's programmatic interface: bots that hold a conversation, and web apps that render a full interface inside the chat.
- Document extraction
- Reading the fields off a photographed document — passport, Emirates ID, driving licence, trade licence, vehicle registration, insurance, an odometer, an invoice — and filing them against a record.
- From an enquiry arriving to somebody answering it
- A message from a person who might buy, travelling from the form they filled to somebody who can actually answer what they asked. 6 steps, 6 known jams.
- From a customer’s question to an answer the business can stand behind
- One question arriving at an automated agent, and everything that has to hold for the reply to be something the company would have said itself. 7 steps, 7 known jams.
Bring one week of enquiries from every channel you run and we will trace each one: where it landed, how long it sat, who owned it, whether it exists in the CRM at all. In most companies the answer is visible in an afternoon and it is not the CRM's fault. You get the trace whether or not the work follows.