Pack · Coaching
Group-program coach pack
A group-program coach sells a cohort programme with enrolment and shared sessions instead of one-to-one hours.
Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.
The workflows in this pack
Built for coaches.
01
Failed payment recovery for coaches
When a card payment fails, send the customer a plain, kind message with the link to pay, by email and text, and tell the owner.
- Starts whenA payment fails
- EmailTell the customer, kindly
- BranchDo we have a mobile?
- IfIf yes
- TextAnd by text
- IfIf no
- NotifyTell the owner
- Starts whenA payment fails
02
Payment thank-you for coaches
When an invoice is paid, thank the customer, mark them a paying customer in the CRM and tell the team.
- Starts whenAn invoice is paid
- EmailThank the customer
- App stepMark them a paying customer
- App stepTell the team
- Starts whenAn invoice is paid
03
Weekly enquiry numbers for coaches
Every Monday morning, send the owner how many enquiries came in through the client’s forms last week, and how many nobody has reached yet.
- Starts whenOn a schedule
- Find leadsEnquiries this week
- Find leadsNot reached yet
- NotifyTell the owner
What each client fills in
- Business name
- How messages sign off.
- Owner’s email
- Gets the summaries and the cases a person must handle.
- Team channel
- The Slack channel that hears about it.
The accounts it needs
Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.
In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.
In the client’s HubSpot: Settings → Integrations → Private Apps (Legacy apps) → Create → scopes crm.objects.contacts.write, and for the triggers crm.objects.contacts.read, crm.objects.deals.read and tickets → copy the access token. A private app needs no HubSpot review.
In the client’s Slack: api.slack.com/apps → Create New App → OAuth & Permissions → add the chat:write scope (and channels:history, plus groups:history for a private channel, for the message trigger) → Install to Workspace → copy the Bot User OAuth Token. Invite the app to the channel.
After you install it
It lands switched off. The client’s checklist holds exactly this:
- Connect the client’s Stripe, for “A payment fails”
- Connect the client’s Resend (email), for “Tell the customer, kindly” and “Tell the owner”
- Connect the client’s Twilio (SMS), for “And by text”
- Fill in Business name (How messages sign off)
- Fill in Owner’s email (Gets the summaries and the cases a person must handle)
- Connect the client’s Stripe, for “An invoice is paid”
- Connect the client’s Resend (email), for “Thank the customer”
- Connect the client’s HubSpot (optional: the step can be turned off instead), for “Mark them a paying customer”
- Connect the client’s Slack, for “Tell the team”
- Fill in Team channel (The Slack channel that hears about it)
- Connect the client’s Resend (email), for “Tell the owner”
Related templates
- PackCoachingExecutive coach packAn executive coach is usually paid by the client’s employer, which may expect reports, so there are three parties to the agreement.
Calendly
3 workflows · 8 steps · 6 apps
- PackCoachingSmall-business coach packA small-business coach is paid by the owner personally to work on the business itself.
Calendly
3 workflows · 8 steps · 7 apps
- PlaybookCoachingApplicant intake for coachesAcknowledge every job application at once, check it against the must-haves, log it, and send it to whoever hires.
Google Sheets4 steps · 3 apps
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.