Qualify every lead, call only the ones worth calling
Conversational qualification against your criteria, scored 0–100 by an explainable rule engine with BANT, CHAMP and MEDDIC presets, synced to your CRM.
- Start with one module
- No rip-and-replace
- Hosted in the region you choose
Illustrative interface. Names, scores and figures are sample data, not a performance claim. The screen shows an OptiML universal inbox filtered to new leads arriving on WhatsApp, voice and a web form, each carrying a qualification score. The panel below breaks one lead's score of 78 out of 100 into its budget, authority, need and timeline components, names the BANT preset it was scored against, and shows the routing decision written back to the CRM.
Answered in seconds, scored with its reasons
A score nobody can explain is a number a rep will ignore. This one shows its working.
-
Step one
Set the criteria
Define your criteria, or start from a BANT, CHAMP or MEDDIC preset.
-
Step two
Respond within seconds
An AI agent responds to every inbound lead within seconds on WhatsApp or voice.
-
Step three
Qualify in conversation
Qualification happens conversationally, not as a form, and the score explains itself.
-
Step four
Route or nurture
Qualified leads route to a rep with the transcript; the rest enter a nurture journey.
What sits under the score
Scoring, segmentation, the channel it answers on and the record it writes to.
Segments, scoring and CRM write-back
Segments are built from AND/OR filter rules over demographic and behavioural signals, and CSV import detects duplicates on the way in. Leads are scored from 0–100 by an explainable rule engine with BANT, CHAMP and MEDDIC presets, and the results sync back to Salesforce, HubSpot, Zoho or Pipedrive idempotently.
WhatsApp, properly
WhatsApp Business Cloud API with template management, interactive buttons and lists, media, and commerce flows including WooCommerce catalogues. Inbound replies route into the same queue as everything else, and outbound campaigns respect the same consent and DNC rules as the dialer.
Cross-channel continuity
A unified customer key ties phone, email and your own identifiers together. When someone who called yesterday messages today, their history is retrieved and injected into the agent’s context. The agent picks up where the call left off.
Nurture journeys for the rest
Multi-step, audience-segmented journeys with send-time optimisation and journey-level A/B testing. Onboarding sequences, renewal nudges, win-back campaigns and post-purchase follow-up, all orchestrated across whichever channel each customer actually responds on.
Scripts that personalise
The template engine handles variables, conditionals and loops, with a catalogue of the available variables and a live preview against a real contact record. The AI agent adapts the script naturally; the human agent sees the same script in the desk.
Compliance that fails closed
Do-not-call enforcement runs across national, internal and client-supplied lists, consent is captured and verified, and calling windows are enforced by the contact’s own timezone and local public holidays. The gate blocks the call rather than logging a warning after it.
What you need before you start
Your qualification criteria and a CRM to sync to.
In practice
A property developer responds to portal enquiries within seconds, captures budget, timeline and location, books site visits for the qualified, and nurtures the rest until they’re ready.
You’ll need
- Your qualification criteria. Your own, or a BANT, CHAMP or MEDDIC preset you then edit.
- A CRM to sync to. Salesforce, HubSpot, Zoho or Pipedrive, written idempotently so the same lead never lands twice.
We publish outcome figures only with the customer's written approval, so this slot stays empty until one is signed off. In the meantime the mechanism above is the honest version.
Customer story
A named customer story replaces this block once the quote and the figure are approved in writing. Until then the scenario above stays unnamed and generic, and no conversion number appears on this page.
Fast is easy. Compliant is not.
68 CRM workflow nodes
Salesforce, HubSpot, Zoho and Pipedrive, synced idempotently so the same lead never lands in the pipeline twice.
8 channels, one record
WhatsApp, web chat, SMS, Messenger, Instagram, Telegram, Discord and email against a unified customer key.
Compliance that fails closed
DNC lists, consent capture and calling windows enforced by the contact’s own timezone before the dial, not logged after it.
231 tables under row-level security
Tenant isolation enforced by PostgreSQL row-level security, so a defect in application code cannot leak data across tenants.
The capabilities behind it
Each of these is a product surface with its own page, not a bullet on this one.
Lead scoring
0–100 with an explainable rule engine and BANT, CHAMP and MEDDIC presets, alongside segmentation and predictive dialing. OutboundInstant WhatsApp response
WhatsApp Business Cloud API with templates, interactive buttons and media. Inbound replies land in the same queue as everything else. OmnichannelNurture journeys
Multi-step, audience-segmented journeys with send-time optimisation and journey-level A/B testing. AutomationCRM sync
Two-way sync with field mapping across Salesforce, HubSpot, Zoho and Pipedrive, with 68 CRM workflow nodes. CRM connectorsSpecification
Every figure on this page is a platform figure, not a customer outcome.
| Scoring | 0–100, explainable rule engine, BANT, CHAMP and MEDDIC presets |
|---|---|
| Segments | AND/OR filter rules over demographic and behavioural signals |
| Import | CSV import with duplicate detection |
| Channels | WhatsApp, web chat, SMS, Messenger, Instagram, Telegram, Discord, email |
| Identity | Unified customer key across phone, email and custom identifiers |
| Scripting | Variables, conditionals, loops, variable catalogue, live preview |
| Journeys | Multi-step, segmented, send-time optimised, A/B testable |
| CRM sync | Salesforce, HubSpot, Zoho, Pipedrive — idempotent |
| Compliance | DNC lists, consent capture, two-party-consent announcements, calling windows |
Related use cases
Outbound sales
Dial more, and dial the right ones — predictive pacing against agent availability. Read the use caseAppointment booking
Booked against real availability, reminded automatically. Read the use caseWhatsApp customer service
Serve customers where they already message, with the same agent and knowledge. Read the use caseThe platform underneath
Everything on this page is the OptiML CX Platform configured for Lead qualification, not a separate product. These are the modules it leans on.
See it handle one of your real conversations
Bring a call recording, a policy document or a WhatsApp thread from your own operation. We will ground an agent in it and run it live on the call, not a canned demo.
- 30 minutes
- A working agent grounded in your content
- No slide deck unless you want one
Book a demo
30 minutes, on your own content. No slide deck unless you want one.
Your details stay private. We never share them.
