How the Customer Profile Tracks Lesson History, Waivers, and Payments in One Place
Published September 22, 2026 · Updated September 22, 2026
How the Customer Profile Tracks Lesson History, Waivers, and Payments in One Place
A customer books a private climbing lesson in March. She comes back for a group session in June. She reschedules once because of rain, tips the instructor after the session, signs two different waivers, and pays a deposit on the first lesson and the full amount on the second.
Where does all of that information live?
For most outdoor schools, the answer is five different places. The booking is in a calendar. The waiver status is in a folder or a spreadsheet. The payment history is in Stripe or a notebook. The instructor's notes are in a text thread. The fact that she rescheduled once is in your head, maybe, if you were the one who handled it.
That works fine when you have ten customers and one instructor. It stops working when you have a hundred customers, three instructors, and someone books again six months later. You can't remember if they signed the waiver. You don't know if they paid last time. You don't know what the last instructor said about their experience level. So you start over, ask the same questions, and make them sign the same waiver again because you're not sure.
The fix is not a better memory. The fix is one customer record that holds everything: every lesson they have taken, every waiver they have signed, every payment on file, and every note an instructor left after a session. When someone books again, you open their profile and you know exactly where they left off.
This guide walks through what the customer profile actually shows, why tying everything to the customer's email matters, and how it eliminates the spreadsheet problem where lesson history, waiver status, and payment records are all in different places.
Table of Contents
The Spreadsheet Problem: Customer Data in Five Different Places
Most outdoor schools start with a spreadsheet. One tab for bookings, one tab for payments, maybe a folder somewhere for signed waiver PDFs. Instructor notes go in a notebook or a text thread. It works for a while, until it doesn't.
The problem is not the spreadsheet. The problem is that a spreadsheet is a flat grid, and a customer is not flat. A customer is a person who has taken lessons, signed waivers, paid invoices, tipped instructors, rescheduled because of weather, and left feedback. All of that information is connected to the same person, but in a spreadsheet world, none of it is actually connected to anything except the email address you typed into five different cells.
So when someone books again, you open the booking tab and see their name. You don't see that they already signed the waiver. You don't see that they owe you $50 from last time. You don't see that the last instructor said they were ready for the intermediate lesson. You see a name in a row, and that is all.
That is the part that breaks.
For context on the larger operational picture, including how scheduling, weather, waivers, and payments fit together across the whole business, see The Complete Guide to Running an Outdoor Lesson Business. That piece covers the full scope of running the operation; this one focuses specifically on the customer record.
What the Customer Profile Actually Shows
Open a customer profile in Seshana and you see a single page with six sections: contact information, lesson history, waiver status, payment history, instructor notes, and any customer-specific flags like VIP or hour packages.
The lesson history is a list of every session that customer has taken, with the date, the lesson type, the instructor, the status, and the outcome. The waiver status shows which templates they have signed, when they signed them, and whether those waivers are current or expired. The payment section shows every payment they have made, every refund, every invoice, and whether they owe anything. The notes section shows what the instructor wrote after each session.
All of that lives on one screen. Not five tabs in five different spreadsheets. One screen.
That is the difference. When someone books again, you open their profile and you know exactly where they left off. You know if they are current on their waiver. You know if they paid last time. You know what the instructor said about their skill level. You don't have to ask them to fill out the same form again or hunt through old emails to figure out if they already signed something.
This is the same admin and instructor view a rock climbing school sees when a customer books a lesson in the public calendar or the embedded widget. The customer does not log in to see this screen. The profile is visible only to the school's staff. Digital Waivers for Outdoor Lesson Schools: What They Are and Why They Matter walks through how waivers are collected and stored. How Outdoor Lesson Schools Handle Payments: Pay Now, Pay Later, or Deposit covers how payment records are created and tracked. This piece explains where all of that information shows up when you actually need to look at it.
Lesson History: Every Session in One Place
The lesson history is a reverse-chronological list of every session the customer has taken. Each row shows the date, the lesson type, the instructor, the location, the status, and whether the lesson was completed, cancelled, or marked incomplete.
If a lesson was rescheduled because of weather, both the original date and the new date appear in the history. If the customer tipped the instructor, the tip amount is visible. If the instructor left notes after the session, those notes are linked from the lesson row.
This is useful in two ways. First, it shows you what the customer has already done. If they took a beginner kiteboarding lesson last year and they are booking again this year, you know they are not starting from zero. You can recommend the next lesson type without asking them to describe their experience level.
Second, it shows you what went wrong. If a customer cancelled three times in a row because of weather, you can see that pattern. If they no-showed once, you can see that too. That information matters when you are deciding whether to require a deposit or whether to reach out before the next lesson to confirm.
Lesson history is not just a log. It is the record you use to make better decisions about what happens next.
Waiver Status: Current, Expired, or Missing
The waiver section shows which waiver templates the customer has signed, when they signed them, and whether those waivers are still valid.
If your school uses once-ever waivers, a customer signs once and they are done. If you use expiring waivers, the waiver status shows the expiration date. If a waiver is expired, the status changes and the customer cannot book again until they sign a new one.
If the customer has not signed a waiver yet, the status shows as missing. You can send a waiver email directly from the customer screen, or you can wait for the auto-send to handle it when they book.
This is the part that matters most: the waiver status is not a guess. It is a field on the customer record, and it is always current. You do not have to search a folder or ask the customer if they already signed something. You open their profile and you know.
When waiver auto-send is enabled, Seshana sends a waiver email the moment a customer books, whether they book through the widget, the public calendar, or the kiosk. The waiver link goes to their email address. They sign it. The status updates. You see it on the customer screen. That is the whole loop.
For a deeper look at how waivers are collected and what the signing process looks like, see Digital Waivers for Outdoor Lesson Schools: What They Are and Why They Matter. That piece covers the waiver templates, the signing modes, and the email flow. This one focuses on where the waiver status shows up after the customer signs.
Payment Records: What They Paid and When
The payment section is a list of every payment the customer has made, every refund issued, and every invoice created. Each row shows the amount, the date, the payment method, and what the payment was for.
If a customer paid a deposit up front and the rest at the lesson, both payments appear. If you refunded part of a lesson because of weather, the refund appears. If they paid cash at the beach and you recorded it manually, that payment appears too.
This is not a Stripe dashboard. It is a customer-specific ledger. You see what this one person has paid, what they owe, and what they have been refunded, all in one place.
That matters when someone books again six months later and you cannot remember if they paid last time. You open their profile and you see the payment history. If they owe you $50, it is right there. If they always pay on time, you can see that too. If you need to issue a refund, you do it from the same screen where you see the original payment.
The payment section also shows whether a customer has a credit balance, a gift card, or an hour package on file. If they have ten hours left on a package, the balance appears at the top of the payment section. You do not have to track that in a separate spreadsheet.
For a breakdown of how payments are collected, whether you charge up front or at the lesson, and how deposits work, see How Outdoor Lesson Schools Handle Payments: Pay Now, Pay Later, or Deposit. This piece explains where those payment records show up once they are created.
Instructor Notes: What Happened After Each Session
After a lesson, the instructor can leave notes about what happened. That might be the customer's skill level, what they worked on, what they struggled with, or what they should try next. Those notes live on the customer record, tied to the specific session.
When the customer books again, you see those notes. You know what the last instructor said. You know what the customer was working on. You know whether they are ready for the next level or whether they need another session on the same material.
This is especially useful when a different instructor teaches the next lesson. They can read the notes from the previous session and pick up where the last instructor left off. The customer does not have to explain their experience level again. The instructor already knows.
Notes also matter for safety. If an instructor noticed that a customer was nervous in high wind, that is worth writing down. If a customer said they have a medical condition that might affect the lesson, that is worth writing down too. Those notes stay on the customer record, and every instructor who teaches that customer can see them.
Instructor notes are not just a log. They are the continuity that lets a school feel like it remembers the customer, even when the same instructor does not teach every lesson.
Why Email Is the Key That Ties Everything Together
The customer record is keyed by email address. That is not an accident. That is the design.
When someone books a lesson, they enter their email. When they sign a waiver, the waiver is tied to that email. When they make a payment, the payment is tied to that email. When the instructor leaves notes, the notes are tied to that email. Everything is tied to the same key.
That means when the customer books again, even six months later, even through a different booking flow, Seshana recognizes them. Their lesson history is still there. Their waiver status is still there. Their payment history is still there. You do not have to ask them to fill out a form again or manually search for their old records.
Email is the key because email is the one piece of information that does not change. Customers move, change phone numbers, and forget to update their contact information. But they use the same email address. That makes email the stable identifier that ties a customer's entire history together.
This is also why duplicate customer records are a problem. If someone books once with john@example.com and books again with john.doe@example.com, those are two different customer records. Their history is split. Their waiver status is split. Their payment history is split. You lose the continuity that makes the customer record useful.
The fix is to merge the records. Seshana has a merge tool that combines two customer records into one, preserving all the lesson history, waiver status, payment records, and notes from both. After the merge, the customer has one profile with all their information in one place.
How Waiver Status Blocks Booking When It Needs To
When a customer tries to book a lesson through the widget or the public calendar, Seshana checks their waiver status. If the lesson requires a waiver and the customer has not signed one, or if their waiver is expired, the booking flow stops them.
The customer sees a message that says they need to sign a waiver before they can complete the booking. They can sign the waiver right then, during the booking flow, or they can sign it later from an email link. Either way, the booking does not go through until the waiver is signed.
This prevents a common problem: a customer shows up for a lesson and you realize they never signed the waiver. Now you are standing on the beach with a piece of paper and a pen, trying to get them to sign something they should have signed a week ago. Or worse, you let them take the lesson without a waiver because you do not want to turn them away.
The waiver block solves that. If the waiver is required, the customer cannot book until it is signed. If the waiver is expired, they cannot book until they sign a new one. The status is checked automatically, at booking time, when it actually matters.
This only works because the waiver status is tied to the customer record. When someone books, Seshana looks up their email, checks their waiver status, and either lets them proceed or stops them. That check happens in real time, every time, for every booking.
One Customer Record, Not a Pile of Disconnected Data
The reason the customer profile matters is not because it shows you information. It is because it shows you everything in one place.
You do not have to open a booking tab, then a payment tab, then a waiver folder, then a text thread with the instructor. You open one screen and you see the whole picture. That is the difference between a customer record and a spreadsheet.
It also means you can make better decisions. You can see if a customer is a repeat customer or a one-time visitor. You can see if they have a pattern of cancelling. You can see if they tip. You can see if they are current on their waiver or if they need a reminder. You can see what the instructor said after the last lesson.
All of that information is already in your business somewhere. The problem is that it is not connected. The customer profile connects it. It takes the booking history from the schedule, the waiver status from the waiver system, the payment records from the payment ledger, and the instructor notes from the follow-up flow, and it puts all of it on one screen, tied to one email address.
That is the part that lets a school grow without losing track of people. When you have ten customers, you can remember all of this. When you have a hundred, you cannot. The customer record is the tool that lets you treat every customer like you remember them, even when you do not.
FAQ
Do customers need to create an account to have a customer record? No. The customer record is created automatically when someone books a lesson, signs a waiver, or makes a payment. The record is visible only to the school's admin and instructors. Customers interact with the school through public booking links, waiver emails, and payment pages, without creating a Seshana login.
What happens if a customer uses two different email addresses? Seshana treats them as two different customers. Their lesson history, waiver status, and payment records are split across two profiles. The fix is to merge the two records into one using the merge tool in the customer screen. After the merge, all the information from both records is combined into a single profile.
Can an instructor see the full customer record, or just their own notes? Instructors can see the full customer record, including lesson history, waiver status, and notes from other instructors. This is intentional. When a customer books again with a different instructor, that instructor needs to see what happened in the previous lesson. The customer record is a shared tool for the whole team.
What if a customer books through Shopify instead of the widget? A Shopify order creates a paid-unscheduled lesson in Seshana. That lesson is tied to the customer's email, just like a widget booking. Once the admin schedules the lesson, it appears in the customer's lesson history. The waiver status and payment records are tied to the same customer record, so everything stays connected.
How does the customer screen handle group lessons where multiple people book together? Each participant in a group lesson gets their own customer record. The primary booker's email is also stored on the lesson, but every participant has a separate profile with their own lesson history, waiver status, and payment records. If the same person books again later, their profile includes both the group lesson and any private lessons they took.
Can you track how much a customer has spent over time? Yes. The payment section shows every payment the customer has made, and the total is visible at the top of the section. This includes lessons, tips, gear rentals, and any other charges. You can see the lifetime value of the customer in one place, without exporting anything or opening a separate report.
Keep reading
September 22, 2026
How Outdoor Schools Handle Payment Timing When Weather Can Cancel a Lesson
A yoga studio charges at booking because the class will happen. An outdoor school cannot guarantee the lesson will run until the weather cooperates. How schools choose payment timing based on their sport's weather risk, and how scheduling software handles deposits and pay-after bookings.
Read →
September 22, 2026
How to Collect Waivers and Payments at the Same Time for Walk-In Customers
A customer walks up to the dock without a reservation and asks if you have room for a lesson today. Walk through the operational flow: how to check availability, get a waiver signed on the spot, and collect payment before the lesson starts.
Read →
September 22, 2026
Why Gym and Salon Booking Software Doesn't Work for Outdoor Lesson Schools
Salon software has no weather layer, no waiver before the customer hooks in, no equipment tied to the lesson, and no concept of tides or wind windows. Here's what breaks when a kite school uses Mindbody, a climbing guide uses Acuity, or a barn uses a spreadsheet, and what outdoor-specific software actually solves.
Read →
