A lead has an owner, a clock and a way back out.
Most lead databases are where leads go to age quietly. AcuityQ™ gives every lead a stamped source, a duplicate check it has to pass, a named owner, a follow-up clock, and a governed route back to the pool when nobody works it — so the pipeline figure means something at the end of the quarter.
Screens in this module: Lead pipeline · Campaigns · Transfers & approvals · Thresholds & alerts
Lead pipeline
1,842 in scopeThe lead object
What a lead holds, and what each part is for
None of this is a custom field somebody added later. It is the shape of the object, which is why reporting on it does not require a data-cleaning exercise first.
A stamped source
Campaign, website, walk-in, partner code, uploaded sheet or referral — set at creation and not editable afterwards. Attribution arguments end here.
A named owner and a scope
One person owns it. Collaborators can be added for a cross-vertical opportunity, with each contribution recorded rather than negotiated at payout.
A follow-up clock
Every lead carries an SLA on the next action. Breaches are visible at the person, branch and region level and can raise a threshold action on their own.
A consent record
What the person agreed to, and against which version of the wording — currently 2026-09-v1 for anything captured on this website. Marketing consent is separate and defaults to off.
An activity trail
Dials, dispositions, meetings, messages, stage changes and transfers, each with who and when. It survives a merge and it survives a transfer.
A path out without re-keying
A converted lead carries into the customer record and the opportunity. An aged one returns to the pool through a governed transfer. Nothing is retyped either way.
Where a lead lands, and why
Four rules, in order. The point is not that they are clever — it is that every lead has a destination with a person's name on it, so "nobody called them" has an owner rather than being a property of the pile.
Round-robin is available and is rarely the right answer. It spreads work evenly and ignores who is on shift, who is already carrying forty open leads, and who speaks the language the lead wrote in.
| Rule | Goes to | Why |
|---|---|---|
| Lead city matches a branch city | That branch | The obvious case, and the majority of them. No cleverness required. |
| City has no branch | Nearest serviced cluster | Better a desk an hour away that will call than a national pool that will not. |
| Lead carries a partner or branch code | The mapped owner | A partner-sourced or branch-sourced lead belongs to whoever sourced it. Fixed mapping, no round-robin. |
| Nothing matches | Central desk | An explicit destination with an owner, not an unassigned pile nobody is measured on. |
Campaigns
Attribution that survives the argument
A campaign that cannot show which leads it produced and what they converted to is a cost line. AcuityQ carries the campaign through to the account, on a stated window.
Segment builder
Build the audience from the same fields the desks work with — segment, dormancy, products held, city, consent state — rather than from an export somebody filtered.
The funnel, end to end
Delivered, clicked, lead created, converted, and the revenue attributed inside the window. Blended cost per lead falls out of it rather than being computed by hand.
Consent is a filter, not a footnote
Anyone who has not given marketing consent, or has withdrawn it, is excluded from the audience by the platform. It is not left to whoever builds the list.
Scheduling and split tests
Schedule a send, and run variants against a split so the comparison is a measurement rather than an opinion about subject lines.
Reminders for abandoners
Someone who started an application and stopped is a defined segment, not a lost cause. Reminders go on a cadence with a cap, because a fourth message is harassment.
Responses become leads
A reply creates or attaches to a lead automatically, deduped against the book, and routed by the same four rules as everything else.
Governance
Moving a book is an approval, not an update
A resignation, a territory rebalance, a maternity cover, a bulk re-churn of aged leads. Each of these moves customer relationships between people, and each one is a transfer with a reason, an approver and a record — never a bulk edit somebody ran on a Friday.
- Raised
By a head, or automatically when the HRMS marks somebody resigned. The reason is a required field.
Manager or HRMS - Approved
By the named role for that size of move. Above the record threshold it takes two approvals, not one.
Gate - Previewed with PII masked
The approver sees the shape of what is moving — counts, values, ages — without a contact list in front of them.
Automatic - Executed
Ownership moves. Activity trails, consent records and open clocks travel with the lead.
Automatic - Recorded
Who asked, who approved, what moved, when. Reportable, and it is the answer when somebody disputes a payout.
Audit
Thresholds that fire before anybody notices
| When this happens | At | What the platform does |
|---|---|---|
| Lead conversion falls below the floor | Branch | Dashboard alert, e-mail to the branch head, and a task raised on the branch. |
| Leads aged past the dialling window | Person | Removed from the dialler and raised as governed transfer candidates. |
| Follow-up SLA breached | Person | Coaching task on the team leader, not a reprimand on the person. |
| A bulk transfer above the record threshold | Region | Dual approval — the requesting head and the business head, both recorded. |
Rules are written by your business admin, and every firing records the value that caused it — so a disputed alert can be checked rather than argued about. The full set lives in the command centre.
Two leads from one organisation will never merge themselves
Two people from the same firm enquiring in one week is the normal case, not the exception. AcuityQ creates both and surfaces the match — "three other leads from this organisation" — so a person decides.
Silent merging loses the second person's message, which is usually the more specific one. A hard block exists only where there is no legitimate second case: the same PAN for the same product.
The match rules
- PAN + product — exact, and a hard block. The save does not complete.
- Mobile + product — soft. Families and firms share numbers; the existing record is shown and the RM decides.
- E-mail + product — soft, for the same reason.
- Fuzzy name + city + product — soft. Catches spelling variants and transliterations an exact match would miss.
Every block and every merge records who decided and when.
Website enquiries do not reach the module yet
The pipeline above runs today. The intake endpoint that would let acuityq.ai post an enquiry straight into it does not — it is in build. We are saying so here rather than letting you find out in an integration workshop.
How a website enquiry travels today
On the day the intake endpoint is live, one switch flips and every parked enquiry replays into the module in the order it arrived. Nothing collected in the interim is lost, and nobody re-keys anything from a mailbox.
Why it is built this way
Your reply should not depend on a system being up. The enquiry is written down durably before the page says thank you, which is why the reference on the confirmation is a real reference.
What we will not do
We will not build a temporary admin screen for parked enquiries. It would become the thing people use, and the module would then have to displace a habit as well as a mailbox.
The promise stands regardless
A person replies within one working day whether the module is receiving or the mailbox is. When the module is live, that promise becomes something the platform measures.
Honest limits
What this module is not
Not a marketing automation suite
It builds audiences, schedules sends, splits variants and attributes outcomes. It is not a journey builder with a hundred branches, and it does not try to be.
It does not buy or enrich contact data
No third-party append, no purchased lists. Every lead in the system came from a source you can name, which is the only version that survives a DPDP question.
It will not market without consent
Anyone who did not tick the separate marketing box is excluded from every campaign audience by the platform. That is a mechanism, not a policy.
It does not score leads on day one
Predictive scoring needs your own conversion history to mean anything. It is configured after a few months of real data, not switched on at go-live.
It is not a dialler
Campaigns hand numbers to the dialler engine and the telephony platform. The sales desk page covers how that side behaves.
The website intake is not live
Stated again because it matters: enquiries from acuityq.ai are parked and notified, not delivered into the module. That changes when the endpoint ships.
See the pipeline against your own sources
Bring the source you cannot currently attribute. Simcomm replies within one working day — and yes, this form is one of the parked ones.