Core Features

Session Packages

Packages are how you track prepaid sessions for clients with the Package billing type. Create a package, and CountedIn counts down the credits as you log sessions. Per-session, monthly, and no-billing clients don't use packages.

Creating a package

From a client's profile, click Add Package in the Packages section.

counted-in.app

Packages show a visual progress bar of remaining credits

Name the package

Choose a clear name like "10-Session Pack", "Monthly Unlimited", or "Intro Special". This name is visible to the client if you share their balance link.

Set the total sessions

Enter the original number of credits in the package. For example, a "10-Session Pack" has 10 sessions. New packages start with all credits available; the remaining balance counts down as you log sessions.

Set the price (optional)

The package price is for your records and doesn't trigger a payment. Dashboard revenue comes from payments you record or receive through CountedIn.

Set an expiration date (optional)

If the package should expire after a certain date, set it here. You'll get an email alert 7 days before expiration. Expired packages can no longer have sessions logged against them.

Bringing an existing package into CountedIn

Choose Record an existing package, enter the original total sessions, and set Sessions remaining now. For a 10-session package with 6 left, enter 10 and 6. CountedIn starts at 6 remaining without creating four past visits, a payment, or a client email. The next session you actually log leaves 5 remaining and one session in the history.

You can enter 0 remaining for an exhausted package, or the full total for an existing package that has not been used. Existing-package mode sends no creation confirmation in either case. The opening balance is recorded once and cannot be edited; subsequent session logs and undo actions change the current balance.

Note

Package cards and the client's balance link show credits used before tracking separately from sessions recorded in CountedIn. Past visits are not reconstructed. Existing records keep their current balances and history.

Follow the existing-package walkthrough and see the client's balance view.

Package templates

If you sell the same packages repeatedly, create templates to save time. A template saves the package name, session count, price, and expiry duration so you can create new packages with one click.

Go to Settings

Templates are managed in your account settings. Navigate to Settings from the sidebar.

Create a template

Click New Template and fill in the default values. For expiry, set a number of days (e.g., 90 days) rather than a specific date.

Use the template

When creating a new package for a client, you'll see your templates listed. Click one to pre-fill all the values, then adjust if needed and save.

Tip

Set up templates for your most common packages during initial setup. It makes adding packages much faster day-to-day.

Tracking credits

Every package shows a progress bar that visually represents how many sessions are remaining out of the total. The progress bar changes color as credits run low:

Green - plenty of sessions remaining
Amber - running low (1-2 sessions left)
Red - exhausted (0 sessions remaining)

Note

The client list page shows total remaining credits across all of a client's active packages, so you can see at a glance who's running low.

Multiple packages per client

Clients can have multiple packages at the same time. This is useful when:

A client buys a new package before the old one is fully used
You offer different types of sessions (e.g., 1-on-1 vs. group)
A client has packages with different expiration dates

When logging a session, you choose which package to deduct from. The credit comes off the selected package only.

Package expiration

If you set an expiration date on a package, CountedIn will:

Send you an email alert 7 days before the package expires
Mark the package as expired on the expiration date
Prevent new sessions from being logged against it

Any unused credits on an expired package remain visible in the client's history but can no longer be used.

Managing Clients

Logging Sessions