What untrusted balances look like
"How many classes do I have left?" should be the easiest question at a studio front desk. Too often it is the hardest. The check-in tablet says three, the member's app says five, and the owner's spreadsheet says four because a comp class from last month was added by hand. Meanwhile a member who asked to freeze her membership for a trip sent the request by direct message, a coach said "sure," and nobody paused her billing.
Booking a class is usually not the problem. Most studios already have a booking tool that handles schedules and spots. The trouble starts after the booking: what happens to the balance when someone checks in, cancels late, misses class, gets a comp, shares a pack, or asks to pause. This article is about that part. TwoQM develops custom software, CRM workflows, automation, and connected systems for fitness studios and gyms when the tools they already pay for do not answer those questions the same way twice.
Here is an original example, not a TwoQM client and not a measured result. A boutique cycling studio sells 10-class packs, monthly memberships, and a few family packs. A member disputes a no-show charge. The manager scrolls through check-ins, finds a late cancel that was waived verbally, a comp class added after a broken bike, and a freeze that started a week later than the member remembers. Forty minutes later the balance is probably right, but neither the member nor the manager is sure.
Treat the balance as a ledger, not a number
The fix is not a better number. It is a history. Every change to a member's balance should be an entry with a date, a reason, and the staff member responsible:
Pack purchased, with its expiration date
Class attended
Late cancel or no-show deduction, under your written policy
Waiver of a deduction, with a reason
Comp credit added, and who approved it
Transfer to or from a family or shared pack
Credits expired
The balance is simply the sum. Nobody edits it directly. When a member asks, staff can show the last ten entries in plain language instead of defending a number. That alone heads off many disputes.
Write the policy once, where the system can use it
Staff should not carry your policy in their heads. Write it down so the software applies it the same way every time:
Pack expiration. How long credits last, and whether a freeze extends that date.
Late-cancel and no-show rules. The window, the deduction, and who may waive it.
Shared and family packs. Who can draw from them and who can see the balance.
Comps. Which roles can grant them and whether a reason is required.
Freeze rules. Minimum and maximum length, how much notice, how often a member may freeze, and any fee you charge. Keep the reasons you collect to simple categories such as travel or injury; you do not need medical details to approve a pause.
Make freeze requests a workflow, not a favor
A freeze touches three things at once: the member's access, their billing date, and their credit expiration. If only one of those changes, someone gets charged for a month they did not use, or credits expire during a pause the studio approved.
Give freezes a short, visible path:
Request. The member submits dates and a reason category from a form or the member portal, not a DM.
Policy check. The system flags requests outside your rules, such as too short, too long, or too little notice.
Decision. A manager approves or declines with a note the member can see.
Effect. Approved freezes pause access, move the next billing date, and extend credit expiration by the same span, per your policy.
Resume. The member gets a reminder before the freeze ends, with the exact date billing restarts.
Statuses like requested, approved, active, ended, and declined let any staff member answer "what is going on with my account?" without calling the owner.
Connect billing so the freeze actually happens
Many studios bill memberships through a payment processor or studio platform. If a freeze is approved in one place and billing runs in another, the freeze has to reach both. That is connected systems work: one approved decision updating the member record, the billing schedule, and the expiration date together. Whether your platform allows a clean connection is confirmed during scoping. Sometimes the right answer is a clear task for staff to pause billing manually, logged on the same record.
Automation first, then AI drafts a person reviews
Ordinary business automation covers most of this: deduct a credit at check-in, warn a member when two classes remain, remind them before credits expire, alert a manager to a pending freeze, and send the resume reminder.
AI fits where language is messy and a person still decides. A member's long message about a trip, a sore knee, and a billing question can become a short summary and a draft reply that uses your policy wording. AI can also turn a member's ledger into a plain-language explanation for a dispute. A staff member reviews before anything is sent, and AI never changes balances, approves freezes, or waives fees.
Where to start this week
Pull five members with active packs and rebuild each balance from scratch. Note every place you had to look and every entry with no reason. Then write your freeze rules on one page and decide who approves exceptions.
If your studio wants balances and freezes on a member record staff can trust, TwoQM can scope it around your policies and the tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Tell Us About Your Membership Workflow · Explore TwoQM CRM workflows