Skip to content

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.

Workflows
3
Steps
10
Client fills in
3
Starts
From Stripe, within seconds, or at a set time

UsesBeta

The workflows in this pack

Built for coaches.

  1. 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.

    1. Starts whenA payment fails
    2. EmailTell the customer, kindly
    3. BranchDo we have a mobile?
    4. IfIf yes
    5. TextAnd by text
    6. IfIf no
    7. NotifyTell the owner
  2. 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.

    1. Starts whenAn invoice is paid
    2. EmailThank the customer
    3. App stepMark them a paying customer
    4. App stepTell the team
  3. 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.

    1. Starts whenOn a schedule
    2. Find leadsEnquiries this week
    3. Find leadsNot reached yet
    4. 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:

  1. Connect the client’s Stripe, for “A payment fails”
  2. Connect the client’s Resend (email), for “Tell the customer, kindly” and “Tell the owner”
  3. Connect the client’s Twilio (SMS), for “And by text”
  4. Fill in Business name (How messages sign off)
  5. Fill in Owner’s email (Gets the summaries and the cases a person must handle)
  6. Connect the client’s Stripe, for “An invoice is paid”
  7. Connect the client’s Resend (email), for “Thank the customer”
  8. Connect the client’s HubSpot (optional: the step can be turned off instead), for “Mark them a paying customer”
  9. Connect the client’s Slack, for “Tell the team”
  10. Fill in Team channel (The Slack channel that hears about it)
  11. Connect the client’s Resend (email), for “Tell the owner”

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.