> For the complete documentation index, see [llms.txt](https://shoppad.gitbook.io/yedric/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shoppad.gitbook.io/yedric/getting-started/page-prompts.md).
# Page Prompts
Page Prompts let you control how the assistant behaves on different pages of your app. Instead of showing the same suggested prompts everywhere, you can tailor what users see (and even change the assistant's instructions entirely) based on where they are.
***
## What is a page prompt?
A page prompt connects a page in your app to a custom set of suggestions and, optionally, a set of instructions that override your assistant's default system prompt for that page. When a user opens the Yedric assistant, it checks the current page URL against your page prompts and applies the first one that matches.
This means a user on your dashboard can see setup-focused suggestions, while a user on an orders page sees prompts about recent shipments, without any extra work from the user.
***
## How page prompts work
When the assistant loads, it checks your page prompts and applies the first one whose URL pattern matches the current page.
A page prompt with a blank URL pattern works as a catch-all. It matches any page that is not covered by a more specific page prompt, so it is a good place for your general-purpose suggestions.
A simple way to set this up:
* Create specific page prompts for the pages where tailored behavior matters most
* Create one with a blank URL pattern to cover everything else
Page prompts are evaluated top-to-bottom and the first match wins. You can reorder them in the UI by dragging.
***
## Creating a page prompt
Inside your assistant, click the **Page Prompts** tab, then click **New Page Prompt**.
Select New page prompt to build new prompts across your site pages.
Each page prompt has the following parts.
Add details for your new page prompts, including quick-start options.
**URL Pattern** Enter a portion of the URL for the page you want this page prompt to apply to. For example, if your orders page is at `yourapp.com/orders`, you could enter `/orders`. Leave this blank to create a catch-all.
By default, patterns use simple glob matching, so `*/orders` matches any URL ending in `/orders` regardless of the domain. If you need more precise control, toggle **Advanced** to switch to regular expression (regex) mode, which allows for more complex pattern matching. This is typically only needed for developers.
**Custom Instructions** Optionally write a system prompt that replaces your assistant's default instructions when a user is on this page. Leave it blank to use the default instructions everywhere.
**Suggestions** Add one or more suggested prompts for this page prompt. Each suggestion has two fields:
* **Label**: the short text shown on the button your user clicks
* **Prompt**: the message that gets sent to the assistant when they click it
Keep labels short and easy to scan. Write prompts the way a user would naturally ask the question.
**Available Tools** Optionally restrict which MCP servers are active on this page. This is useful if certain tools are only relevant in specific parts of your app.
Click **Save** when you are done.
***
## Showing page prompts beside the closed launcher
Page prompts normally appear inside the chat panel once a user opens it. You can also show them before that: on the [Widget](/yedric/getting-started/widget.md) tab, under **Configure**, set **Default state** to Closed and check **Show Page prompts when beacon is closed**. The current page's suggestions then appear as clickable bubbles next to the closed launcher, and clicking one opens the chat and sends that prompt.
The bubbles use each suggestion's **Label**, and at most four bubbles show at once, so put the suggestions you most want seen first. The optional **Prompt suggestion** field on the same card adds a message of your own above them. Visitors can dismiss the bubbles, and they come back after an hour.
***
## Example
Here is what a simple page prompt setup might look like for an e-commerce app:
**Page Prompt 1: Orders page**
* URL pattern: `/orders`
* Suggestions:
* Label: `Find a recent order` / Prompt: `Show me my most recent orders`
* Label: `Check fulfillment status` / Prompt: `What is the fulfillment status of my open orders?`
**Page Prompt 2: Default (catch-all)**
* URL pattern: *(blank)*
* Suggestions:
* Label: `How do I get started?` / Prompt: `Walk me through the basic setup`
* Label: `What can you help with?` / Prompt: `What are the most common things people ask you?`
***
## Tips
Start with a few high-value suggestions per page prompt rather than trying to cover every possible question. You can expand them once you see what users are actually asking.
Use the Conversations tab to review real interactions and spot questions that would make good suggestions on specific pages.
