The Insurance Agency Client Intake Form Template
A copy-paste client intake form template for Medicare, ACA, life and final expense agents, built around household, consent and Scope of Appointment fields a generic form misses.
The Field-by-Field Client Intake Form for Medicare, ACA and Life Agencies A client intake form for an insurance agency has to do three things at once: collect the household and coverage details an agent needs before the first real conversation, capture the compliance record that goes with that conversation (consent, Scope of Appointment), and land every answer on the client's record without anyone retyping it. A generic "name, email, phone" form does the first job and skips the other two. Below is a field-by-field template built around what Medicare, ACA, life and final expense agencies actually need to ask, plus the compliance boxes each section has to check. Why a Generic Intake Form Falls Short Most intake-form templates are written for law firms or medical practices and ported over to insurance with a few fields swapped. They miss three things that are specific to this business: a household often has more than one person whose coverage decisions are connected (a spouse aging onto Medicare, a dependent about to turn 26), the client's medications and providers matter for Medicare Advantage and some underwriting conversations, and a Medicare appointment legally requires a signed Scope of Appointment before certain products can even be discussed. Build those three things into the form from the start, instead of bolting them on with a separate PDF. The Template Copy the sections that apply to the products the agency sells and drop the rest. Each section lists the fields and why they're there. Section Fields to collect Why it matters Contact & household Full name, date of birth, phone, email, mailing address, preferred language, preferred contact method (call, text or email) Routes the response to the right agent and sets how the agency is allowed to follow up Household members Name and relationship for a spouse or dependent, and date of birth for anyone approaching a plan-eligibility milestone (26, 65) Surfaces coverage conversations the household doesn't know it needs yet Current coverage Current carrier and plan type, renewal or effective date, reason for shopping Tells the agent what's changing and why, before the call Medications & providers Current medications, primary care and specialist providers Needed for Medicare Advantage plan-fit conversations and some health underwriting referrals Health conditions Relevant conditions the client wants considered in a plan or product recommendation Feeds plan-fit and underwriting conversations without a second phone call to ask Consent & communication preference Written consent to call or text, opt-in checkbox with the exact consent language shown, timestamp Documents consent the way a texting-compliance program needs it recorded Scope of Appointment (Medicare only) Product lines the client agreed to discuss, how the agent first made contact, typed or drawn signature, date Required before a marketing appointment can go beyond the scope the client agreed to Signature & acknowledgment E-signature, date, and (for Medicare) the beneficiary's own signature rather than the agent's Makes the record enforceable and auditable The Compliance Boxes an Insurance Intake Form Has to Check Scope of Appointment, if the agency sells Medicare Under 42 CFR 422.2264 , a Medicare Advantage agent can't market a product beyond what the beneficiary agreed to discuss unless it's documented in a Scope of Appointment, and that SOA is valid for 12 months from the date of the beneficiary's signature (or their initial request for information). Discussing a product line that wasn't on the original SOA means a new one is needed. Build the SOA section into the intake form itself rather than a separate paper form, and keep the signed record as-is once it's captured — it shouldn't be editable after the fact, since it's the agency's evidence of what the client actually agreed to. A Medicare agent CRM that captures the SOA at intake, rather than as a separate paper form, is one less place for that record to go missing before an audit. Consent to call or text The consent checkbox on an intake form is only useful if the exact language the client agreed to is captured along with the timestamp, not just a checked box. AgencyView's texting compliance checklist covers what that record needs to hold up to scrutiny. HIPAA, if the form touches health information Any medication, provider or health-condition field turns the form into protected health information once it's submitted. If the form is hosted or processed by a vendor other than the agency's own CRM, HHS's HIPAA guidance on business associates is clear that the agency needs a signed business associate agreement with that vendor before PHI touches its system. A CRM built for insurance agencies should carry that BAA already, instead of leaving the agency to track down a form vendor's compliance paperwork separately — the same way AgencyView's approach to HIPAA-compliant call recording keeps a BAA in place for recorded calls rather than leaving it to the agency. How the Form Should Flow Into the CRM Collecting the answers is half the job. The other half is what happens to them after submission. A few things to check for before an agency builds or buys an intake form: Answers write directly to the client record — household members, medications, providers and conditions should land on the contact without an agent re-typing them from a PDF. In AgencyView, an intake form's answers write straight into the CRM record this way, and can be sent by email or text in English or Spanish. New entries get deduplicated, not duplicated — if the same medication or provider is already on the household's record, a second intake submission shouldn't create a second copy. And a household sharing one phone number or email address is a household, not a duplicate contact — the form shouldn't merge people who happen to share contact information. The SOA becomes a permanent record, not an attachment that gets lost — once a Scope of Appointment is signed through the form, it should be stored as its own compliance record tied to the response, not edited or deleted afterward. Access is role-based and logged — anyone who opens a submitted intake form full of medications and health conditions should do so under an audit trail, the same as any other protected health information in the system. AgencyView's survey builder supports this with four layouts — a classic single-page form, a guided one-question-per-screen flow with a progress bar for longer intake forms, a split layout with a live summary sidebar for eligibility-style questions, and an agent-introduction layout that keeps the licensed agent's name and photo next to every question. Field types include text, email, phone, dropdown, multi-select, date, signature and file upload, so a signed Scope of Appointment or an uploaded ID can live in the same form as the household questions. Example: A Five-Agent Medicare and ACA Agency This is an illustrative example, not a real client or measured result. Picture a five-agent agency running AEP with a single intake form sent by text before every first call. The form collects household members, current coverage, medications and the Medicare Scope of Appointment in one sitting, bilingually. Before the form existed, agents spent the first ten minutes of every call re-asking questions a prior conversation already answered, and SOAs lived in a shared drive folder that nobody could search under audit. After the form, the agent opens the call already knowing the household and the medications that matter, and the signed SOA is already attached to the right contact before the phone rings. Rolling Out the Template Pick the sections that match the products the agency sells — drop Scope of Appointment entirely for an agency that only sells ACA and life, for example. Write the exact consent language the client will see and agree to, and keep it identical on every channel the form goes out on (text, email, web). Decide who on…
Where AgencyView fits
Keep reading
Share: Facebook · LinkedIn · X · Email
All articles · AgencyView