Skip to main content
The composer is the single form behind every one-off message you write: new sends, drafts, and replies. You address one contact, a hand-picked group, or everyone matching a segment. Owners and managers use it to send updates to a segment of members, and front desk staff and instructors use it to message and reply to individual members.

When to use it

Use the composer when a message is a one-off: an announcement, a personal follow-up, or an answer to a member’s question. The Recipients count shows how many contacts a segment reaches before you send, and templates save you rewriting repeatable emails. For messages that should go out on a trigger or a schedule, use an automation instead. Typical uses:
  • Tell a group about something new - a tennis gym opens extra Saturday areas and emails every member tagged “Weekend player”, starting from a template and attaching the updated area grid.
  • Answer a member’s question - a boxing coach replies to a WhatsApp question about sparring gear, and the reply goes back over WhatsApp.
  • Welcome a new lead - a climbing gym opens the composer from a lead’s profile and sends just that person a welcome email.
  • Win back lapsed members - a yoga studio drafts a return offer to its lapsed contacts and saves it as a draft for a second look before sending.
See Worked examples for more detail on each.

Pick recipients

The composer lives inside the Inbox. Open it by clicking Compose in the Inbox header (route /messages/new), or by selecting a draft from the conversation list. To reply, open a conversation and click Reply: a reply box opens inside the thread, headed “Replying to” the contact. Some flows open the composer pre-filled. On a live event, the Message menu offers Announce to all members, which opens a draft invitation with the event details and a link to book, addressed to every member, and Message attendees, which addresses everyone booked on the event. Under Recipients, choose how to address the message:
  • Select manually - Pick individual contacts in Select Contacts. The message goes to exactly those people, up to 5,000 of them. Sending with nobody picked is refused with “Select at least one recipient”.
  • Use segments - Send to every contact matching the filters at send time. Combine Contact Type (members, drop-ins, leads, lapsed members, contacts, staff), Filter by tag, Membership Categories, Pipeline stage is one of, Source is one of, and Membership Plans. A count such as “Recipients: 120” shows how many contacts match. With no filters set it reads “Recipients: 1,450 (all contacts)”, and the message goes to everyone in your organization.
Before a segment send, or a send to more than one hand-picked contact, a confirmation asks “Send to 120 recipients?” (or “Send to everyone matching your filters?”). Sent messages can’t be recalled. When you switch channel, contacts who can’t be reached on the new channel are removed from a hand-picked list, and a message tells you how many. When you arrive from a contact’s profile, the URL carries contactId (one recipient), contactIds (a comma-separated list), or contactType (pre-select a type filter), and the composer pre-fills the audience from those. Instructor-only accounts compose to the members they teach: the segment option and template picker are hidden. Staff limited to the .own compose scope can message specific contacts they pick, but cannot send to a segment.

Channels

A new message starts as email. Switch to SMS once your gym has set up an SMS sender, or to WhatsApp once a WhatsApp number is connected; a channel that isn’t ready isn’t offered. The channel of a reply follows the conversation it belongs to: reply inside a WhatsApp thread and it goes out over WhatsApp. Each channel changes the editor and the payload.
  • Email uses a block editor: paragraphs, headings, lists, images, embeds, code, and quotes. A subject field is required, and the body is stored as block JSON, not HTML. Email supports templates and file attachments.
  • SMS uses a plain text area. No subject, no formatting, no attachments. A counter under the text shows how many SMS the message takes. It leaves from your gym’s own sender name or toll-free number, and members in a country without a ready sender are skipped. While your home country’s sender is still being approved, a banner says those members won’t get the text yet. Paid-plan only; see SMS.
  • WhatsApp is also plain text and requires a connected WhatsApp Business number plus a paid plan.
Switching to a plain-text channel (SMS or WhatsApp) clears any applied template, since templates are an email construct. The channel switch is hidden on replies, and when email is the only channel available.

The email editor and attachments

