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

# Use the Jurni Agent

> Start a page-building conversation with the Jurni Agent, attach products and campaign references, and continue working in the editor.

The **Agent** is the conversation workspace you open from Jurni's main sidebar. Use it to start a page-building task with your products, creative, and references. Use **AI inside the editor** when you are already working on a particular experience and want to change its content.

## Start a page-building conversation

<Steps>
  <Step title="Check the active shop">
    Confirm the brand in the shop switcher. The products and assets you provide should belong to the shop you are building for.
  </Step>

  <Step title="Open Agent">
    Select **Agent** in the main sidebar. Start with one clear outcome, such as building a landing page for a specific campaign.
  </Step>

  <Step title="Attach the source material">
    Add the relevant product, media, file, Meta ad, saved experience template, Figma link, or web link using the attachment options. Describe what each reference should contribute.
  </Step>

  <Step title="Describe the page and its boundaries">
    Include the audience, offer, desired page structure, and primary action. State which claims and assets are approved. A design reference should not be treated as permission to copy another brand's product claims.
  </Step>

  <Step title="Continue in the editor">
    When the Agent completes experience creation, Jurni takes the conversation into that experience's editor. Review the page there, configure purchasing behavior, and continue with focused edits.
  </Step>
</Steps>

## Choose useful context

| Attachment          | How to use it                                                                                                                  |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Product             | Identify the actual product the page should sell rather than relying on a similar product name.                                |
| Media or file       | Provide approved images, creative, copy, or a campaign brief. Explain where each asset belongs.                                |
| Meta ad             | Connect the landing-page message to a particular ad's audience and creative angle. Access depends on the connected ad account. |
| Experience template | Give the Agent an existing page structure to work from. Review products, offers, and wording after creation.                   |
| Figma link          | Specify the exact frame and whether it represents desktop or mobile.                                                           |
| Web link            | Explain whether you want to reference layout, visual style, messaging structure, or shopping interaction.                      |

## Example starting prompt

> Build a mobile-first landing page for the attached product and Meta ad. Keep the ad's creative angle, use the approved copy in the attached brief, and include a hero, benefits, reviews, Buy Box, and FAQ. Use the attached reference for layout only. Do not invent discounts, product claims, ratings, or testimonials. The primary action should use the selected product's configured purchase option.

## Agent conversation versus editor AI

An Agent conversation can start before an experience exists. Once the conversation is connected to an experience, reopening it can take you directly into that experience's editor. This is expected; the work has not disappeared or moved to another shop.

For changes to an existing page, open the experience first, select the relevant section, and use the editor AI. This makes the target easier to identify and reduces accidental changes elsewhere.

## Review before launch

Treat the generated page as a draft to review, not proof that every product selection, subscription, discount, integration, and checkout action is correct. Check the actual page in desktop and mobile views and test the intended publishing environment before sending traffic.

* [Edit pages and sections with AI](/build/ai-editing)
* [Prompting best practices](/building-funnels/ai-chat-prompts)
* [Find and resume AI conversations](/build/chat-history)
* [Pre-launch QA checklist](/building-funnels/qa-checklist)


## Related topics

- [Find and resume AI conversations](/build/chat-history.md)
- [Edit pages and sections with AI](/build/ai-editing.md)
- [Build a campaign page with AI](/build/ai-campaign-workflow.md)
- [Attribution in Jurni](/analytics-reporting/attribution-overview.md)
- [Read Meta ad account insights](/analytics-reporting/meta-ad-insights.md)