Introduction
A customer buys five private language lessons. The payment succeeds, a confirmation arrives, and the first lesson goes well.
Two weeks later, they return to book again. Do they need to find the original offer? Pay again? Contact the teacher? How many lessons are left, and where can they check?
Those questions are part of the product the business sold. A package includes a continuing relationship, not only a discounted purchase.
This guide explains how to design that relationship so customers understand what they bought, how to use it and what happens when plans change. The examples are illustrative policies for a fictional language teacher, not default PAKA settings.
Decide exactly what one session means
“Five lessons” sounds specific until a customer asks whether the package can be used for group classes, shared with a partner or split into shorter appointments.
Before selling a package, define its unit of value. For example:
- Five individual, 45-minute language lessons.
- Available for the named learner.
- Delivered online with the selected teacher.
- Eligible lesson types clearly identified.
- Any booking deadline or expiry stated before purchase.
- Cancellation and rescheduling conditions shown with the offer.
These are business decisions. Software should express and apply the decisions you actually make, rather than forcing the customer to infer them from a title.
If there is no expiry, say so. If a package is restricted to certain services, explain which ones. If appointments depend on availability, do not imply that buying the package reserves five times automatically.
Separate the package purchase from the appointment
There are two distinct events:
Buying the package gives the customer an entitlement under its terms.
Booking a session assigns a particular appointment to that entitlement.
A useful confirmation makes this separation clear. If the customer has not selected a time, the message should say that the package has been purchased and explain how to arrange the first session. It should not say that the appointment is confirmed.
If the purchase includes a selected first appointment, show both records: the package and the specific booking details.
This clarity also helps the business answer questions. “I bought lessons” and “I booked Tuesday at 10” are different claims, and each should be easy to verify.
Make the balance understandable
A single number can become ambiguous as soon as future appointments exist.
Imagine the learner has purchased five lessons, completed two and scheduled one for next week. A screen that simply says “Three remaining” might leave them wondering whether next week’s lesson is included in that number.
A clearer explanation would separate the states:
- Two lessons completed.
- One upcoming lesson booked.
- Two lessons still available to book.
That is an example of a useful presentation, not a requirement to use those exact labels. The important part is that a customer can tell what has happened, what is scheduled and what they can still arrange.
The same logic should guide the language an AI agent uses. “You have two more lessons available to book” is more useful than an unexplained balance when another appointment is already scheduled.
Give returning customers a short route to the next session
Returning customers should not have to shop for something they already own.
After identifying the correct account, a useful journey begins with the customer’s existing package and eligible next steps. The learner might say, “I want to book my next lesson,” or choose an equivalent visible action.
Before confirmation, they should see the relevant service, teacher, date, time, timezone and location or online-meeting arrangement. If the booking uses an existing package, that should be clear too. If any additional charge applies, it must be explained before the customer agrees.
In PAKA, the customer’s personal space brings together purchased services, upcoming bookings and the package balance, with a route to book the next session from the existing order. Cancelling a package session within the permitted window returns that session to the package; cancelling the session is different from requesting a refund for the purchase. See PAKA’s customer experience.
Define what changes the balance
The hardest package questions often concern exceptions rather than ordinary attendance.
Write down what should happen when:
- A customer cancels within the allowed window.
- A customer cancels late or misses the session.
- The business cancels.
- A session is moved to another time.
- The customer books an ineligible service.
- A package reaches its expiry or is refunded.
The rules do not have to be identical for every business, but they do need to be explicit and consistent. Customers should not receive one explanation before purchase and another when they try to use a lesson.
For a rescheduled appointment, check both sides of the change. The old time should not remain presented as an upcoming booking, and the entitlement should not be accidentally counted twice. For a cancelled appointment, make the outcome visible: is the session available again, or was it used under the stated policy?
Do not use an AI response as the sole evidence that a change succeeded. The booking record and balance should support what the customer is told.
Keep the agent helpful without hiding the details
An agent can help a customer navigate their package in ordinary language. The visible interface should still provide something they can check.
For example, a returning learner might ask, “Can I use my package for a group conversation class?” A useful answer should explain the actual eligibility rule and show the relevant option or next step. It should not assume that any service offered by the teacher is included.
If the account or entitlement cannot be verified, the agent should not guess. Account information belongs to the authenticated customer, and questions that need a business decision should have a clear route to a person.
The goal is a coherent experience: the conversation helps the customer understand, the presentation makes the facts visible, and a supported action moves the booking forward.
Test the full package lifecycle before inviting customers
Use a realistic test account and follow one package all the way through. A successful payment alone does not prove the experience works.
Check these six moments:
- Purchase: Can the customer understand the eligible services and terms before paying?
- First booking: Is a time actually selected and confirmed, rather than merely suggested?
- Return visit: Can the customer find the package and book without buying it again?
- Completion: Does the record distinguish completed appointments from future ones?
- Change: Does a cancellation or reschedule produce the correct booking state and balance?
- Final session: Once the entitlement is used, is that clear without suggesting unused sessions remain?
Include a customer who clicks through the interface and one who asks the agent for help. Both paths should lead to the same facts and valid outcomes.
Where a step requires staff intervention, make that handoff understandable. The customer needs to know whether a request has been received or a change has actually been made.
Make the fifth lesson as clear as the first
The value of a package depends partly on how easy it is to keep using it. Clear terms at purchase, understandable balances and a straightforward return journey reduce the need for customers to repeatedly ask what they own.
For an agent-first business, that continuity matters. The agent should help customers act on an existing relationship, while the Canvas makes the relevant information and next choices visible.
Before promoting your next package, follow the journey as a returning customer. Ask one practical question: “If I came back a month from now, would I know exactly what I can do next?”
For the broader relationship after a purchase, read Returning customers. For choosing booking software more generally, see How to choose an online appointment booking system.


