Customer Support

How to build a customer knowledge base as Educators, Coaches, and Course Creators

Customer SupportFor Educators, Coaches, and Course Creators3 apps12 steps~24 min to set up

Your students email you the same five questions every single cohort. 'Where do I find the recording from Tuesday?' 'What's the refund policy?' 'I can't get into the Zoom.' The answers exist — they're in lesson 4, in the welcome email you sent, in the FAQ doc buried in Notion. But students don't find them, you answer the same thing for the sixteenth time, and your Sunday evening disappears into your inbox. You have no support team. You have Notion, a Gmail thread, and the knowledge that if you take a week off, questions pile up unanswered for days.

Build this on Starch → See the apps used

Customer SupportFor Educators, Coaches, and Course Creators3 apps12 steps~24 min to set up

Outcome

What you'll set up

A searchable knowledge base that pulls from your Notion curriculum, past email FAQs, and course materials — so students (or you) can find answers without digging

An AI-assisted email triage layer that spots repeat questions, drafts replies from your knowledge base, and flags anything genuinely new that needs your attention

A structured process for keeping the knowledge base current after each cohort — so the 'where is the recording?' question finally gets answered once, permanently

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 Customer Support Agent

Data sources & config

Starch connects directly to Notion (scheduled sync — pages and databases refresh automatically) and Gmail (scheduled sync — messages and threads). Your course platform like Kajabi or Teachable is reachable through Starch's integration catalog if it has an API, or Starch automates it through your browser — no API needed. Calendly is a scheduled-sync provider so booking data is available too. The Customer Support Agent app is coming soon; in the meantime, the Knowledge Management and Email Triage (Founder Inbox) apps handle the same core loop.

Prompts to copy

Build me a knowledge base from my Notion workspace. Pull in all pages tagged 'curriculum', 'FAQs', and 'student resources'. Let me search across all of it in plain English and surface the most relevant page or passage.

Connect my Gmail and watch for emails from students. When an incoming message matches a question already answered in the knowledge base, draft a reply pulling the exact answer and the relevant Notion link. Flag anything that doesn't have a match so I can write a new entry.

After each cohort ends, scan the last 60 days of student emails, find the five most frequently asked questions that aren't already in the knowledge base, and draft knowledge base entries for each one so I can review and publish them.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect your Notion workspace — Starch syncs your pages and databases on a schedule, so your curriculum docs, lesson guides, and any FAQ pages you've already written are immediately searchable.

2 Connect Gmail — Starch syncs your messages so it can read incoming student emails and your sent history, which is where most of your informal FAQs already live as one-off replies.

3 Tell Starch to build a knowledge base app: 'Pull everything from my Notion pages tagged student-facing and my sent Gmail replies to students. Organize by topic — tech setup, payments and refunds, curriculum questions, community access.' Starch builds the surface.

4 Search your own knowledge base first. Type 'Zoom link for live sessions' or 'what happens if a student misses a call' — if the answer is there, you're done building that entry. If it's not, write it once and publish it.

5 Set up the Email Triage app (Founder Inbox) and tell it: 'When a student emails a question that matches something in the knowledge base, draft a reply with the answer and the relevant Notion link. Label it KB-match so I can review and send with one click.'

6 Review the first week of drafted replies. Correct any that misread the question or pulled the wrong passage — this trains you on where the knowledge base has gaps.

7 After your next cohort launch, ask Starch: 'Look at student emails from the last 30 days. Which questions came up more than twice that aren't already in the knowledge base?' Use the output as your knowledge base backfill list.

8 Write the missing entries — typically 8 to 12 after a cohort — and publish them. Future cohort students, and future you, now have those answers without an email thread.

9 Set a recurring automation: 'Every time a cohort ends — I'll trigger this manually — scan the last 60 days of student emails and draft new knowledge base entries for any repeat question not already covered.'

10 Share the knowledge base link in your welcome sequence and your community. Add one line: 'Search here before emailing — it has answers to 90% of common questions.' Track whether your weekly student email volume drops.

11 When Customer Support Agent launches (coming soon), point it at this same knowledge base as its source of truth — it will handle first-line student questions over email and chat automatically, escalating to you only when the knowledge base doesn't have an answer.

12 Revisit the knowledge base before each new cohort. Ask Starch: 'What entries haven't been updated in 90 days and might be stale?' Update anything that's changed — new Zoom link, updated refund policy, different module order.

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

Spring 2026 Cohort — Knowledge Base Build in Week 1

Sample numbers from a real run

Notion pages imported (curriculum, FAQs, onboarding)	47
Sent Gmail replies mined for informal FAQs	312
Knowledge base entries auto-drafted by Starch for review	34
Entries published after founder review	28
Student emails in week 1 that got KB-match drafted reply	19
Emails requiring a new original reply from founder	4

