> 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/rtp/4.-rtp-specific-flaik-functionality/rtp-or-fields-for-group-lessons.md). # RTP - Fields for Group Lessons There are several flaik fields available for Group Lesson details captured in the POS system. Below is a guide to the available fields in flaik and the RTP location the field is populated from.\ \ If you have custom prompts configured in RTP that correspond with flaik fields listed below, please contact us at to discuss whether it's possible for flaik to custom map to those prompts. ### **Guest / Customer Details** **(Guest) Name - First and Last** * flaik Name fields are populated with the Customer who is associated with the purchased product, i.e. the order line, rather than the purchaser of the product. **(Guest) Age** * The flaik Age field is populated using the birthdate associated with the Customer’s Guest Profile in RTP. **(Guest) Email** * The flaik Email field is populated from the Customer’s Guest Profile in RTP. * If no email is included on the customer's email profile and the Head of Household has an email available, the Head of Household email will be used. **(Guest) Phone** * The flaik Phone field is populated from the Customer’s Guest Profile in RTP. * If the Customer is a child and there is an Emergency Contact phone number in the Child Registration Form/Emergency Contact Profile, that phone number will populate the guest phone field. If neither the phone profile nor the Child Registration Form/Emergency Contact Profile is filled in, the phone number will be populated from the Head of Household phone field. **Emergency Contact** * The flaik Emergency Contact will initially be populated from the Child Registration Form/Emergency Contact Profile first. If the Child Registration Form/Emergency Contact Profile is not filled in, the emergency contact will be populated from the Head of Household phone field. If the Head of Household phone field is not filled in, the emergency contact will be populated from the participant's phone profile. ### **Medical Information** **Allergy - Food and Drug** * The flaik Allergy fields are populated from the Child Registration Profile/Emergency Contact Profile. **Medication** * The flaik Medication field is populated from the Child Registration Profile/Emergency Contact Profile. **Special Condition** * The flaik Special Condition field is populated from the Child Registration Profile/Emergency Contact Profile. ### **Lesson Details** **Product - Product Description (RTP)** * The flaik Product field is populated based on the sale associated with the Customer in RTP Order Processing. **Discipline** * The flaik Discipline field is populated by the selection made on the connected Task in Admin Settings. * Mapping between RTP group lesson products and flaik Tasks should be 1:1. **Lesson Date - Date of Lesson** * The flaik Lesson Date is populated from the inventory pool date in RTP. The lesson will appear on the selected day in Scheduling - Task View. * Group lessons should be inventoried. **Ability Level / Lesson Level** * If no ability level exists in flaik, the Ability Level can be populated from the Skier Profile in RTP. Once the Ability level is set within flaik it will never be overwritten from the POS. * RTP Lesson Levels must be mapped by a flaik staff member to flaik Ability Levels. **Start Time and Duration** * The start time and lesson duration are set in flaik for Group Lessons. * Mapping between RTP group lesson products and flaik Tasks should be 1:1. ### **Ecommerce Platform Orders** flaik fields are populated based on the RTP fields listed above. If the ecommerce platform used does not populate the fields above, it may be possible to make custom prompts within your ecommerce platform to populate the relevant RTP fields. --- # 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/rtp/4.-rtp-specific-flaik-functionality/rtp-or-fields-for-group-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.