Know the relationship
See plans, packages, add-ons, services, visits, notes, balances, and status from one member context.
Members & memberships
Connect the profile, membership, packages, add-ons, visits, services, balances, access, and follow-through behind every member in one operating view.
The member operating advantage
A useful member record carries more than contact information. It connects what the member bought, how they use it, what they owe, where engagement is changing, and what should happen next.
See plans, packages, add-ons, services, visits, notes, balances, and status from one member context.
Connect billing status, plan eligibility, service use, and access decisions instead of reconciling them later.
Turn missed visits, declining activity, failed payments, and unused services into coordinated follow-through.
Member 360
The profile stays consistent while the team moves between the relationship summary, what was sold, what is being delivered, how the member is engaging, and what is happening financially.
See a tailored member workflowSix of twelve prepaid sessions remain.
Two eligible bookings each week.
Bookable add-on tied to active membership.
Quarterly assessment included with plan.
Unlimited eligible classes under primary plan.
One-time onboarding service completed.
Membership architecture
A member can hold a primary plan, recurring add-ons, prepaid packages, and individual services at the same time—without forcing every revenue relationship into one generic membership type.
Recurring plans that define the primary relationship, billing cadence, access, and included benefits.
Ongoing upgrades such as small-group access, premium services, or additional recurring benefits.
Prepaid sessions or service entitlements with quantities, expiration rules, and assigned delivery context.
Rules that connect plan status, service use, booking eligibility, check-in, and physical access.
The member lifecycle
Each stage adds context the next team member should not have to reconstruct.
Create the member profile, agreement, primary plan, billing relationship, and initial access.
Coordinate orientation, assessments, first bookings, staff handoff, and early member communication.
Track visits, service use, bookings, purchases, notes, milestones, and the active relationship.
Surface changes in attendance, unused services, payment issues, cancellation signals, or missed starts.
Coordinate the right staff, communication, billing, scheduling, or service action and track the result.
Signals in context
Attendance, billing, service use, access, and follow-through can point in different directions. BuzOps keeps those signals close enough to guide a useful response.
Connected to the rest of the platform
Scheduling, money, communication, access, and reporting should add to the same relationship context instead of creating parallel versions of the member.
Member management questions
The right member structure depends on the business model, service catalog, billing rules, access requirements, and the way the team follows through.
Yes. The relationship can include a primary membership, recurring add-ons, prepaid service packages, and individually purchased services at the same time, with each retaining its own billing, eligibility, usage, and expiration context.
Check-ins, appointments, class bookings, package usage, completed services, and related staff activity can be associated with the same member record so the team can see how the relationship is being used.
Billing, plan status, access permissions, and service eligibility can be evaluated together. The exact rules should be configured around the business policy rather than assumed from one generic status.
The platform can bring attendance changes, unused services, failed payments, cancellations, missed first visits, and other operating signals into the same context. The response still depends on the workflow and staff action the business chooses.
Multi-location setups can preserve shared member context while still applying location-level schedules, services, staff, access, and operating rules where needed.
The transition plan depends on the current software, data quality, memberships, packages, balances, history, locations, and required integrations. Those details are mapped before a specific migration sequence is recommended.
See your membership model in BuzOps
A useful walkthrough should show how the real relationship fits—not only how to create a contact record.