Customer Support

How to build a customer knowledge base as Independent Clinic Owner-Operators

Customer SupportFor Independent Clinic Owner-Operators2 apps11 steps~22 min to set up

Your front desk handles the same twenty questions every week — what insurances do you take, how does your cancellation policy work, what should a new patient bring, how long is the initial eval. The answers exist somewhere: a PDF on your website, an email template in someone's drafts, a sticky note on the desk. When your front desk person is out, you're fielding those calls between patients. When a new hire joins, you spend four hours walking them through things that should be written down. Your EHR documents clinical encounters fine. It does nothing to capture the operational knowledge your clinic actually runs on — and every month that information lives in people's heads, you're one resignation away from losing it.

Build this on Starch → See the apps used
Customer SupportFor Independent Clinic Owner-Operators2 apps11 steps~22 min to set up
Outcome

What you'll set up

A searchable internal knowledge base covering your clinic's policies, intake procedures, insurance FAQs, and front-desk scripts — so new staff can find answers without interrupting you
An AI-assisted inbox system that drafts replies to common new-patient and referral emails and flags the ones that need a human decision, including insurance follow-ups aging past 45 days
A living doc system that surfaces stale content — so when your cancellation policy changes, the old version doesn't keep circulating
The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used
Knowledge Management
Data sources & config

Email Triage (founder-inbox) connects to Gmail via Starch's scheduled sync, so your inbox is read on a schedule and replies are drafted from knowledge base content. Knowledge Management (knowledge-management) is built on top of Notion — connect Notion from Starch's integration catalog and the agent queries your pages live when answering questions or checking for stale content. Your clinic's existing policy documents (Google Drive or Dropbox) can also be connected from Starch's integration catalog. If your EHR has a web-facing patient portal or intake form page, Starch can automate reading or populating it through your browser — no EHR API required.

