> ## 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.

# What can you do with Lana?

> Choose a Lana workflow and copy a practical starting prompt for your business.

Start with the outcome you need. Choose a card below, adapt its prompt to your business, and review the evidence Lana returns. For access, progress, approvals, and credits, see the [Lana overview](/product-guides/product/lana).

<Columns cols={2}>
  <Card title="Understand Visito" icon="book-open" href="#understand-visito">
    Get an explanation of a feature with links to the relevant documentation.
  </Card>

  <Card title="Review a conversation" icon="comments" href="#review-a-conversation">
    Summarize what happened and identify the next human decision.
  </Card>

  <Card title="Audit your knowledge" icon="magnifying-glass" href="#audit-your-knowledge">
    Find gaps in existing information and prepare suggested edits.
  </Card>

  <Card title="Build a booking enquiry report" icon="file-spreadsheet" href="/product-guides/product/lana-booking-report">
    Follow the complete example: scoped evidence, spreadsheet download, and optional follow-up.
  </Card>

  <Card title="Investigate a failed action" icon="wrench" href="#investigate-a-failed-action">
    Inspect the saved execution without rerunning it.
  </Card>

  <Card title="Prepare a guest reply" icon="pen-to-square" href="#prepare-a-guest-reply">
    Review a draft before deciding whether to propose a send.
  </Card>
</Columns>

## Understand Visito

Use this when you need to understand a feature before changing anything.

```text theme={null}
Explain the difference between a handoff and an internal review in Visito.
How do automatic replies behave in each case? Link the relevant published
documentation and explain what I should check in my business. Do not change settings.
```

**Review:** the linked documentation, the current business configuration if inspected, and any differences between them. An explanation does not apply a configuration change.

## Review a conversation

Open the relevant conversation and confirm any attached page context, or provide its conversation ID.

```text theme={null}
Summarize conversation [conversation ID]. Separate the guest's request,
recorded actions, unresolved questions, and the next human decision.
Use the saved evidence and identify anything you cannot confirm.
Do not send messages or change the conversation's state.
```

**Review:** source messages and recorded outcomes. A proposed next step is a suggestion, not an operation already completed.

## Audit your knowledge

Use this to prepare an editorial review of your existing sources.

```text theme={null}
Review the knowledge sources available to this business for check-in and
late-arrival information. Identify missing or contradictory details, cite
the sources, and propose concise edits. Do not invent a policy or apply changes.
```

**Review:** source coverage and proposed wording. Confirm the actual business policy before asking Lana to propose an approved update.

## Investigate a failed action

Provide an execution ID, or the conversation and time of the failure. Do not paste credentials.

```text theme={null}
Inspect the failed action in conversation [conversation ID] around [date and time].
Explain its recorded request, outcome, and any evidence of an external effect.
Separate confirmed facts from possible causes. Do not rerun the action.
```

**Review:** the saved receipt and error. A failed request can have an uncertain external outcome; verify that outcome before requesting another execution.

## Prepare a guest reply

Start with a draft so you can review the content before requesting an operation.

```text theme={null}
For conversation [conversation ID], draft a short reply based on the guest's
latest question and our current knowledge. Flag missing information rather
than inventing it. Show me the draft only; do not send it.
```

**Review:** the conversation, business facts, language, and wording. If you later ask Lana to send it, inspect the operation-specific approval card. Approving one operation does not authorize additional sends. Acceptance for sending does not confirm delivery.

## Want a downloadable result?

For a complete workflow with dates, evidence, report columns, coverage checks, and downloads, follow the [booking enquiry report example](/product-guides/product/lana-booking-report).

These prompts use only the tools and information available to your administrator account. Business reads consume shared credits; documentation retrieval and export processing add no extra action credit. See [Lana credits and limits](/product-guides/product/lana#credits).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.