In US insurance a CRM is almost never “just a funnel.” The cycle runs through quote, bind, policy download, commission, endorsement, then renewal. A P&C agency, a Medicare shop, and a life producer do not buy the same stack — and a generic sales CRM does not hold a policy number, a carrier statement, or an E&O file by itself.
There is a third group that is easy to confuse in a demo: the sliced stack. AMS, comparative rater, commissions engine, and sales CRM are often separate products from the same brand — or a layer that syncs into someone else’s policy system. This yardstick marks a feature native only when it ships in the product under review. A sibling SKU (AgencyBloc Commissions+ next to AMS+, EZLynx Rating Engine sold beside the management system when it is not embedded, Salesforce Digital Insurance next to Financial Services Cloud Core) counts as missing — and the profile explains what lives next door.
Native messaging on the client or policy record (two-way SMS/inbox or WhatsApp API) is on the yardstick. One-way blasts, portal-only chat, and marketplace bridges do not count.