> ## 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. # Work with Lana, your Visito business assistant > Ask Lana to investigate your business, explain Visito, prepare downloadable reports, and propose operations for your approval. Lana helps administrators work with the business selected in the dashboard. Ask a question in plain language, follow the activity in the chat, and review the evidence or downloadable result. Use Lana for your team's operational work. Your customer-facing agent continues to answer guests through your connected channels and [Playground](/product-guides/ai-agent/test-your-agent). Lana is available to registered administrators in businesses where it has been enabled. If it is missing, confirm the selected business and your access with your workspace administrator or Visito Support. Illustrated Lana workflow: ask a scoped question, review activity and approvals, then inspect the answer or download a report. ## Start a conversation 1. Confirm the business selected in the dashboard. 2. Open **Lana** from navigation, or use the Lana composer on **Home** where available. The top-bar Lana button opens a compact panel; expand it for a full chat. 3. Describe the result you need, the date range, and any restrictions. When opening from a page, check any attached page context before sending. 4. Follow the activity, answer clarifying questions, and review the final result. For example: ```text theme={null} Review booking enquiries from October 5–11, 2026, in this business's timezone. Summarize the available evidence and prepare a follow-up spreadsheet. Do not send messages or change settings. ``` Choose **Standard** for everyday requests. Use **Deep analysis** when a request needs more involved reasoning; it can take longer. Select the mode before starting the next task. ## Choose a workflow Lana can explain Visito, review conversations and knowledge, investigate actions, and prepare reports. Available operations depend on your permissions, connected services, and enabled tools. Pick a goal and copy a starting prompt for documentation, conversations, knowledge, reports, actions, or reply drafts. Review booking enquiries step by step, download a spreadsheet, and prepare an optional follow-up. ## Follow progress and handle interruptions | Feedback | Meaning and next step | | - | - | | **Sending…** | Your request is being submitted. Avoid sending it again. | | **Working…** or **Starting…** | The request was accepted. Activity and results appear as they become available; this is not a queue position or completion estimate. | | **Waiting for your approval** | Inspect the proposed operation and select **Approve** or **Reject**. | | **Needs attention** | A step failed. Expand its activity receipt and read the explanation; it does not by itself mean the business has no credits. | | **Needs verification** | The operation's outcome is uncertain. Review the evidence before requesting another attempt. | | **Could not confirm delivery** | Submission was not confirmed. Use **Recover send** rather than creating another copy of the request. | Connection recovery is shown separately from task progress. Closing the panel or browser does not stop accepted work. Use **Stop** to request cancellation and wait for the stopped state. An operation already executed is not undone by cancellation. A business can have two active tasks, with one active request per chat. Each task has a ten-minute active-work limit. Split larger investigations into smaller date ranges or questions. Waiting for approval is limited to 30 minutes; expired proposals need a new review. ## Review approvals and results Business changes and external executions require an operation-specific approval. Review the business, target, arguments, effects, and expiry shown in the approval card. Approving one operation does not approve later changes. Reject it if the target or content is wrong, and ask for a revised proposal. Expand activity receipts to inspect status, outcome, and recorded time. A message **accepted for sending** is not yet proof of delivery. A completed availability or checkout action is not proof of payment or a confirmed reservation; ask for the corresponding evidence. ## Download reports Ask for a CSV, XLSX, or PDF and describe its columns, period, and intended audience. When a file appears in the chat, select its filename to download it. Review the contents before using or sharing it. Reports are limited to **10 MiB per file** and authorized dataset exports to **1,000 rows**. Ask Lana to disclose truncation, missing records, and unsupported conclusions. Narrow the range if the result reaches a limit. Saved chat content and reports are retained for **30 days**; download files you need to keep. ## Credits Lana uses the existing shared business credit balance. A new turn costs **one credit**, and each requested business tool action or read costs **one credit** after validation and any required approval. Started turns and actions remain charged if they fail or are cancelled. Progress updates, steering an active task, analysis, delegation, documentation retrieval, and export processing add no extra action credits. Business reads used to assemble a report still consume credits. Review consumption under **Lana** in [Billing & Usage](/product-guides/product/usage-billing). If credits run out or billing cannot be confirmed, the next chargeable step does not start. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.