ChronSync
Bookings

Set client allocations

Cap how many sessions a client can book against a ChronSync event type — a session package or quota that ChronSync enforces automatically as they book.

Limit how many sessions a particular client can book against an event type — for instance, a six-session coaching package or a monthly quota. ChronSync counts each booking and stops the client once they reach the limit, so you don't have to track it by hand.

How allocations work

An allocation ties one client's email to one event type and sets a maximum number of sessions. From then on:

  • Each time that client books the event type, ChronSync counts one session against the allocation.
  • When the limit is reached, ChronSync stops them booking more of that event type.
  • If the client cancels in time, the session is given back so they can rebook.

You can see how many sessions each client has used on the Allocations page, shown as used out of the maximum (for example, "2 / 6").

Before you start

  • Know the client's email and which event type the allocation applies to. Use the same email the client books with.
  • Decide the maximum number of sessions to allow.

Create an allocation

Go to Allocations in the main navigation.

[Screenshot: The Allocations page with the Create Allocation button and the allocations table]

Click Create Allocation.

Choose the Event Type the allocation covers.

Enter the client's Client Email.

Set Max Sessions — the most the client can book for this event type.

[Screenshot: The Create Allocation panel with the event type, client email, and max sessions fields]

Optionally set a Completion Date and add Notes for your own reference.

Click Create Allocation.

The new allocation appears in the table on the Allocations page, starting at zero sessions used. ChronSync begins enforcing the limit straight away.

Edit an allocation

Open an allocation from the Allocations page and click to edit it. You can change the Max Sessions, Completion Date, and Notes. The client email stays fixed once the allocation exists.

You can't set Max Sessions below the number of sessions the client has already used — for example, if they've used 4, you can't lower the maximum past 4.

Allocations can't be deleted once created. To effectively close one, set Max Sessions to the number of sessions already used — the client then can't book any more against it.

On this page