> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/siriusware/flaik-siriusware-integration-standards/without-ssm/private-lessons.md). # Private Lessons Integration standards for resort using Siriusware without the Ski School Module | | Preferred | Also Supported | Notes | | :---------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | | Lesson Date | Lesson Date and Product Date are required to be the same | | | | Lesson Duration | Specific Duration Modifier attached to the sale (e.g. "ARMOD900") | Can use substring from the Item (e.g Item = "ARP1FADLSK" substring = "1F") | | | Start Time | Specific Start Time Modifier attached to the sale (e.g. "ARMOD900") | Can use substring from the Item (e.g Item = "ARP1FADLSK" substring = "1F") | | | Discipline | Set in flaik on the Task | Can use a product modifier | | |

Additional Guests\*
(see notes below)

| | Can be a Unique DCI and mapped as an 'Additional Guest Product in flaik | | | Requested Instructor | Built-in Siriusware 'Messages' option | Can use a Custom Text Field mapped into the Guest Profile (same as all other Notes) | | | Consecutive Days | Mapped by flaik staff per DCI | Determined by a Modifier attached to the Sale |

Typical recommendation is to handle most Lesson attributes by 'Modifiers' in the case of CONSECUTIVE days, though we recommend having distinct DCIs per length for a variety of POS reporting and usability reasons.

To accommodate that we have the ability to set the number of days on mapping into flaik.

| | Guest Ability Level | Modifier attached to the sale | Can be a String/Number value mapped to a value on the Guest Profile | All lesson types should share the same ability level scale (eg 1-6 for groups/privates/adults/kids) | | Lesson Ability Level | Modifier attached to the sale item | | | | Lesson Comments | Built-in Siriusware 'Messages' option | Can use a Custom Text Field mapped into the Guest Profile (same as all other Notes) | | ### Additional Guests If there will be multiple participants in a private lesson, the recommendation is to pass this information from SW to flaik via a modifier. The benefit from this method is that it ensures additional guests are associated with the correct lesson in flaik. * If a POS transaction contains two or more private lessons on the same date and at least one lesson has additional guests joining the lesson: * **If added via a modifier:** the additional guests will be added to the correct private lesson in flaik as outlined in the sale. * **If added via a unique DCI:** the additional guests will be added to the 'first' private lesson for that date in the sale. The only way to adjust this in flaik is to refund both private lessons & additional guest products in the POS and then sell each private lesson again as separate transaction. As a result, it is recommend to use a modifier for adding more guests to a private lesson. It helps ensure that they are associated to the correct private lesson in both systems. This is especially relevant for privates sold online, as it wouldn't be possible to limit one private sold for the same date in a transaction. Additionally the modifier must be sold to an actual guest. It can't be sold to no guest. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/siriusware/flaik-siriusware-integration-standards/without-ssm/private-lessons.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.