Customer Support

How to triage customer support tickets as Fitness Studio Founders

Customer SupportFor Fitness Studio Founders2 apps11 steps~22 min to set up

When a member sends an angry email about being charged for a class they cancelled, you're the one who sees it — at 10pm, after teaching two sessions. Your inbox mixes Mindbody billing complaints, ClassPass 'how do I book?' questions, Instagram DMs about drop-in rates, and Gmail threads from members who emailed your personal address. Nothing is triaged. Nothing is tracked. You reply to whoever yelled loudest, forget the quiet churn risks, and spend 45 minutes Sunday night catching up on messages you missed during Friday's packed schedule. There's no system — just you, a phone, and guilt about the three members you haven't replied to in a week.

Build this on Starch → See the apps used

Customer SupportFor Fitness Studio Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

A support triage system that pulls member messages from Gmail and classifies them by urgency (billing dispute, cancellation risk, general inquiry) before you open your inbox each morning

An AI-drafted reply queue so you approve responses to common questions — class schedules, membership holds, make-up policies — in under two minutes instead of typing them fresh each time

A member flag that surfaces anyone who's complained twice in 30 days or hasn't received a reply in 48 hours, so churn risk from bad support doesn't hide in your inbox

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

CRM Customer Support Agent

Data sources & config

Starch connects directly to Gmail via scheduled sync — your inbox data refreshes automatically and is stored in Starch so the triage app can classify threads without you doing anything. Starch's CRM connects to Gmail from the same sync to log member interaction history. For member data from Mindbody, MarianaTek, or Wodify — none of which offer open APIs for independent studios — Starch automates through your browser to pull attendance records, billing status, and membership tier on a schedule, so support context (is this person on a 5-class pack or unlimited? did they cancel twice before?) is attached to every ticket. Note: Customer Support Agent is currently in development — request beta access now; the Gmail triage workflow and CRM flagging are available today.

Prompts to copy

Connect my Gmail and pull all member support emails from the last 30 days. Classify each one as: billing dispute, class cancellation, general inquiry, or churn risk. Show me anything unanswered for more than 48 hours at the top.

For any email tagged 'general inquiry' about class schedules, membership holds, or our cancellation policy, draft a reply using the following policy text: [paste your policy]. Show me the draft before sending.

Flag any member who has sent more than two support emails in the past 30 days and hasn't gotten a reply within 24 hours. Add them to my CRM as a churn risk and note the reason.

Every morning at 8am, summarize my unread support inbox: how many new messages, what categories, which ones need my personal response today. Slack me the summary.

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

Walkthrough

Step-by-step

1 Connect your Gmail to Starch — Starch syncs your inbox on a schedule, pulling messages and labels so the agent has your full support thread history without you doing a manual export.

2 Tell Starch how you want tickets classified: billing disputes, membership holds, class cancellation requests, general schedule questions, and anything that sounds like a member about to quit. Starch builds the classifier from your description, not a template you have to adapt.

3 Wire in your studio management platform. If you're on Mindbody, MarianaTek, or Wodify, Starch automates through your browser — no API required — to pull the member record that matches each email sender: their membership type, last visit date, and billing status.

4 Build a triage dashboard: unread count by category, oldest unanswered thread, and a 'needs you personally' list for anything a canned reply won't handle. You tell Starch what that dashboard should look like; it builds it.

5 Write your reply templates once — your cancellation policy, your make-up class policy, your hold policy — and paste them into Starch. The agent drafts replies for matching tickets and puts them in a review queue. You approve or edit; Starch sends.

6 Set a rule: any support email unanswered for more than 48 hours gets escalated to a daily digest Slack message so it doesn't disappear into your inbox.

7 Add a churn-risk flag: any member who's submitted two or more complaints in 30 days, or who cancelled a class and then emailed about a refund, gets added to your Starch CRM with a 'support risk' tag and the thread history attached.

8 Build a morning briefing automation — every day at 7:30am, Starch pulls your overnight inbox, classifies anything new, and sends you a Slack summary: 'Three new messages. One billing dispute needs your reply. Two general questions — drafts are ready to review.'

9 Review your draft replies each morning during the first break between classes. Approve the ones that are right, edit the ones that aren't, and close out the easy ones in under five minutes.

10 Once a week, run a churn-risk report: who has an unresolved complaint older than seven days? Who replied to your check-in and who didn't? Starch surfaces this from your CRM and Gmail sync so you have a real list, not a vague worry.

11 When Customer Support Agent launches (currently in development — request beta access now), it will handle the most repetitive tickets — 'what's the dress code for hot yoga?' — automatically, 24/7, so they never reach your inbox at all.

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

