A useful vendor review covers origin, sharing, permission evidence, replacement terms and outcome reporting. Ask for concrete records and contract definitions rather than accepting a volume promise.
Ask for the origin, not just the product name
Request the collection channel, landing-page example and description of the advertised offer. Determine whether the vendor collects inquiries directly, buys them from another supplier or combines several sources. An agency should be able to understand the chain between the person's request and the delivered record.
Ask for a redacted demonstration showing collection timestamp, source identifier, geography, permission evidence and delivery timestamp. A vendor can explain field structure without exposing an unrelated person's sensitive information. Refusal to describe provenance is a meaningful procurement concern even when the sales presentation promises volume.
Put distribution and replacement terms in writing
Clarify whether records are exclusive, shared or resold later. Define duplicate, invalid contact, wrong geography and ineligible audience conditions. Ask how quickly replacements must be requested and whether credits expire. A replacement policy that requires evidence the agency cannot capture is difficult to use.
Confirm minimum purchase obligations, cancellation timing and whether a delivery cap can be reduced. Seasonal capacity changes should not force a solo agent to buy more records than can be handled. Compare payment commitments with a realistic pilot before entering a recurring contract.
Test the evidence handoff
Have the vendor deliver a demonstration record through the proposed integration. Confirm that supporting evidence remains accessible after the data enters the CRM. A CSV containing only name, telephone number and a consent label may lose essential context during import.
For beneficiary acquisition, route the proposed workflow through current CMS and carrier review. Ask the vendor to identify which documents support its claims, while keeping the agency responsible for its own assessment. A vendor's generic assurance is not equivalent to verifying the actual collection and intended outreach.
Use a procurement scorecard
Score each source on provenance completeness, audience fit, sharing clarity, integration reliability, operational cost and flexibility. Give each category a documented reason; do not reduce review to a single price ranking. Define mandatory conditions that cannot be offset by a low cost.
- Who created the original collection material and maintains its versions?
- Can a delivered record be traced back to the exact material shown?
- What happens if the source or sharing terms change mid-contract?
- How are suppressions, withdrawals and record corrections communicated?
Review an illustrative pilot before scaling
Suppose two vendors deliver fifty records each. One delivers a lower price but cannot retrieve evidence for ten records. The other supplies complete evidence and an integration that preserves source fields. Calculate appointment outcomes for both, while separately documenting which records the agency could use appropriately.
Hold a review with the person who handled the records, not only the buyer who negotiated the contract. Ask which fields were missing, how disputes worked and how many hours the batch consumed. Continue only when the evidence, economics and delivery process support an actual operating decision.
Questions agents ask
Should agencies request a sample lead record?
Yes, using a privacy-appropriate sample or demonstration. The review should show fields and evidence without unnecessarily exposing real beneficiary data.
Sources & further reading
Primary references for the rules and platform mechanics discussed here. Templates and recommendations are Medicare Marketing’s planning guidance. Examples are illustrative unless explicitly sourced.
Turn the idea into a next step.
Use the free toolkit to check your local foundation, build a content rhythm, or plan a webinar.
Explore the tools →