Start an overdue-payment review by identifying the member, the service and the actual payment state. Confirm that the record is current before sending a reminder. Then give staff a clear next action and a practical way for the member to resolve the issue.
An unpaid service does not explain why payment is missing. A transfer may need checking, a recurring payment may have failed or the member may not understand how to pay. Treating all three situations as the same debt message creates unnecessary friction.
Separate the service from the payment event
A membership describes access, validity and any visit allowance. A payment describes a financial event. Reception needs to understand both when someone asks why they cannot book or which service a charge relates to.
For a family, identify the child concerned before discussing the record with the appropriate guardian. Combining siblings into one informal balance can make it difficult to explain which membership needs attention.
Check the status before contacting the member
Review the service, due date and payment history. Where a payment provider is involved, distinguish a pending transaction from a confirmed failure or successful payment. The exact states and available actions depend on the integration and configuration.
Record the outcome of any manual review. If one colleague has already checked a transfer or agreed a next step, the following shift should not send a contradictory reminder because that information stayed in a private conversation.
Write a reminder that helps someone complete the task
Explain which membership or service the message concerns and what the person can do next. Provide the appropriate route to review the account or contact the team. Avoid vague wording that leaves a willing member searching old messages for payment instructions.
Use the club’s agreed communication process and contact permissions. The purpose of an operational reminder is to resolve a specific issue. Do not turn it into an unrelated marketing sequence or assume that repeated messages will fix an unclear payment journey.
Handle recurring-payment exceptions explicitly
A recurring subscription can reduce repeated payment administration, but it still needs a process for failures and changes. Ask how staff see the subscription state, what the member sees and which actions are available through the payment integration.
Agree who reviews unresolved cases and how often. If the club makes an individual arrangement, record it in the relevant operational context. Access decisions should follow the configured service rules and the club’s policy, with exceptions handled consistently.
Review the process as well as the outstanding amount
Look for recurring causes: unclear instructions, duplicate profiles, missing family context or unresolved provider states. Improving these points can reduce unnecessary conversations even before changing the reminder schedule.
In Klunivo, memberships and payments sit alongside participant records and front-desk work. Use the shared history so staff can explain the situation accurately and continue from the previous contact.
FAQ
Questions worth answering
Should we remind every person with an unpaid record immediately?
Check that the service and payment state are current first. A pending payment or previously agreed arrangement may need a different response.
Is a failed recurring payment the same as cancellation?
No. Review the subscription state and available next steps through the configured payment integration.
What should reception see for a family payment question?
The appropriate guardian, the child concerned, the service and its payment history, within the staff member’s access scope.
