> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inklyai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Annotations and storylines

> Show the guide what matters and put those moments in order.

An **annotation** tells the guide where to point and why it matters. A **storyline** puts annotations in an order the guide can follow.

<Note>
  **Inkly AI can write these for you.** Click **Inkly AI** and try: “Review my screens. Add annotations for the strongest product moments, explain why each matters to a buyer, and build a concise storyline around them.”
</Note>

## Add an annotation

Open **Assets**, select a screen, and add an annotation.

| Setting        | What to add                                                                                    |
| -------------- | ---------------------------------------------------------------------------------------------- |
| **Target**     | Select the product area the guide should point to. Choose a region large enough to notice.     |
| **Kind**       | Use **Showcase** to point and explain. Use **Action** when the guide should click.             |
| **AI context** | Explain what the feature does and why the buyer should care. The visitor never sees this text. |

Good context sounds like a briefing, not a tooltip:

> Dragging a bar reschedules the job without opening a form. Dispatchers do this dozens of times each morning, so this removes repetitive data entry.

On an image, **Action** shows a click without changing screens. Clickable captured pages are an [Enterprise capability](/account/enterprise).

## Build a storyline

Open **Storyline**, then:

1. Give the storyline a goal from the visitor's perspective.
2. Add annotations in the order that best explains the value.
3. Open **Preview** and test the flow.

Keep each storyline focused:

* Use six to ten annotations.
* Start with the problem, not your navigation.
* Explain one idea at a time.
* End where your [next step](/build/outcomes) makes sense.

Create another storyline only when a different audience needs a different argument.