Customer Support

How to respond to online reviews as Educators, Coaches, and Course Creators

Customer SupportFor Educators, Coaches, and Course Creators2 apps11 steps~22 min to set up

When a student leaves a 3-star review on Google or Trustpilot because they couldn't figure out how to access the replay, that review sits there for three days while you're mid-cohort and haven't checked that inbox. You have no system for monitoring where reviews land — Google Business, Trustpilot, Course Report, maybe a Facebook group — so you find out about problems six weeks late, when enrollment for the next cohort is already open. Drafting a reply that sounds human, not defensive, while also being accurate about your refund policy takes 20 minutes you don't have on a Tuesday between coaching calls. Nothing in your Kajabi or Teachable stack touches this.

Build this on Starch → See the apps used

Customer SupportFor Educators, Coaches, and Course Creators2 apps11 steps~22 min to set up

Outcome

What you'll set up

A browser-automated review monitor that checks Google Business, Trustpilot, and Course Report on a schedule and surfaces new reviews in one place — no manual checking required

An AI-drafted reply queue where Starch proposes a response for each review, grounded in your actual course policies and FAQ content from Notion, that you can approve or edit in under two minutes

A weekly digest sent to your Gmail that summarizes new reviews by rating, flags anything below 4 stars for immediate attention, and tracks whether you've responded — so nothing sits unanswered through a launch week

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

Customer Support Agent

Data sources & config

Starch automates Google Business, Trustpilot, and Course Report through your browser — no API needed for any of them. Notion is connected as a scheduled-sync provider so Starch always has your latest FAQ and policy pages as context when drafting replies. Gmail is connected as a scheduled-sync provider for the weekly digest and for catching complaint-adjacent direct emails. The Email Triage app (live in the App Store) handles the inbox filtering layer; the Customer Support Agent — coming soon — will eventually handle drafting and posting replies end-to-end once it launches.

Prompts to copy

Check Google Business, Trustpilot, and Course Report for new reviews every morning. For each new review, pull the reviewer's name, star rating, and review text. Save them to a table. Flag any review with 3 stars or fewer as high priority.

For each unresponded review in the table, draft a reply using the FAQ document in my Notion workspace as the source of truth for policy questions. Match the tone to the review — if the reviewer is frustrated, acknowledge the frustration first before explaining anything. Keep replies under 120 words. Show me the draft before posting anything.

Every Monday at 8am, send me a Gmail summary of all reviews received in the last 7 days: total count, average rating, any unresponded reviews older than 48 hours, and a link to each pending draft reply.

Set up the Email Triage app to catch any direct student emails that mention a bad experience or use words like 'refund', 'disappointed', 'didn't work', or 'cancel' — surface those immediately, not in the daily digest.

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

Walkthrough

Step-by-step

1 Connect Gmail as a scheduled-sync provider so Starch can send you the weekly review digest and monitor your inbox for student complaint signals.

2 Connect Notion as a scheduled-sync provider and point Starch at the database or page where you keep your course FAQ, refund policy, and access troubleshooting guide — this becomes the grounding document for every reply draft.

3 Tell Starch which review platforms matter for your business: typically Google Business Profile, Trustpilot, and Course Report. Starch automates each one through your browser — log in once and it handles the rest.

4 Starch checks each platform on your chosen schedule (daily recommended) and adds new reviews to an internal table: platform, reviewer name, star rating, review text, date, responded status.

5 For every new unresponded review, Starch drafts a reply using your Notion FAQ as context. Reviews mentioning access problems get a reply that walks through the login fix; reviews mentioning value or results get a thank-you that's specific to what they described.

6 Drafts land in a review queue inside Starch. You read the draft, make any edits, and click approve — Starch posts the response to the platform through browser automation. You never log into Trustpilot manually again.

