> ## Documentation Index > Fetch the complete documentation index at: https://docs.visitoai.com/llms.txt > Use this file to discover all available pages before exploring further. # Use Lana to review booking enquiries and prepare a report > Find enquiries using recorded action evidence, create a downloadable follow-up report, and review any proposed guest reply before sending. A hotel manager wants to review last week's booking enquiries before deciding who needs a follow-up. Lana can gather authorized evidence, explain the gaps, and prepare a spreadsheet without contacting guests. This example uses fictional data and an availability action already configured for the business. It illustrates a workflow, not a live customer result. Your action names, data, and available tools can differ. Illustrated booking enquiry report with fictional rows, evidence labels, and an explicit unknown booking outcome. ## 1. Define the question Select the intended business and start a new Lana chat. Use explicit dates and distinguish action activity from a confirmed booking: ```text theme={null} Prepare a booking-enquiry review for October 5–11, 2026, using this business's timezone. First identify our availability and booking actions and ask me to clarify if more than one matches. Find conversations with an availability action executed during that period. Use the recorded action history, deduplicate conversations, and include the conversation ID, contact name when available, action time, action outcome, booking evidence, and a suggested next step. Do not infer a booking or payment from an availability result or completed checkout. Mark missing evidence as unknown. Do not send messages or change data. ``` The selection is **actions executed during the period**. This differs from conversations whose latest message happened during the period, or guests who asked a question without ever reaching the availability action. If you need all enquiries, including those without an action, ask for that broader investigation explicitly. Its completeness depends on the conversation and message history available. ## 2. Review the evidence before making a report Lana uses the permitted read tools and records activity in the chat. It may ask you to choose an action or narrow the dates. Ask for a summary of: * The action and time window used, including the timezone. * How many unique conversations were included and whether all result pages were read. * Failed actions, missing contact fields, missing history, and any truncation. * Which outcomes are recorded facts and which next steps are suggestions. For this fictional example, an availability result only shows that availability was checked. The booking-outcome column stays **Unknown** until the available evidence establishes otherwise. Missing records do not establish that no bookings occurred. ## 3. Request a downloadable file Once the scope is correct, ask: ```text theme={null} Create booking-enquiry-review.xlsx from the evidence you just reviewed. Use one row per conversation with the columns above. Add a Coverage sheet with the dates, timezone, action selected, source counts, and any missing or truncated data. Keep unknown values explicit. Do not include message bodies or unnecessary personal information. Give me a short summary in the chat. ``` Select the generated filename in the chat to download it. Use CSV for a simple flat table, or ask for a PDF summary if you need a shareable narrative. A file is only ready once Lana has generated it and its download is available. Check the selection and a few source conversations before using the report. Download it within the **30-day retention period**. If a dataset reaches **1,000 exported rows** or a file exceeds **10 MiB**, narrow the period or request smaller reports and check that the parts do not overlap. Creating the export adds no action credit by itself. The initial turn and the business reads used to gather evidence consume shared credits. Another message that starts a new turn also consumes a turn credit. ## 4. Optionally prepare one follow-up Choose a specific conversation from the reviewed report. Keep drafting separate from execution: ```text theme={null} For conversation [conversation ID], draft a short reply asking whether the guest still needs help with their dates. Use the current conversation context. Show me the draft only; do not send it. ``` After reviewing the draft, you can ask Lana to propose the supported send operation. Inspect the approval card's recipient, channel, exact text, and effects before selecting **Approve**. Select **Reject** if anything needs changing. A report does not authorize sending, and one approval does not authorize the whole spreadsheet. Check the recorded request and delivery outcome after an approved send. If the outcome needs verification, resolve it before requesting another send. ## Keep exploring Try documentation, knowledge, conversation review, and action troubleshooting prompts. Review progress, approvals, limits, downloads, and credits. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.