Veeva and IQVIA Added Voice to the CRM. What Happens to the Data After That?
The two largest names in pharma CRM now let reps report by voice and get an AI briefing before a call. That is real progress. This post looks at what those tools do, where they are centred, and why Solvara Field starts from a different question: not how the report gets written, but whether the strategy is working.
What changed in the last year
For years, a pharma rep's visit ended the same way: a few taps in the CRM, a product selected from a list, a call marked as completed. Free text was restricted for compliance reasons, so almost nothing about the conversation itself was recorded.
That is changing. Veeva made its first AI agents for Vault CRM available in December 2025, including a Pre-call Agent, a Voice Agent and a Free Text Agent. Its Agentic Call Report lets a rep dictate after a visit; the AI turns the dictation into the call report inside Vault CRM, and a monitoring agent checks the text for compliance issues. Veeva calls the result Commercial Evidence.
IQVIA introduced its Field Force Agent in September 2025: an AI assistant for reps, key account managers, MSLs and managers that supports them before, during and after a call. It works with CRM platforms such as Veeva and Salesforce, or as a standalone mobile app, and draws on IQVIA's own data assets.
Both are serious products from companies that know this industry well. Making voice and free text usable again in a regulated environment is a meaningful step, and the compliance work behind it is not trivial.
Where these tools are centred
Look at what each tool is built around, and a pattern appears. The centre is the rep's workflow and the CRM record: prepare faster, report faster, write richer notes, stay compliant.
The record gets better. What a company then does with thousands of richer records is largely the company's own job. Veeva, for example, offers data access so that customers can power their own AI and analytics, and lets them embed external agents. That is a reasonable design for a platform that serves hundreds of companies with different products and strategies.
But it means the last step, the one that turns visit data into an answer, still has to be designed and built by someone.
The question a product manager actually has
A product manager does not lie awake wondering whether calls were logged. The questions are different:
- Is our key message actually reaching physicians?
- How do they react to it, and does that differ by specialty or region?
- Which objections keep coming up?
- Is the campaign we launched last month working in the field?
- Which reps deliver the message consistently, and who needs coaching on what?
Answering these takes four things in a row: capture that is designed around those questions, structuring of what was said, analysis across all visits, and delivery of the result to the person who can act on it. If capture and analysis are designed separately, the gaps show up exactly where the answers should be.
How Solvara Field is built
Solvara Field is built as one system from the visit to the decision.
Before the visit, the assistant briefs the rep: the last conversation, open questions, today's key message, likely objections.
After the visit, the rep reports by voice in about two minutes. This is a short conversation, not dictation: if the rep did not say whether the key message was delivered or how the physician reacted, the assistant asks.
Then the system structures it: message delivered, reaction, objection, open question, follow-up promised. Not a paragraph of notes, but data that can be counted and compared.
And it analyses it: product managers see which messages land and where they meet resistance. Regional managers see how consistently each rep works and where coaching is needed. The rep gets a better briefing next time.
The CRM stays where it is. Solvara Field works alongside it, and each deployment is built around one company's products, messages and team structure.
Side by side
| CRM-centred voice tools | Solvara Field | |
|---|---|---|
| Starting point | The call report and the rep's workflow | The question "is the strategy working?" |
| Voice | Dictation that becomes the call report | A short conversation that asks for what is missing |
| What is stored | Richer notes in the CRM record | Messages, reactions, objections and follow-ups as structured data |
| Analysis | Data made available for the company's own analytics | Built in, delivered to each role |
| Fit | A standard feature across many customers | Built around one company's products and messages |
| Strength | Scale, compliance tooling, industry data | Depth on one company's field strategy |
This is a comparison of where each product is centred, based on the vendors' public materials. It is not a claim that one replaces the other.
Which one do you need?
If your problem is that reps spend too long on administration, the voice features in your CRM are the natural place to start. Use them.
If your problem is that you cannot tell whether your strategy is working in the field until the sales figures arrive months later, faster reporting will not fix it. You need the whole chain, from what was said in the visit to what a product manager sees on Friday.
The two are not mutually exclusive. A company can run Vault CRM, use its voice features, and still want a system whose only job is to answer strategy questions from the field.
Final thoughts
Voice in the CRM solves the reporting problem. It does not, by itself, solve the insight problem. The data getting richer is the beginning, not the end.
Solvara Field exists for the part that comes after: turning what happens in each visit into answers that product and regional managers can act on. If that is the gap you feel, see how it works or talk to us about your field team.
Product descriptions are based on Veeva's and IQVIA's public materials as of November 2026. Veeva, Vault CRM and IQVIA are trademarks of their respective owners.
See it on your own data
Tell us about your team and we'll show you what this would look like for you.
Book a Demo

