Member communication

Keep club messages close to the member they concern.

Use inbox conversations, group messages and configured delivery channels with the context of participants, families, classes and events.

See how it works
Messages and notifications connected with club activity.
Messages and notifications connected with club activity.

The operational challenge

Messages lose value when staff lose the context.

A parent asks about a child’s camp while a coach announces a class change. If those conversations live in unrelated personal inboxes, the next colleague cannot see what was agreed.

Klunivo puts communication alongside operational records. Staff can address the appropriate person or group and keep follow-up connected to the work that prompted the message.

How Klunivo works

From setup to everyday use.

Shared records let colleagues continue the process without copying the same information.

  1. 01

    Choose the context

    Start with a participant, group, class or event.

  2. 02

    Check the recipient

    Distinguish the person attending from the guardian who should receive information.

  3. 03

    Use an enabled channel

    Send through the inbox or external channels configured for the club.

  4. 04

    Review the conversation

    Keep the history available to authorised staff who continue the enquiry.

A day in the club

Cancel one class and contact the people affected.

A club-wide announcement is rarely the best response to a single timetable change. Start with the session and identify its participants or guardians.

  1. 01

    Confirm the change

    Update the operational record so the message matches the timetable.

  2. 02

    Select the audience

    Use the relevant group or participant context.

  3. 03

    Choose the channel

    Use the channels available in the club’s configuration.

  4. 04

    Keep the history

    Let colleagues see what has already been communicated.

Outcome: The message becomes part of handling the change, with less dependence on private staff conversations.

Operational details

Make the record useful when plans change.

The important details are the ones your team needs to make the next decision.

Families

Distinguish the child attending from the guardian who should receive an administrative message.

Push notifications

Delivery depends on permissions and the user’s device configuration; it is not a guarantee that a message has been read.

SMS

Availability and costs depend on the SMS integration. Do not assume SMS is included without checking the agreement.

Feature details

Member communication: how it works

Explore the module’s scope, operating rules and practical examples for your club.

01

Use a shared inbox and the right audience

Reception and administration can work with conversations in the context of their roles. Contact history does not need to move with a staff member’s private messaging account. Group and process-based audiences help the team identify who needs a particular update.

The audience may be a class group, one participant, a guardian, an event’s members or someone arranging a trial. For a cancellation, begin with the affected session and its people rather than contacting the whole club.

02

Review each communication channel

Email requires appropriate configuration. SMS needs a configured provider and can incur external charges. Messages can also appear in the user’s application context. Available event communication can include chat and group updates.

For children’s activities, the person attending and the administrative recipient may differ. Keep the guardian relationship and the relevant child context clear when selecting recipients. Device permissions and channel settings also affect the practical notification experience.

03

Connect channels with a defined process

Communication establishes how to reach an audience. Automation defines when a configured event should trigger a response. These areas work together, but selecting a channel does not by itself establish a retention workflow.

Use the automation and retention page to review triggers, conditions and limits. Keep routine updates clear enough that a member can understand the affected class, date and next step without searching earlier conversations.

What the feature supports

What member communication includes

Club inbox

Keep staff conversations within the member-service workflow.

Group messages

Address information to the relevant class or participant group.

Family context

Connect communication with the appropriate guardian relationship.

Email and SMS

Use external channels when enabled and configured with their providers.

Benefits by role

Shared information. Clear responsibilities.

Each person takes part in the workflow with access suited to their responsibilities.

01

Reception

Continue a member conversation with its operational history.

02

Instructor

Communicate relevant class information within assigned responsibilities.

03

Parent

Receive information in the context of the correct child and activity.

Related features

Connect this workflow with the rest of your club.

Explore the features that share these records and support the next step.

Members and familiesLeads and trial classesCamps and events
Especially useful forSee how this workflow fits different types of organisation.

FAQ

Member communication: common questions

Can the club send group messages?

Yes. Group communication is part of Klunivo’s documented member workflows.

Is SMS included automatically?

SMS requires an enabled channel and provider configuration. Confirm availability and costs for the club’s market.

Are automations part of messaging?

Automation can trigger supported communication actions, but it has its own rules and configuration. Review the separate automation feature for its scope.

See member communication in your club’s workflow.

Bring your workflow. We will show its setup and daily use.

See this feature in a demo