Prompts to copy
Build me a knowledge base for my three-provider clinic. It should have sections for: new patient intake (what to bring, how to complete forms, what to expect on the first visit), insurance (which plans we're in-network with, how to check benefits, what to tell patients about out-of-network coverage), scheduling policies (cancellation, no-show fees, late arrivals), referral workflows (how to receive a referral, what we need from the referring provider, how we respond), and front desk scripts for the ten most common phone questions. I'll paste in my current documents and you should organize and fill gaps.
Set up an email triage system for my clinic inbox. Prioritize: (1) new patient inquiries that haven't received a response in more than 4 hours, (2) insurance or billing emails that reference a date of service older than 30 days, (3) referral emails from physicians. Draft a reply for each category using the clinic knowledge base as the source of truth. Flag anything that requires a clinical decision for me personally.
Every Friday, scan the knowledge base and flag any article that references a specific insurance policy, fee, or staff name that may have changed. Show me a list of articles that haven't been reviewed in 90+ days.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Gather every document your front desk currently uses: intake forms, insurance lists, fee schedules, cancellation policy, referral checklists, new-patient welcome emails. If they're in Google Docs or Notion, connect those from Starch's integration catalog. If they're PDFs on a shared drive, upload them directly.
2 Open the Knowledge Management app in Starch and type: 'Organize these documents into a clinic operations knowledge base with the following sections: Patient Intake, Insurance & Benefits, Scheduling Policies, Referrals, and Front Desk Scripts.' Starch structures the content and identifies gaps.
3 For each section, Starch will surface questions it can't answer from your documents — things like which specific CPT codes you bill, your exact no-show fee, or which insurances you recently dropped. You fill those in conversationally.
4 Connect Gmail via Starch's scheduled sync. Open the Email Triage (founder-inbox) app and tell Starch which email categories matter most: new patient inquiries, insurance correspondence, referral emails, and anything from your billing person.
5 Tell Starch: 'When you draft a reply to a new patient inquiry, pull the answer from the knowledge base. If the question isn't covered, flag it for me and add a placeholder to the knowledge base so we can fill it in.' This closes the loop between inbox and knowledge base over time.
6 Set up a weekly stale-content check: 'Every Friday at 8am, scan the knowledge base and list any article that hasn't been reviewed in 90 days or references a specific dollar amount, insurance name, or staff member name.' Starch runs this as a scheduled automation and Slacks you the list — connect Slack from Starch's integration catalog.
7 Build a front-desk onboarding path: 'Create a 3-day onboarding reading list for a new front desk hire, pulling from the knowledge base. Day 1: intake and scheduling. Day 2: insurance and billing basics. Day 3: referral workflow and phone scripts.' New hires get a structured start without you running the training.
8 For referral thank-you emails specifically, tell Starch: 'When I receive a referral email from a physician practice, draft a thank-you reply that includes the patient's appointment date (if scheduled), our fax number for records, and a brief summary of what we'll send back after the first visit.' Draft is queued for one-click send.
9 Handle the insurance aging problem: 'Flag any email thread in my inbox where we're discussing a claim and the most recent date-of-service mentioned is more than 45 days ago. Summarize what the outstanding issue is and draft a follow-up to the payer.' Run this on demand or on a Monday morning schedule.
10 Once the knowledge base has been live for 30 days, ask Starch: 'Which questions have been asked via email that weren't covered in the knowledge base? Show me the top five gaps.' Use this to fill in the articles that actually matter to your patients, not the ones you assumed mattered.
11 When Customer Support Agent becomes available (currently in development — request beta access), it will let the knowledge base answer common patient inquiries directly from your website contact form, 24/7, and escalate anything requiring a scheduling decision or clinical judgment to your inbox with full context.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →
Worked example

New Office Manager Onboarding — February 2026

Sample numbers from a real run
Knowledge base articles created at launch34
Email templates auto-drafted from knowledge base in first 2 weeks47
Insurance aging flags surfaced (claims >45 days)6
Hours of founder onboarding time replaced by self-serve reading list4
Stale-content flags after first 90-day review cycle8

In February, your office manager of three years gave two weeks notice. You had 10 days to get a replacement up to speed before she left. You opened the Knowledge Management app and told Starch: 'Build a 3-day onboarding reading list for a new front desk hire at a three-provider outpatient physical therapy clinic.' Starch pulled from the 34 articles already in the knowledge base — intake workflow, the insurance grid showing your 12 in-network payers, the cancellation and no-show fee policy ($75 after two no-shows), the referral checklist for physician practices — and organized them into a sequenced reading plan. The new hire spent her first day in the knowledge base, not in your office. Meanwhile, Starch's email triage surfaced 6 open insurance threads where the date of service was older than 45 days — including one Aetna claim from September that had been sitting because the denial letter had been misfiled. Starch drafted a follow-up to the payer with the claim number and date of service pulled from the email thread. You edited two sentences and sent it. By week three, the new office manager was answering new patient inquiries using draft replies Starch generated from the knowledge base, and you'd stopped being the person who knew where everything was.

Measurement

How you'll know it's working

Front desk response time to new patient inquiries (target: under 4 hours during business hours)
Insurance claim follow-up rate — claims flagged and actioned within 45 days of denial or no-response
No-show rate by provider and day of week (tracked manually or via EHR export; Starch surfaces trends)
Knowledge base coverage — percentage of common front desk questions answerable without escalating to the owner
Staff onboarding time to independent operation (days from hire to handling inbox without supervision)
Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Notion standalone wiki
Notion stores the docs, but doesn't draft email replies from them, doesn't flag stale content automatically, and doesn't connect to your inbox — you're maintaining two separate systems manually.
Jane App / SimplePractice internal messaging and templates
EHR-native templates cover clinical documentation and appointment reminders well, but they don't handle open-ended patient inquiries, referral correspondence, or insurance follow-up threads — the stuff that lands in your regular email inbox.
Google Docs + Gmail labels
Free and familiar, but search across docs is poor, there's no staleness detection, and nothing drafts replies — your front desk still has to find the right doc, read it, and write the email from scratch.
Zendesk or Freshdesk
Built for high-volume support teams with dedicated agents; pricing and configuration overhead are sized for a 20-person support org, not a three-provider clinic where the front desk is one person.
On Starch RECOMMENDED

One platform — knowledge management, founder inbox all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →
FAQ

Frequently asked questions

Does Starch connect directly to my EHR — Jane, SimplePractice, Kareo?
Not via a direct scheduled sync today. Most EHRs have web-facing portals or reporting pages, and Starch can automate reading those through your browser — no EHR API required. For patient scheduling data or provider availability, if your EHR exports to Google Calendar, Starch syncs Google Calendar directly on a schedule. The knowledge base and inbox workflows don't require EHR access to deliver value — they operate on your email and the documents you already have.
Is this HIPAA compliant? Can patient information live in the knowledge base?
Starch is not SOC 2 Type II certified today. We'd recommend keeping the knowledge base focused on operational policies, front desk scripts, and administrative workflows — not patient records or clinical notes, which belong in your EHR. New patient inquiry emails that include PHI should be handled with that in mind; draft replies can be reviewed before sending rather than auto-sent.
My front desk person is not technical. Can she actually use this?
The knowledge base is a search interface — she types a question and gets an answer, same as Google. The email triage produces draft replies she reviews and sends. There's no configuration burden on her side. Setup happens once, on your end, by describing what you want to Starch in plain language.
What about the Customer Support Agent you mentioned — the one that answers patient inquiries from the website automatically?
Customer Support Agent is currently in development. It's not available today. You can request beta access to be notified when it launches. In the meantime, the Email Triage app handles the inbox side of the same problem — drafting replies to inquiries that come in via email so your front desk can respond quickly without starting from scratch.
Will Starch automatically update the knowledge base when our policies change?
Not automatically — you still decide when a policy changes. What Starch does is flag articles that are likely stale (based on age or references to specific fees, staff names, or payer names) so you know which ones to review. The weekly staleness check means you're not relying on memory to keep things current.
We already have a Google Drive folder with policies. Do I have to start over?
No. Connect Google Drive from Starch's integration catalog and point Starch at the relevant folder. Tell it: 'Organize these existing documents into a structured knowledge base and flag any gaps.' It reads what you have, structures it, and asks you to fill in what's missing — you're not rewriting from scratch.

Ready to run build a customer knowledge base on Starch?

Request closed-beta access. Everything is free during beta.

You're on the list! We'll be in touch soon.