Service & support
Know who is responsible for the next step.
A useful support relationship starts with clear responsibilities. Your organization should understand how to get help, what is covered and which commitments apply to the service you choose.
Updated October 29, 2026
Support routes and coverage agreed for your organization
Implementation responsibilities made clear
Contractual service levels belong in your agreement
Bring a problem to the people who can help.
Use the support route established for your organization when an existing platform workflow needs attention. For evaluation and service questions, contact the Clubward team and explain the task or concern you want to discuss.
A useful report includes the affected workspace, the action attempted, the time and the impact on your team. Keep passwords and sensitive member information out of website inquiries.
Contact the Clubward teamAgree the handoff before launch.
Implementation should identify who prepares the data, validates imported records, configures access and approves the organization’s operating workflows. Training should reflect the tasks each role actually needs to complete.
Choose representative examples for review before launch: a renewal, a payment question, a check-in exception and a staff handoff. Record who owns an unresolved question so it has a clear route to completion.
Onboarding and setupMake coverage and response expectations explicit.
Support channels, coverage hours, escalation arrangements and any response targets should be confirmed in the service agreement offered to your organization. A first response, an investigation update and a complete resolution are different milestones.
Maintenance notice, availability calculations, exclusions and any service credits also need a defined scope. This overview explains the subjects to agree; the applicable written agreement sets any contractual service levels and remedies.
Keep responsibilities current.
Clubward is responsible for the service it provides and the support arrangements it agrees. Your organization remains responsible for its policies, authorized staff, account security and the accuracy of information it enters.
Review those responsibilities when your team changes, an integration is introduced or your operational needs expand. A clear conversation at that point helps prevent an important task from falling between teams.
A person behind the answer
Let’s talk through what matters to you.
Bring a security question, a data request or a workflow your board needs to understand. We’ll help you find the relevant information and the next step.