A queue to work, not a database to search.
Most CRMs give a relationship manager a search box and a list of everything. AcuityQ gives them the eleven things that need doing today, in the order that makes the day work — and the buckets are defined by where a lead actually stopped, not by a stage somebody remembered to set.
Screens in this module: My day · Smart views · Leads & opportunities · Dialler & campaigns · Meetings & follow-ups
My day
Tuesday · 14 actionsWhat it does
Six things, stated plainly
My day, not my pipeline
Calls due, follow-ups, drop-off cases and meetings for today, with the overdue ones first. Counters for accounts and revenue month to date against target, so nobody has to open a report to know where they stand.
Smart views that name the problem
Buckets by the actual stopping point — stuck on the e-Sign page, bank proof rejected, KYC mid-validation, aged 30 days with no dial, unreachable and due for re-churn. Each one carries its recoverable value and its average age.
A dialler, not a phone
Click-to-call with screen-pop and automatic logging through the telephony plug-in. Disposition is captured at wrap, not from memory at 6 p.m.
Rules that stop harassment
At most two automated calls per campaign per lead. Manual call-backs are unlimited. Unreachable numbers re-churn the same day; DND and not-interested are hard-excluded from dialling altogether.
Collaboration across verticals
A lead can be worked jointly where a second vertical is needed, with both contributions visible on the record and attribution recorded rather than argued about later.
Meetings logged where they happened
Client meetings, stakeholder meetings with bank RMs, CAs and channel partners, and the revenue attributed to each. Geo-verification where the branch requires it.
Screen flow
A lead, from arrival to account
The path a retail lead takes through the sales desk. The gate in the middle is the point most CRMs skip, and it is the reason a book stays clean.
- Lead arrives
From a campaign, the website, a branch walk-in, a partner code or an uploaded sheet. Source is stamped and never edited afterwards.
Automatic - Duplicate check
PAN and product is an exact match and a hard block. Mobile, e-mail and fuzzy name with city are soft matches that warn and offer a merge.
Gate - Routed to an owner
City to branch where they match, nearest serviced cluster where they do not, mapped code for partner-sourced, central desk for the rest.
Routing rules - Worked from a smart view
The RM dials, meets, or sends. Every touch is logged with its disposition and the follow-up SLA clock starts.
Sales RM - Opportunity created
Contact-level and product-level, carrying an estimated value that weights the pipeline by stage.
Sales RM - Account opened, or re-churned
Converted leads carry into the customer record. Aged and unreachable leads return to the pool under a governed transfer rather than dying on a desk.
Automatic
How it actually behaves
Duplicate prevention, rule by rule
The engine that keeps one person from becoming three records. Hard blocks stop the save; soft matches warn and offer a merge, because a genuine second product for the same person is not a duplicate.
| Match on | Action | Why |
|---|---|---|
| PAN + product | Hard block | The same person cannot be entered twice for the same product. There is no legitimate case for it. |
| Mobile + product | Soft warn | Families and firms share numbers. The RM is shown the existing record and decides. |
| E-mail + product | Soft warn | Same reasoning. A shared office address is common in small firms. |
| Fuzzy name + city + product | Soft warn | Catches spelling variants and transliterations that an exact match would miss. |
Every block and every merge is recorded with who decided and when, so a disputed lead has an answer rather than an argument.
Who works here
The roles this module belongs to
AcuityQ™ is one platform. What a person sees is decided by the capabilities their role holds and the scope they sit in — see every role side by side.
Manager / supervisor
Sees the whole organisation and can drill from it to one person without changing screen. Sets targets, thresholds and escalation policy, and approves the transfers that move a book from one person to another.
- Enterprise dashboard
- Targets & achievement
- Productivity & activity
- Leaderboard
- SLA & escalations
Retail sales RM
Works a queue rather than a database. Opens on the day’s agenda, moves through smart-view buckets that are defined by where a lead actually stopped, and dials from inside the product rather than from a phone on the desk.
- My day
- Smart views
- Leads & opportunities
- Dialler & campaigns
- Meetings & follow-ups
Honest limits
What this module does not do
Stated here so nobody spends a procurement cycle discovering it. If one of these is a requirement, say so early and we will tell you whether it is on the roadmap or simply not our product.
It is not a telephony platform
AcuityQ dials through your switch and logs the result. It does not run the switch, the IVR or the recording, and it does not replace your telephony contract.
It does not open the account
Account opening happens in your back-office system. AcuityQ tracks the stage, shows where it stopped, and hands the customer back — it is not the KYC engine.
It does not score leads for you on day one
Predictive lead scoring needs your own conversion history to be worth anything. It is configured after a few months of real data, not switched on at go-live.
Questions
What a buyer asks in the second meeting
What stops an RM simply working the easy leads?
Smart views are defined centrally and the counters are visible to their team leader. A bucket that nobody touches for a week is visible as a bucket, not buried in a list, and the threshold rules in the command centre can raise a coaching task automatically.
Can a lead be worked by two people?
Yes, where a second vertical is genuinely needed. Both contributions sit on the record and the attribution is recorded at the time. What is not possible is two people separately working the same lead without either knowing.
What happens to a lead nobody converts?
It ages. At thirty days with no dial it leaves the dialler and becomes a governed transfer candidate — back to the pool, or re-assigned in bulk with an approval above the threshold. It does not sit on a desk indefinitely.
Does the dialler work with our telephony?
It integrates through a CTI plug-in for click-to-call, screen-pop and automatic logging. Which switches are supported today is an integration question — ask, and we will tell you whether yours is one of them rather than promising it is.
See sales desk against your own desks
Bring the thing you cannot currently do. Simcomm replies within one working day.