Week of March 10, 2026 — Monday morning triage at a 200-member Pilates studio

Sample numbers from a real run

Billing dispute — member charged after freeze request	1
General inquiry — make-up class policy (draft ready)	4
Cancellation request — wants to pause for April	2
Churn risk — third email in 30 days, no reply yet	1
Instagram DM — drop-in rate question (browser automation picked it up)	1

On Monday at 7:30am, the Starch briefing hits Slack: nine new messages since Friday. One billing dispute — a member froze her account in February but was charged in March. Starch pulled her Mindbody record through browser automation, confirmed the freeze was logged, and drafted a reply acknowledging the error and issuing a credit. Studio owner approves it in 30 seconds. Four emails asking about make-up class policy get a single drafted response from the policy text the owner pasted in week one — sent in bulk in under two minutes. Two members want April pauses; Starch drafts the hold confirmation and flags the owner to actually action the hold inside Mindbody (since that still requires a human). The one that matters most: a member who's emailed three times in 30 days — twice about class scheduling, once about a billing question — has been sitting unanswered for 52 hours. Starch flagged her in the CRM as a churn risk on Saturday when she hit the 48-hour threshold. The owner writes her a personal note. She stays. Total time spent on Monday morning support: fourteen minutes instead of the usual forty-five.

Measurement

How you'll know it's working

Average first-reply time to member support emails (target: under 24 hours)

Percentage of support tickets resolved without the owner typing a custom reply

Number of members flagged as support-driven churn risks per month

Churn rate among members who received a same-day reply vs. those who waited 48+ hours

Weekly unanswered thread count at end of each Sunday

Comparison

What this replaces

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

Mindbody's built-in messaging

Only covers messages sent inside the Mindbody app — misses Gmail, Instagram DMs, and direct emails entirely, so your support still lives in four places.

Zendesk or Freshdesk

Proper helpdesk platforms built for support teams, not solo studio owners — setup takes weeks, costs $50–100/month per seat, and still requires someone to write all the macros and routing rules.

Gmail labels + manual sorting

Free and already in use, but the triage is entirely manual, nothing drafts replies for you, and churn risks stay invisible until someone posts a Google review.

Zapier + Gmail + Google Sheets

Can route emails to a sheet automatically but can't classify intent, draft replies, or attach member context from Mindbody — you get a log, not a triage system.

On Starch RECOMMENDED

One platform — crm, 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

Does Starch work if I'm on Mindbody or MarianaTek? They don't have open APIs for small studios.

Yes — this is specifically why Starch uses browser automation for those platforms. Starch logs into your Mindbody or MarianaTek account through your browser, pulls the data it needs (attendance history, membership tier, billing status), and attaches it to the relevant member record. No API needed. It works the same way you'd look it up manually, just automatically.

What about Instagram DMs and Facebook messages? I get a lot of questions there.

Instagram and Facebook's DM APIs are heavily restricted. Starch can automate through your browser to check and surface DMs, but it's not a polished sync the way Gmail is. The more reliable path today: funnel your social inquiries toward email (add your Gmail to your Instagram bio, use a link-in-bio form) so they land in your Starch-connected inbox where triage is clean. Browser automation for Instagram DMs is possible for simple monitoring workflows.

Is this the same as the Customer Support Agent I saw mentioned?

Not exactly. The Customer Support Agent — which would handle tickets automatically 24/7 without your review — is currently in development. What's available today is the Gmail triage and CRM flagging workflow described here: Starch classifies your inbox, drafts replies, and surfaces risks, but you stay in the approval loop. Request beta access for Customer Support Agent if you want to be notified when it launches.

Can Starch actually send replies from my Gmail, or just draft them?

Both — Starch's Gmail connection includes read and send access. You can set it to put drafts in your review queue (recommended when you're starting out) or to send approved categories automatically. Most studio owners start with a review queue for everything, then flip a few categories — like 'make-up class policy replies' — to auto-send once they've seen the drafts are consistently right.

Is Starch SOC 2 certified? My members' data is in here.

Starch is not SOC 2 Type II certified today. If your studio is handling sensitive health or payment data and SOC 2 is a hard requirement, that's worth knowing upfront. For most independent studios, the practical risk profile is similar to using Gmail itself — your member data sits in Starch's database attached to your account. We'd rather you know this than find out later.

How long does setup take? I don't have an IT person.

Connecting Gmail takes a few minutes. Describing your triage categories and pasting in your policy text takes another 20–30 minutes the first time. The browser automation setup for Mindbody or MarianaTek requires you to walk Starch through your login once. Most studio owners have a working triage workflow in an afternoon — no technical background required.