> 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/rtp-troubleshooting/rtp-submitting-screenshots-tips.md).
# RTP - Submitting Screenshots tips
Some helpful tips for submitting screenshots for support with products that aren't syncing, customers not in sales fetch, etc
### Order Processing
Some tips for submitting a screenshot of the applicable customer's order in RTP.
1. Ensure that the Order Id is visible in the screenshot.
2. Click the blue triangle to select *List View* instead of *Summary View* (List View provides more details for us to help troubleshoot the potential issue).
3. Click the *View* option and select *All* instead of *Open*.
4. Ensure the screenshot includes the *Customer ID* and *Customer Name* fields. Also expand the width of the Description column if need be so that the product description is fully visible.
5. If possible, include the Deposits and Transaction Viewer portion of the screenshot. The Transaction Viewer can be added by clicking on *Advanced Options* > *Transaction Viewer*. 
### Transaction History
As a best practice, all lesson products should be sold in Order Processing and not Sales Transaction. It allows for the frontline staff to have an easier time reviewing what has been purchased and making updates (changing details about a private, changing dates for a lesson, swapping a ski lesson for a snowboard lesson, etc). If a lesson was sold in Sales Transaction it won't be possible to take a screenshot from Order Processing. In that case, a screenshot from Transaction History will be the best option to aid with troubleshooting.
1. In Customer Manager search for & find the lesson participant.
2. Navigate to History Profiles > Transaction History.
3. Expand any relevant transactions to include details that will help flaik troubleshoot the issue - eg transaction #, Customer #, Order # (if applicable), Inventory Pool descriptions, etc.
### Skier Profile
If submitting a ticket related to ability levels not syncing from RTP to flaik, please include the guest's Skier Profile.
A screenshot like either of these examples works equally well for us:
### Email Address or Phone Numbers
If submitting a ticket related to an email address or phone number not syncing to flaik, please include a screenshot of the Email Profile and/or Phone Profile, including the last update date on the right side.
---
# 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/rtp-troubleshooting/rtp-submitting-screenshots-tips.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.
