What Agents Actually Ask For in a CRM: A Dialer, Two-Way Texting and Lead Import That Works
Nobody asks for a pipeline view. They ask for the phone, the texts and the leads in one place. Six requirements and five questions to ask on any demo.
Strip the vendor pitches away and the CRM questions agents ask are remarkably consistent. These are questions from agents like you. One agent wrote the spec out in full: a built-in dialer, two-way texting, strong lead tracking and follow-up, and a bonus for Facebook ad integration and easy lead importing. Another asked for a dialer and CRM that could "load leads from a number of different vendors into and work them all" with text drips. A third, on a team hunt, listed "CRM, dialer or VA, pre-booked appointments." Nobody asked for a pipeline view. Nobody asked for AI. They asked for the phone, the texts and the leads to be in the same place. This post is that spec, written as a checklist you can hold any product against, ours included. 1. The phone lives in the CRM Click a contact, place the call. The call, its duration and its outcome are logged on that contact without anyone typing. Inbound calls pop the contact on screen before you answer, with the last note visible. Calls are recorded, and the recording is attached to the contact, not sitting in a phone system nobody opens. If the agency already has a business phone system, the CRM should work with it rather than replace it. Why it matters: every metric worth coaching, contact rate, time to first attempt, talk time by outcome, depends on the call being logged where the lead is. We covered those numbers in Dials Don't Pay. Talk Time Pays. 2. Texting is two-way, from a number the agency owns Replies land in the contact's conversation, next to the calls, not in an agent's personal phone. Texts go from the agency's number, so a departing agent does not take the thread with them. Stop replies are honored automatically and the opt-out applies across the whole agency, not just the agent who received it. Bulk campaigns are paced. A thousand texts in one minute is how numbers get flagged. 3. Leads come in from anywhere, with the source attached Vendor deliveries by webhook, with the lead source set on arrival. Spreadsheet imports that map the vendor's columns once and remember the mapping. Carrier exports for existing clients, so the book is in the CRM on day one. Duplicate detection that understands a household: a spouse sharing a phone number is not a duplicate. This is the "load leads from a number of different vendors" request. If the import requires reformatting the vendor's file by hand each time, agents stop importing and the CRM goes stale within a month. 4. Follow-up runs on a schedule, and stops when a human takes over A new lead triggers the first call task and the first text without an agent remembering to do it. A sequence of touches runs over days, at different times of day. A reply, or a logged conversation, stops the sequence. Nothing is worse than an automated "just checking in" text arriving an hour after the client said no. The sequence itself is in The Lead Isn't Dead, Your Follow-Up Is . 5. The policy is a record, not a status Most CRMs stop at "closed won." An insurance CRM needs the policy as its own record: carrier, product, policy number, effective date, premium, and the people it covers. Otherwise renewals, anniversaries, cross-sells and commission matching all have nowhere to attach. 6. It knows what it is for Insurance is not generic sales. Health information needs access controls and logging. Medicare work needs the Scope of Appointment stored. ACA work needs the enrollment to write back. A generic CRM can be bent into this shape, at the cost of the agency maintaining the bend forever. The questions to ask on the demo Place a call from a contact. Where did the recording go? Text a contact and reply from your phone. Where did the reply land? Import this vendor's file. How many columns did I have to rename? Show me a policy record. Now show me every policy this household holds. What happens to the automation when the client texts back? Where AgencyView fits AgencyView was built to this list. Calls run through RingCentral or the CRM's built-in phone, are recorded, transcribed and logged on the contact, and inbound calls pop the record on screen. Texts go from the agency's number with opt-outs enforced agency-wide and campaigns paced. Leads arrive by vendor webhook, by spreadsheet import, or from the built-in lead marketplace, and duplicate checks understand households. Policies, household members, medications and providers are records attached to the contact. ACA quotes and enrollments run through HealthSherpa from the client record. It is one subscription that includes the CRM, calling and texting, commissions and the HIPAA program; the comparison with a general-purpose CRM is in AgencyView vs. Salesforce: What an Insurance Agency Actually Pays .
Where AgencyView fits
Keep reading
Share: Facebook · LinkedIn · X · Email
All articles · AgencyView