Field force is the most expensive line in promotion and the least measurable one. NUMU CX makes the medical visit itself measurable: every conversation scored against your own model, cycle messages tracked to the doctor, compliance and adverse events caught the same day.
Double visits cover roughly one visit in twenty, and the rep behaves differently when the manager is in the room. Everything else reaches headquarters as a CRM entry written from memory in the evening.
And those few are observed under conditions that change the behaviour being observed.
The same territory, the same portfolio, the same cycle materials — and a difference that nobody can currently explain with data.
A doctor mentions a suspected adverse event in passing. If the rep does not recognise it, the SLA is already running and nobody knows.
Visits to doctors by specialty and category, with the visit model scored stage by stage and cycle messages tracked per brand.
Conversations at the counter, recommendation share, stock and display objections — the same scoring logic applied to the pharmacy floor.
Negotiations with chains, hospitals and procurement, with commitments and next steps captured rather than remembered.
Remote visits and outbound calls scored against the same standard, so channels can finally be compared to each other.
Pre-call through post-call, scored on the scale your trainers use, with the checklist calibrated against visits your own team has already run.
Your portfolio, competitor brands, dosages and therapeutic areas — so detailing time per brand is measured, not estimated.
Share of message per brand and per specialty, so the brand team learns mid-cycle which arguments are actually reaching doctors.
A suspected case is checked against the four validity criteria and routed to pharmacovigilance inside the 24-hour SLA, with the transcript attached.
Off-label claims, unsupported head-to-head comparisons, incentives and events offered in exchange for prescriptions — flagged in the same pass.
Whether A, B and C category doctors are actually being seen at the planned frequency — verified against real visits rather than planned routes.
Masking happens before storage, not after. Capture of the other party stops without consent. The whole platform can run inside your own perimeter, which is what turns local data-residency and privacy requirements from a legal risk into a checkbox.
Role-based access means a rep sees their own visits, a first-line manager sees their team, and every access is written to an audit log.
Capture of the other party stops if consent is not given, and that state is logged. Patient names and details are masked before storage — the architecture assumes the strictest reading of health-data rules from day one.
Yes — your stages, your scale, your FABS structure and your cycle key messages, calibrated with your trainers during the pilot until the AI's scores agree with theirs on the same visits.
The fragment is checked against the four validity criteria and routed to pharmacovigilance the same day, inside the 24-hour SLA, with the transcript attached — whether or not the rep recognised it in the moment.
Launches run coaching-only: scores visible to the rep and their first-line manager, not to HR. Reps get feedback minutes after the visit plus reference examples from teammates — which is why field teams end up defending the tool, not fighting it.
Eight to ten reps, your portfolio in the dictionaries, your checklist calibrated with your own trainers. It ends with a report on real visit quality, share of message and the compliance picture — plus a scale-up plan.