7 The Email Triage app monitors your Gmail for direct student messages containing complaint language ('refund', 'cancel', 'disappointed', 'didn't work') and surfaces them immediately rather than letting them sit in the morning batch.

8 Any flagged complaint email that matches a review you've already seen gets threaded together so you're not responding to the same issue twice with different answers.

9 Every Monday morning, Starch sends a digest to your Gmail: total reviews last 7 days, average rating, list of any review older than 48 hours without a response, and links to pending drafts.

10 Before each new cohort launch, run a one-off prompt: 'Pull all reviews from the last 90 days, group by the complaint topic mentioned, and tell me which issues came up more than twice.' Use that to update your FAQ before 200 new students ask the same question.

11 When the Customer Support Agent launches (coming soon), it will connect to this same review monitoring layer and handle posting responses autonomously for reviews that match known patterns — you set the rules once, it executes without a queue.

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

April 2026 cohort launch week — 11 new reviews in 5 days

Sample numbers from a real run

5-star reviews (Google Business)	7
4-star reviews (Trustpilot)	2
3-star review — login access complaint (Course Report)	1
2-star review — 'didn't get the bonus materials' (Google Business)	1
Response time without Starch (estimated)	72
Response time with Starch (actual, in hours)	6

You opened your April cohort on a Monday. By Wednesday you had 11 new reviews across three platforms. Without Starch, you'd have found out about the 2-star 'bonus materials' review on Friday when someone in your Slack community mentioned it — and by then it had been sitting unanswered for four days during peak enrollment traffic. With Starch running, the review landed in your queue by Tuesday morning with a draft reply already written: it acknowledged the confusion, explained that bonus materials are delivered via a separate email 24 hours after enrollment, and offered a direct link to re-trigger the delivery. You edited one sentence to match how you actually talk, clicked approve, and Starch posted it. The 3-star Course Report review about login access got a reply that pulled the exact troubleshooting steps from your Notion FAQ — steps you wrote once six months ago and never had to rewrite. Total time you spent on 11 reviews: about 18 minutes. The Monday digest told you your 7-day average rating was 4.6 and that nothing was sitting unresponded. You didn't have to log into any review platform once.

Measurement

How you'll know it's working

Average review response time (target: under 24 hours during launch weeks)

Percentage of reviews responded to within 48 hours

Average star rating by platform, tracked week over week

Number of complaint topics appearing in reviews more than twice per cohort (used to update FAQ before next launch)

Inbox complaint emails caught and surfaced same-day vs. falling into the daily batch

Comparison

What this replaces

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

Manual platform checking (Google Business + Trustpilot + Course Report tabs)

Free but takes 15-20 minutes daily and breaks the moment you're mid-cohort and stop checking.

Birdeye or Podium

Purpose-built review management tools with solid dashboards, but priced for multi-location service businesses — $300+/month — not a solo course creator, and they don't connect to your Notion FAQ or Kajabi stack.

Zapier + Google Alerts + a Google Sheet

Catches some Google reviews if the alert fires correctly, but misses Trustpilot and Course Report entirely, and produces zero draft replies — you still write every response from scratch.

Hiring a VA for review management

A good VA can monitor and draft replies, but they don't have context on your refund policy or course content unless you brief them constantly — and they're not available at 6am when a launch-week review drops.

On Starch RECOMMENDED

One platform — customer support agent, 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 actually post the reply to Google Business and Trustpilot, or do I have to do it manually?

Starch posts replies through browser automation — it logs into each platform the way you would and submits the response. You approve the draft first; Starch handles the posting. No API required for either platform.

What does Starch use to draft replies? I don't want it making up my refund policy.

You connect your Notion workspace as a scheduled-sync provider and point Starch at the specific pages that contain your FAQ, refund policy, and access troubleshooting steps. Starch grounds every draft in that content. If a review raises something not covered in your Notion docs, Starch flags it for you to write manually rather than guessing.

I use Teachable, not Kajabi. Does it matter?

For review monitoring, no. The review platforms (Google Business, Trustpilot, Course Report) are all reached through browser automation regardless of your course platform. If you want Starch to pull student enrollment data to cross-reference who left a review, Teachable is reachable from Starch's integration catalog of 3,000+ apps.

What about reviews inside my Circle or Facebook community? Can Starch monitor those too?

Facebook Groups are web-accessible, so Starch can automate monitoring through your browser — no API needed. Circle has API access and is reachable from Starch's integration catalog. Tell Starch what you want to monitor and it builds the workflow.

Is Starch SOC 2 certified? My course platform has student data I don't want exposed.

Starch is not currently SOC 2 Type II certified. For the review monitoring workflow, the only personal data flowing through Starch is the reviewer's name and review text — both already public on the review platform. Starch doesn't need to access your student roster or payment data for this specific workflow.

The Customer Support Agent sounds like exactly what I need — when does it launch?

The Customer Support Agent is currently in development. You can request beta access to get notified when it launches. In the meantime, the Email Triage app (available today) handles the inbox filtering and prioritization layer, and the browser-automated review monitor described here covers the external review platforms.

How is this different from setting up a Google Alert for my course name?

Google Alerts misses Trustpilot, Course Report, and any platform that doesn't surface in Google's index quickly. It also gives you a link, not a draft reply. Starch checks the platforms directly, stores the reviews in a structured table, drafts a reply grounded in your actual course policies, and tracks whether you've responded — Google Alerts does none of that.