Skip to main content
The inbox is one list of every conversation between your gym and your members, outbound and inbound, with drafts alongside. Each row is a conversation - a piece of human-authored, replyable correspondence between your gym and a member - not an individual delivery. Admins and managers work the organization-wide inbox, and instructors see the conversations they took part in.

When to use it

Open the inbox to see what members have written back, pick up a conversation where it left off, and finish messages you started. Each row rolls up a whole thread, new replies appear without a refresh, a dot marks conversations waiting for your reply, and a Draft chip marks anything not yet sent. Typical uses:
  • Catch a member’s reply - a boulderer answers your route-setting update, and its conversation shows the Waiting for a reply dot and a fresh timestamp without a refresh, ready to reply inline.
  • Finish a draft - a message to all jiu-jitsu members about a belt-grading date is still marked Draft, and clicking it reopens the compose pane.
  • Follow a group conversation - a message to four padel members about a doubles ladder shows as one row, with every reply threaded beneath.
See Worked examples for more on each.

How the list is built

The conversation list is the main view of Inbox in the left rail (route /messages). The left pane lists conversations; the right pane shows the selected thread or the compose form. On mobile the right pane slides up as a sheet over the list. Each row is a conversation head: a message you sent with its replies, a message a member sent in with your responses, or a draft not yet sent. Replies never get a row of their own. Rows are sorted newest first and load 25 at a time. Load more conversations at the bottom extends the page in 25-row steps. Use Search conversations above the list to find a conversation by subject, recipient name, or sender name. In the instructor inbox, search matches the subject only.

What a row shows

Each row is built around the counterparty of the conversation:
  • A single contact shows that contact’s avatar and full name.
  • A pair of contacts shows two stacked avatars and “Firstname, Firstname”.
  • A group of 3+ shows the first contact’s avatar with a +N badge and “Firstname + N others”.
  • An inbound message with no stored recipients falls back to the sender’s avatar and name - this is how a member-initiated conversation renders.
To the right of the name you may see:
  • A WhatsApp icon next to a single contact who can be reached on WhatsApp.
  • A Draft status chip when the message has not been sent yet.
  • The relative time of the latest message (when it was sent, or created if it is still a draft).
  • A Waiting for a reply dot when the latest message in the thread came from the contact rather than your gym. A reply from staff or an automation clears it. Drafts never show it.
Below the name is a snippet: the subject if there is one, otherwise up to the first 80 characters of the body with HTML stripped.

Channels and direction

A message carries a channel and a direction, both stored on the record.
  • Channel is email, SMS or WhatsApp.
  • Direction says where the message came from: outbound messages started in 1club, inbound ones arrived from outside, such as a member’s email to your gym’s address or a WhatsApp message to your number. A member writing from the portal or the app creates an outbound message addressed to your gym, because it started in 1club.
When a message is sent on behalf of a specific person - today, a class instructor via the “send from the instructor” option - the inbox shows that person’s name and avatar as the sender, matching the email the member received. 1club still records which staff member sent it.

Selecting a row

Clicking a row updates the URL to /messages/<id> and renders the right pane:
  • If the message is a draft, the compose pane opens so you can finish writing.
  • Otherwise, the thread view renders: the original message at the top, then replies in order, with date separators between days.
Click Reply at the bottom of the thread to open a reply box in place, headed “Replying to” the contact, with the subject pre-filled as Re: <subject>. Send Reply sends it into the same thread. The URL doesn’t change. On desktop, opening the inbox with nothing selected auto-opens the first conversation so the detail pane is not blank. On mobile the list stays put until you pick a row.

Real-time updates

The inbox updates live. When a message arrives (a member writing in by email, WhatsApp or a website contact form), the list and the open thread refresh on their own, so new replies appear without reloading the page. The list also checks for changes every 30 seconds, and Refresh inbox reloads it on demand. Members’ email replies to messages you send arrive in the conversation automatically: each emailed message carries a personal reply address alongside your gym’s own address. See Replies to your messages.

Status and engagement signals

A message is either a draft or sent, which decides whether selecting its row opens the composer or the thread. Delivery is tracked per recipient but not shown in the list: whether each email was delivered, bounced or marked as spam, and whether it was opened or clicked. To check one email, use Email activity, which shows each email’s delivery status and, when it wasn’t delivered, why.

Audience scope: admin vs instructor view

  • Admins and managers see the organization-wide inbox: every message attached to the org. Segments and the template picker are available when composing.
  • Instructors see only their own conversations: messages they sent, messages from the contacts they wrote to, and the threads those belong to. They can still use Compose, but their compose form hides segments and the template picker; replying to messages they can read still works.

Permissions

  • Reading the inbox requires messages.read.own (broader messages.read.club / messages.read.organization holders see more).
  • Composing or replying requires a messages.create permission.
  • Sending to a segment and using templates require messages.read.club and messages.create.club, which admins and managers hold.

Worked examples

Spotting a member reply (climbing gym)

A boulderer replied to your route-setting update. Because the inbox updates live, the conversation jumps to the top with a Waiting for a reply dot and a fresh timestamp - no refresh needed. Click it to open the thread and reply inline.

Finishing a draft blast (martial arts)

You started a message to all jiu-jitsu members about a belt-grading date but did not send it. It sits in the list with a Draft chip. Clicking the row opens the compose pane instead of a thread, so you can finish and send it.

Reading a group thread (racket sports)

You messaged four padel members about a doubles ladder. The row shows the first member’s avatar with a +3 badge and “Firstname + 3 others”. Opening it shows the single outbound message and any replies threaded beneath.

Tips & best practices

  • Work the dots. A Waiting for a reply dot means the member wrote last and nobody has answered yet.
  • Let the auto-select help on desktop. The first conversation opens on load, so you can triage without an extra click.
  • Use Reply, not a fresh compose, to keep threads intact. Replying preserves the conversation and pre-fills the Re: subject.
  • Search, or load more. The list starts at 25 rows; search by subject or name, or extend it before hunting for an older conversation.
  • Check WhatsApp before relying on it. The WhatsApp icon tells you a contact is reachable on that channel.

Troubleshooting

  • Compose - The send and reply flow the right pane drives.
  • Templates - Templates the compose pane reads from.
  • Inbox overview - How the inbox fits with automations, channels, and permissions.
  • Automations - Automated, trigger-based sends that also land in the inbox.