How to set up knowledge base for in network provider finder

Gather the source material your members use today to find doctors and understand their benefits. This usually includes:

• Provider directory exports – lists of in-network physicians, hospitals, and specialists, typically as PDFs or spreadsheets (save as PDF or plain text).
• Network and coverage rules – documents that explain which services are covered, referral requirements, and plan‑specific limitations.
• Member FAQs – existing help-center articles or internal agent scripts that describe how to use the in‑network finder.

Chatref accepts PDFs, URLs, sitemaps, and plain text. If your directory is behind a member login, export it as a PDF or point Chatref at a publicly accessible list. You’ll also need a Chatref account (new accounts get $50 in free credit with no expiration) and a domain where you can embed the widget later.

If the agent should personalize answers – for example, to filter providers by a member’s ZIP code or plan type – decide which fields you’ll capture (plan ID, member ZIP, date of service). You’ll use Chatref’s custom actions to collect this information during the conversation. For an overview of how Chatref supports Health Insurance Providers, see the industry page.

1. Create a new agent in Chatref
   Log in to app.chatref.ai and click “New Agent.” Give it a name your members will see, like “Plan Finder” or “Coverage Assistant.” Choose a primary color that matches your member portal.

2. Add your knowledge base sources
   In the agent’s “Knowledge” tab, upload the gathered documents. Click “Add source,” then select PDF, URL, or sitemap. For a large provider directory, uploading the PDF is usually fastest. If you have a searchable online directory, you can paste the URL – Chatref will crawl it and index the content. Add separate sources for network rules and member FAQs. Chatref reads and learns your content automatically; no manual tagging required.

3. Configure a custom action to collect member details
   Switch to the “Actions” tab and add a custom action. Name it “Collect member info” and define the fields you need: for example, Plan ID (text), ZIP (text), and Member Name (text). Make these required. When a member asks “Which dermatologists are in‑network near me?”, the agent will first ask for the plan ID and ZIP, then narrow the response using the information in your knowledge base. For more advanced workflows, you can later extend this action to trigger an API call to your own eligibility system, but the knowledge‑base‑only setup already answers basic “show me the list for plan X” queries.

4. Train and review
   Chatref trains on your documents as you add them. Wait a moment for indexing, then open the built‑in playground. Ask questions your members would ask: “Do I need a referral for a specialist under silver plan?”, “Show orthopedic surgeons in 90210 for my plan.” The agent should answer from your documents. If it returns an incorrect or generic response, check that the relevant source was uploaded and has the detail spelled out clearly. You can add supplementary documents or tweak wording.

5. Embed the widget
   Under “Widget” in your agent settings, copy the embed snippet. Paste it into your member portal or on the page where members look for provider information. Origin‑allow the domain so the widget appears only on your authorized site. The in‑network finder will now appear as a chat bubble on that page, ready to answer coverage and provider questions.

Before you announce the finder to members, test thoroughly:

• Basic lookup: “I have plan HMO‑100, who are the primary care doctors in 30303?” The agent should name practices listed in your uploaded directory.
• Specialist search with referral requirement: “Can I see a cardiologist directly under my plan?” It should indicate whether a referral is needed, based on your coverage rules.
• Missing data handling: “What about providers in Alaska?” If your directory has no Alaska entries, the agent should state that the information is not available, not make up an answer.
• Out‑of‑hours behavior: Test at night – the widget is always available, so you should receive a grounded answer instantly.

If any test fails, add the missing detail to your knowledge base or update the custom action prompt.

The agent returns vague answers, not specific providers.
Your uploaded directory likely wasn’t parsed fully. Export it as a clean PDF with one provider per row, and include provider name, address, and specialty. Avoid complex tables that Chatref may not interpret well. Re‑upload and test again.

It doesn’t filter by plan type even after capturing the plan ID.
The knowledge base must contain the mapping between plan IDs and network tiers. Add a simple document that lists “Plan HMO‑100: Providers in file A; Plan PPO‑200: Providers in file B.” The custom action only grabs the ID; the agent still needs the rule to apply it.

The directory goes stale.
Provider networks change monthly. Set a calendar reminder to upload a fresh PDF each month. Because Chatref’s knowledge‑base sources are easily replaceable, you can swap the old file for the new one in seconds, and the agent will use the updated data immediately.

Members ask for help that goes beyond the finder, like claims status.
That requires a different integration. For now, configure a fallback message in the agent settings that routes such queries to your member‑services phone number or a dedicated form.

What causes in network provider finder problems for Health Insurance Providers?

The most common cause is outdated or incomplete provider directories that lead to members receiving inaccurate results. When the knowledge base relies on monthly PDF uploads that haven’t been refreshed, the agent cannot reflect recent network changes. Additionally, unclear or missing plan‑to‑network mapping rules cause the finder to return unfiltered lists, frustrating members who expect a personalized answer.

How do I improve in network provider finder for Health Insurance Providers?

Keep the knowledge base fresh by uploading the latest provider directory every month. Include a detailed document that maps plan IDs to specific network tiers and rules, so the agent can apply those constraints. Use custom actions to collect the member’s plan and location each time, ensuring the response is relevant to that member. Finally, regularly test with real member queries and add any missing language or edge cases as supplementary FAQ documents.