Engage members immediately at the moment they request cancellation, hold the save conversation, and process the cancellation cleanly when retention is not the right outcome.
The Cancellations agent for Antares - Ember handles cancellation requests. Immediately. In writing. On the surfaces members already use to leave.
A member submits a cancellation request through the website form, the member app, or by email. Ember engages within seconds.
By having a two-way conversation rather than a one-way submission, Ember can quickly understand the actual reason behind the request and offer a relevant alternative where one exists.
Sometimes there is nothing to save. Sometimes the member has not seen the right option. Ember makes both paths frictionless, either completing the cancellation cleanly or surfacing the most relevant alternative so the member can stay.
Most fitness operators lose around a third of their members every year. Many of those members leave through a cancellation form with no real save conversation.
The example below uses a conservative 10% save rate, an average monthly fee of $50, and assumes a saved member stays for an additional six months beyond the point they would have cancelled.
Six additional months is a floor, not a forecast. Average member tenure in the industry runs well above that, and the actual retained value of a saved member is materially higher than the table suggests. The numbers above are what the operator can defend without argument. The real economics are better. The numbers move further when the save rate is higher, when the operator's average fee is higher, when actual remaining tenure is modelled, or when acquisition cost replacement is factored in. They move further still when the reason data Ember captures is used to fix the systemic drivers of attrition upstream.
Ember runs on the same Antares platform as every other agent in the suite. Configure once, and the same operating logic carries across every agent.
The operator controls what Ember is allowed to offer, including freezes, tier changes, location switches, discounts, concessions, and escalation rules. Ember does not invent offers.
Because Ember shares the same knowledge base, brand voice, policies, and integrations as the rest of the Antares agents, there is no separate cancellation system to manage.
Ember records what each member said, in their own words, then classifies it into a structured reason. Operators see the real drivers of cancellation, not just the limited options from a dropdown form.
Every conversation shows what Ember offered, whether the member accepted it, and what happened next. This makes it clear which interventions are working and where new save options may be needed.
Ember helps operators see whether cancellation reasons are isolated incidents or part of a wider pattern. Those patterns do not stay trapped in cancellation. When Ember identifies why members are leaving, that data feeds back into Nova, helping it qualify leads more intelligently at acquisition. The agents learn from each other.
Ember turns cancellation conversations into lifecycle data. Each save, downgrade, pause, and cancellation can be viewed alongside lead source, tier, tenure, location, and revenue. That gives operators stronger evidence for LTV modelling, sharper retention decisions, and a clearer view of which members stay, leave, and why.
Continuous Improvement Every Ember conversation contributes to the conversational intelligence environment underneath Antares. Operators see which save offers worked, which cancellation reasons exposed knowledge base gaps, and where agent behaviour can be refined. The platform learns from every conversation, and Ember gets better the more it runs.
Most of what governs Ember is set at the Antares platform level. The knowledge base, the brand voice, the integrations, and the policies are shared with every other agent. Ember-specific configuration:
Every Ember conversation is recorded, reviewable, and auditable. Nothing the agent does is a black box.
---3.png){kind=logo}