Automation and retention

Respond to member activity with rules your team understands.

Build supported trigger, condition and action sequences around the member journey. Use attendance and renewal signals to support considered follow-up.

See how it works
Configured automation supports the member journey and retention review.
Configured automation supports the member journey and retention review.

The operational challenge

A reminder is useful only when the timing and context fit.

A generic message can reach a member who has already renewed or is taking an agreed break. Meanwhile, someone who stopped attending may receive no personal attention at all.

Klunivo lets the club configure actions from a defined automation catalogue. Retention analysis helps identify the people and situations worth reviewing before selecting the appropriate response.

How Klunivo works

From setup to everyday use.

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

  1. 01

    Choose a supported trigger

    Start from an event or condition available in the automation catalogue.

  2. 02

    Define the audience

    Apply supported conditions to narrow when the rule should run.

  3. 03

    Configure the sequence

    Build up to ten steps using the available actions.

  4. 04

    Review the outcome

    Check what happened and whether a human follow-up is appropriate.

Feature details

Automation and retention: how it works

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

01

Build a sequence from the supported catalogue

An administrator can start with an empty automation and select from the available triggers, conditions and actions. Current triggers include registration without purchase, an incomplete profile, an expiring or expired membership, no training for a chosen number of days, a first purchase and a first attendance.

Conditions can include membership plan, adult or child status and marketing consent. Actions include email, SMS, in-app messages and a staff follow-up notification. A sequence can contain up to ten steps, with delays and quiet hours.

02

Use member context to choose the response

A member who has stopped attending may need help finding a different class. A membership approaching expiry may need a clear reminder. Configure the audience and timing around the actual situation and the available contact permissions.

Connect the review with D30, D60 and D90 cohort retention, renewal categories and the participant drilldown available in selected reports. The purpose is to understand the relationship between actions and member behaviour, without treating a message sequence as a guaranteed retention result.

03

Know the current limits

The module uses a defined catalogue; it is not an unrestricted no-code workflow engine. Users cannot currently create arbitrary custom triggers, generate a unique coupon for every person or change any lead status through an automation.

A staff follow-up action in this module creates an in-app notification for the appropriate roles. It is not a full reception task with a due date and status. Those full tasks exist in other workflows, including leads and trials. SMS also requires a configured operator and may have external costs.

What the feature supports

What automation and retention includes

Trigger and condition catalogue

Build rules from supported operational events and conditions.

Multi-step sequences

Connect up to ten configured steps in an automation.

Communication actions

Use supported channels with their provider and consent requirements.

Retention context

Connect cohort and renewal analysis with member-level review.

Benefits by role

Shared information. Clear responsibilities.

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

01

Owner

Agree which situations merit an automated response.

02

Administrator

Configure and verify the rule’s supported steps.

03

Member-services team

Use the result as context for a helpful conversation rather than a reason to send repeated messages.

Related features

Connect this workflow with the rest of your club.

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

Especially useful forSee how this workflow fits different types of organisation.

FAQ

Automation and retention: common questions

Can we build any automation imaginable?

Rules use the available trigger, condition and action catalogue, with up to ten steps. Arbitrary custom behaviour is not implied.

Can a rule send an SMS?

Only when the supported action and SMS channel are enabled and configured for the club.

Does an automation follow-up create a reception task?

Do not treat an automation follow-up as equivalent to a reception task. The documented workflows are distinct.

See automation and retention in your club’s workflow.

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