A WhatsApp broadcast to everyone
One message to the whole list is fast to send and easy to ignore. It doesn't mention what anyone actually asked about, unconsented contacts report it, and a spike of blocks can get your business number restricted.
Any business with a CRM · Solution
Years of enquiries are sitting in your CRM. Nobody's talking to them.
Soluvide builds lead reactivation for UAE businesses with a CRM full of past enquiries and lapsed customers. The system reads each contact's history, writes a personalised WhatsApp or email message that picks up where the last conversation stopped, sends it in small batches your team approves, and routes anyone who replies with real interest to a salesperson. It only contacts people with consent, uses Meta-approved WhatsApp templates and honours every opt-out.
- Messages built from each contact's own history
- Consented contacts and approved templates only
- Your team approves every batch before it goes
- Opt-outs written back to the CRM
The problem
The leads didn't say no. They just went quiet.
What the day actually looks like — described as an operator would, not as a brochure.
Open your CRM and filter for older enquiries that never closed. There will be a long list of people who asked for a quote, booked a viewing, came in for a consultation or bought once and never came back. Most of them never said no. The timing was wrong, the budget wasn't approved yet, or the salesperson who owned them left.
Those contacts cost real money to win the first time, through ads, portals, events and sales time. Yet the marketing budget goes on finding new strangers, while people who already know your name sit untouched because nobody has the time to go back through them one by one.
When someone does try, it's usually a generic broadcast: one message to the whole list, sent on the same afternoon. It ignores what each person asked about, lands as spam, gets a burst of opt-outs and blocks, and puts the WhatsApp number at risk. After that, the old list is treated as dead.
The problem isn't that old leads are worthless. It's that reaching them properly — personally, carefully, one at a time, within the rules — is slow manual work no salesperson will prioritise over a fresh lead.
Why the obvious fixes fail
You've probably already tried these.
None of them are stupid. They fail because the work itself stays manual — they just move who does it.
Asking sales to work the old list
Salespeople will always prioritise the lead that came in this morning over a contact from last year. Going through old records takes hours of reading notes before writing one message, so it slips to "next week" indefinitely.
An email newsletter
A monthly newsletter keeps your name in an inbox, but it's the same content for everyone and asks for nothing in particular. It doesn't reopen a specific conversation, so it rarely turns a dormant enquiry back into a deal.
What we build
Personal messages, small batches, a person signs off.
The honey step is where a person stays in control. Everything else is the typing and checking the system does for you.
- CRM export
- Clean & segment
- Draft messages
- Approve batch
- Send & reply
- Route to sales
Engineering decision. We send in small, approved batches rather than one big blast. It is slower, but it keeps the WhatsApp number healthy, lets your team handle the replies properly, and means a person has seen every message before a past customer reads it.
- 1
Pull the history
The system reads past enquiries and customers from your CRM, with their notes, quotes, stages and last-contact dates. Nothing is copied into a third-party marketing list; it works from your own records on your own accounts.
- 2
Clean and segment
Duplicates are merged, invalid numbers and closed accounts removed, and consent and opt-out status checked. Contacts are grouped by what they asked about and why they stalled — quoted but didn't decide, booked but didn't show, bought once and lapsed — because each needs a different message.
- 3
Draft personalised messages
For each contact the system drafts a short message in English or Arabic that refers to their actual enquiry and offers a relevant next step. WhatsApp openers use templates approved by Meta on your account; email is used where WhatsApp consent isn't on record.
- 4
Your team approves the batch
Before anything is sent, a person on your team reviews the batch: the segment, the drafts, any offer mentioned. Batches are kept small and spread over days so replies can be handled properly and the number stays in good standing.
- 5
Send and handle replies
Approved messages go out and the system answers replies as a conversation: it asks what they need now, answers simple questions and offers to book a call or visit. Opt-outs and "wrong person" replies are recorded immediately and the contact is closed.
- 6
Route to sales and log
Anyone showing real intent is handed to a named salesperson with the old history and the new conversation in one record. Every outcome — reply, booking, opt-out, no response — is written back to the CRM, so the list gets cleaner with each round.
Named systems, not “connects to anything.”
We confirm exactly which CRM and channels connect during scoping. The system commonly touches:
- HubSpot
- Zoho CRM
- Salesforce
- Odoo
- WhatsApp Cloud API
- Google Workspace / Outlook email
- Google Sheets
- Google Calendar
Engineering decisions
Clear lines, agreed up front.
What the fixed price covers, and the things we will not build. Both are written into the scope before we start.
In scope
- Cleaning, de-duplicating and segmenting your past enquiries and customers
- Checking consent and opt-out status before anyone is contacted
- Personalised messages built from each contact's CRM history
- WhatsApp via approved templates, email where WhatsApp isn't appropriate
- Small, approved batches spread over time
- Answering replies, qualifying and booking the next step
- Writing every outcome, opt-out and booking back to your CRM
Not in scope
- Messaging bought, scraped or unconsented lists
- Sending the same blast to your whole database at once
- Discounts or offers your team hasn't signed off
- Pressuring people who've said no — opt-outs are final
What you get
Live in weeks, quoted before we start.
Most reactivation systems go live in about two to four weeks. What moves it inside that range is the size and state of your CRM data, how many segments need their own message angle, template approval with Meta, and which CRM and email system it connects to. No hourly billing, no surprises.
- 1Week 1
We map the work, then quote it
A short call, then we document what's in your CRM, what consent you hold and why old deals stalled — including the exceptions and the workarounds people built around it. You get a written scope, acceptance criteria and a fixed price before any build begins.
You get: Scope + fixed quote
- 2Weeks 2–4
We build on the tools you already run
HubSpot, Zoho CRM, Salesforce and the rest of your stack — no rip-and-replace. Outputs are structured and checked against your own data, not trusted blindly.
You get: Working system on your stack
- 3Go-live
Your team approves, then it runs
The human step is tested with the people who will own it before anything goes out. Logging and alerts so problems surface early, documentation your team can read, and you own the code and the accounts.
You get: Approval gate, monitoring, full ownership
Restart conversations you already paid to start.
Tell us which CRM you use and roughly how far back your enquiries go. We reply within one business day, and the price is fixed after a free scoping conversation.
Questions owners ask
Straight answers.
If yours isn't here, send it on WhatsApp and you will get a straight reply.
Prefer a form? Contact pageNo. A blast sends the same message to everyone on a list. This works from what your CRM actually knows about each person — what they asked about, when, what they were quoted, why the deal stalled — and writes a message that refers to that. Contacts are sent in small batches your team approves, and anyone who replies is answered as a conversation, not as a campaign.
Related solutions
Other problems we engineer away.
Services behind this build
Each service page lists exactly what is included and the questions owners ask before they start.