You're launching your spring cohort — 180 students, 6-week program. Before Starch, week 1 meant 40+ student emails, half of which were 'where do I find X?' You spent four hours on Sunday just on inbox. This time, you spent 90 minutes in week 0: connected Notion (47 pages synced automatically) and Gmail (Starch mined 312 sent replies going back 18 months). Starch drafted 34 knowledge base entries from that raw material. You reviewed, cleaned up, and published 28. When cohort week 1 started, 19 of the 23 student emails that came in were KB-matched — Starch drafted a reply for each with the exact passage and the Notion link. You reviewed and sent them in about 20 minutes total. Only 4 emails were genuinely new questions. You answered those, then added two of them as new knowledge base entries on the spot. Week 1 inbox time: 35 minutes instead of four hours.

Measurement

How you'll know it's working

Student emails per week per active cohort (target: drops by 50%+ after knowledge base is live)

Percentage of incoming student emails matched to a knowledge base entry (tracks coverage quality)

Time to first reply on student questions (goal: under 2 hours for KB-matched, same day for new)

Number of net-new knowledge base entries added per cohort (tracks whether the base is actually growing)

Repeat questions per cohort — same question asked by more than one student (should trend toward zero for documented topics)

Comparison

What this replaces

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

Notion alone as a student FAQ doc

Students don't read it, can't search it well, and you have no way to know which questions are coming in repeatedly — so it stays static and underused.

Zendesk or Freshdesk

Proper helpdesk software built for support teams — setup takes weeks, costs $50-150/month, and is overkill if you don't have an agent to staff it; you'd still answer everything yourself, just in a different interface.

Kajabi's built-in support tools

Only works if Kajabi is your entire stack; doesn't connect to Notion, Gmail threads, or Calendly, so your knowledge stays siloed inside one platform.

A pinned Slack or Circle FAQ post

Easy to set up but hard to search, impossible to keep current, and doesn't help students who email instead of posting in community — which is most of them.

Hiring a VA to handle student emails

Works, but a VA still needs a knowledge base to pull answers from — without one, they're guessing or asking you anyway, and you've added a coordination layer without solving the root problem.

On Starch RECOMMENDED

One platform — knowledge management, founder inbox, customer support agent 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

I already have a Notion FAQ doc. Does Starch just search that, or does it actually build something new?

Both. Starch syncs your existing Notion pages on a schedule and makes them searchable in plain English — so yes, your existing doc works immediately. On top of that, it can mine your sent Gmail replies and draft new entries you haven't written yet, then let you review and publish them. Your Notion doc becomes the foundation; Starch fills in the gaps.

My course runs on Kajabi. Can Starch connect to it?

If Kajabi exposes an API, Starch can connect to it from the integration catalog and query it live. If that connection isn't available, Starch can automate Kajabi through your browser — no API needed. Either way, you're not blocked. The knowledge base itself lives in Notion and Gmail, which Starch syncs directly, so Kajabi access is additive rather than required.

Will the Customer Support Agent app actually answer students automatically, or do I still have to review everything?

The Customer Support Agent app is coming soon — it's currently in development and not available yet. Today, the Email Triage app (Founder Inbox) drafts replies for you to review and send with one click. That's still faster than writing from scratch, and you stay in the loop. When the Customer Support Agent launches, it will handle first-line replies automatically using your knowledge base, escalating to you only when it doesn't have an answer.

Is my student data safe? These are real people's names and emails.

Starch handles your data securely, but it's honest about its current state: Starch is not SOC 2 Type II certified today. There's no self-hosted option. If your program is subject to strict data compliance requirements (FERPA, HIPAA for wellness coaching, etc.), you'll want to evaluate that before connecting sensitive student records. For most coaching and course businesses, this isn't a blocker — but it's worth knowing.

I run cohorts every 6 weeks. How does the knowledge base stay current instead of becoming outdated?

Set up a manual-trigger automation in Starch: when a cohort ends, you trigger it, and Starch scans the last 60 days of student emails for repeat questions not already in the knowledge base, then drafts new entries for your review. You can also ask Starch to flag entries older than 90 days before each new cohort so you can update anything that's changed — new Zoom links, updated refund terms, new module structure. It takes about 30 minutes per cohort cycle once the base is established.

What if I don't use Notion? My course materials are in Google Docs or just in the Kajabi lesson editor.

Google Drive is available through Starch's integration catalog, so Google Docs content can be queried live when your apps run. For content that lives only inside Kajabi or another platform, Starch can automate the browser to pull text from those pages — no API needed. The knowledge base gets populated from whatever you have, not from what you wish you had organized.