The email body is a block editor. Write directly, or apply a template and edit it in place. You can attach files to an email with Attach files. The limits: up to 5 files, 10 MB per file, and 25 MB total. Attachments are not stored on our side; they ride along with the send, get encoded into the email, and are dropped. Because of that, drafts cannot keep attachments - saving a draft warns you and drops the files, so re-attach them when you reopen the draft to send. SMS and WhatsApp ignore attachments entirely.

Templates

If you have access to custom templates (the messages.read.club permission, which admins and managers hold), a template picker sits beside the subject on email composes. It lists templates of type message (your “Marketing & Updates” templates). Selecting one populates the subject and body in place; edit either afterward without changing the original template. Templates carry {{variable}} placeholders. For message templates the available variables are organizationName, organizationEmail, organizationPhone, orgBaseUrl, orgLogoUrl, contactName, contactFirstName, contactLastName, contactEmail, subject, senderName, and messageDate. SMS and WhatsApp messages can use variables too, except subject and orgLogoUrl. Legacy HTML templates predating the block editor are accepted, rendered, and converted to blocks on the next save. These manual message templates are distinct from the system (transactional) templates that drive receipts and event emails. See Templates for the full variable reference and the picker.

Generate with AI

The reply box inside a thread shows a Generate with AI button above the editor. It drafts a reply from your gym’s details, the conversation and the member’s recent bookings and memberships, in your Brand Book’s tone of voice. The draft replaces the text in the reply box (and the subject, on email), so click it before you start typing. Edit the draft, then click Send Reply. It isn’t offered on new messages.

Send, save draft, or reply

The action row at the bottom of the form changes with the mode:
  • Send Message posts the message immediately (POST /v1/messages). Success shows a toast and navigates to the new conversation; errors show as a toast. A successful send invalidates the Inbox list and the billing quota.
  • Save Draft posts the same payload with isDraft: true. Drafts show in the Inbox with a draft chip and reopen into the composer. (Drafts drop any attachments, as noted above.)
  • On a reopened draft, Update & Send sends it, Update Draft saves your changes, and Delete removes it after a confirmation.
  • Send Reply, in the reply box inside a thread, sends with replyToMessageId set so the message threads under the original, with the subject pre-filled as Re: <original subject>. A reply goes to the contact who wrote the original message, or to its first recipient if your gym sent it. Save Draft isn’t offered on replies.
There is no scheduler in the composer. To schedule a future send, use an automation with a delay, or save a draft and send it manually when ready.

Validation

The form blocks a send until:
  • The subject is non-empty (email only).
  • The body has at least one block (email) or non-whitespace text (SMS and WhatsApp).
  • A reply resolves to at least one recipient.
Both Send Message and Save Draft are disabled while a request is in flight.

Worked examples

Racket sports - waitlist opened. A tennis club opens extra Saturday areas. Compose an email, switch to Use segments, pick the Members type and the “Weekend player” tag, apply the “Area availability” template, adjust the times, attach the updated grid, and send. The Recipients count and the confirmation dialog show the audience size before you commit. Martial arts - single-student reply. A boxing coach gets an inbound WhatsApp question about sparring gear. Open the thread, click Reply, write the answer, and click Send Reply - the reply goes out over WhatsApp automatically. Climbing - lead onboarding. A climbing gym arrives at the composer from a lead contact’s profile (contactId pre-filled), writes a welcome email with a trial-pass button block, and sends to just that person. Pilates/Yoga - filtered win-back with a draft. A yoga studio switches to Use segments, picks the lapsed contact type, drafts a return offer, and saves it as a draft to get a second set of eyes before sending. Because it targets a segment, this needs organization-level compose access.

Tips & best practices

  • Watch the Recipients count before sending a filtered blast; it is your last check that the audience is who you expect.
  • Keep attachments under the total 25 MB cap and remember drafts drop them - attach right before you send, not when you draft.
  • Apply a template for repeatable sends, then personalize the opening line so it does not read as a template.

Troubleshooting

  • Inbox overview - Channels, the message model, and permissions.
  • Conversation list - Where drafts, sent messages, and replies live afterward.
  • Templates - Templates the picker reads from, plus the variable reference.
  • Contacts - Tag and segment the contacts you message.
  • Automations - Trigger-based and scheduled sends, instead of one-off compose.