# AI Content Assistant for Product Tours

> The AI Content Assistant drafts tour step copy — a title and a description — from the UI context of the element a step is anchored to. It runs in the StepsKit dashboard at authoring time, is always user-initiated, and never runs in the embed on your customers' site.

*Source: https://stepskit.com/features/ai-content-assistant*

## What it does

Click "Suggest Title & Description" on any tour step. StepsKit sends UI metadata — element text, tag type, ARIA labels, page title, and the copy of previous steps — to the AI provider and returns a suggested title and description. You accept it, edit it, or give feedback and regenerate.

## Capabilities

| Capability | Detail |
| --- | --- |
| Context-aware suggestions | Reads button labels, headings, ARIA attributes, and surrounding UI elements to understand what the user is looking at. |
| Narrative flow across steps | Each suggestion considers previous steps in the tour, so step 3 doesn't repeat step 1. |
| Iterative refinement | Add direction ("make it shorter", "focus on the benefit") and regenerate. |
| Tuned for microcopy | Titles land at 2–8 words; descriptions at 1–2 sentences. |

## How it works

1. Select a tour step in the builder — new or existing.
2. Click "Suggest Content." StepsKit sends UI metadata (element text, tag type, page title). No end-user data is transmitted.
3. Review the suggested title and description. Accept as-is, edit, or provide feedback and regenerate.
4. Publish when ready. AI writes the first draft; you control what goes live.

## Pricing

| Plan | AI generations |
| --- | --- |
| Free | 10 generations included |
| Pro — $19/month | Unlimited generations |

See [pricing](/pricing.md) for the full plan.

## Privacy and data handling

**Sent to the AI provider:**

- UI metadata — element text, tag names, ARIA labels, page titles
- Tour context — the copy of previous steps in the same tour

**Never sent:**

- End-user personal data, form values, or credentials
- Any data collected by the embed script on your customers' site

**Handling:**

- The provider is Anthropic (Claude API). Under Anthropic's API terms, data sent through the API is not used to train or improve their models. API logs are retained up to 30 days for safety monitoring.
- Always opt-in and user-initiated — the AI never runs in the background.
- Every suggestion can be edited or replaced with manual copy.

Full detail in the [Privacy Policy](/privacy.md) (Section 4) and [Terms of Service](/terms.md) (Section 8).

## FAQ

**What data does the AI see?**
Only UI metadata: element text content, tag names, ARIA labels, page title, and the text of previous tour steps. Never end-user data, form values, passwords, or personal information from your users.

**Is the AI content any good?**
It's tuned for product tour microcopy — short, action-oriented, context-aware. Most suggestions need minor edits at most, and you always review before publishing.

**Can I still write copy manually?**
Yes. AI is optional. Every step has standard title and description fields.

**Which model powers it?**
Anthropic's Claude API. Data is processed under Anthropic's API terms, which prohibit using customer data for model training.

**Does AI content affect tour performance for end users?**
No. Generation happens at build time in the dashboard. The embed script on your customers' site never calls an AI provider — it only displays the copy you approved.

## Related

- [All features](/features.md)
- [Visual tour builder](/features/visual-tour-builder.md)
- [AI agents (MCP)](/features/ai-agents.md) — a different feature: authoring tours from your codebase via an AI coding agent
- [Pricing](/pricing.md)