Page rules

By default the assistant behaves the same everywhere on your site. A page rule changes that for pages whose web address matches a pattern you write — so you can turn chat off during checkout, show different suggestions on your pricing page, or stop the assistant taking actions on your admin screens.

What a rule can change

A rule changes only the things you switch on. Everything else keeps following your workspace settings.

• Availability — whether chat is shown, hidden, disabled, or replies with a notice you write.
• Acting on the page — whether the assistant may click and fill things in for the visitor.
• Suggestions — the starter chips shown when chat opens.
• The look — the base colours, corner rounding and font from one of your Design Studio designs.
• Voice — a different assistant voice, chosen from the profiles on your Prompts page.
• Blocked actions — specific things the assistant must not do on these pages. This can only take actions away; a page rule can never grant one.

Choosing which pages it applies to

Pick how the address should be compared, then write the address. The editor has a tester: paste a real address and it tells you whether the rule would apply, using the same matching your live site runs.

• Is exactly — that one page, and nothing beneath it.
• Starts with — the page and everything under it. /checkout covers /checkout/cart but not /checkout-express.
• Contains — the text appears anywhere in the address.
• Matches a pattern — advanced. Use * for any run of characters. Unlike the other three, this one IS case-sensitive and DOES include anything after a ?.

The first three options ignore capital letters, ignore anything after a ?, and treat a trailing / as the same page — so /Pricing, /pricing/ and /pricing?utm_source=ads all match a rule written as /pricing. You can change either of those with More matching options.

When more than one rule applies

Rules combine. Each thing a rule can change is decided separately by the highest-priority rule that says anything about it — so “highest priority wins” is true for each behaviour, not for the whole rule.

For example: a rule on /checkout/* at priority 100 hides chat, and a rule on /checkout/cart at priority 200 only changes the colours. On the cart page the visitor gets the new colours AND chat stays hidden — the cosmetic rule does not cancel the safety one, even though it has the higher priority.

Blocked actions are the one exception, and they are stricter: every matching rule's blocks apply together. A narrower rule can never re-allow something a broader rule blocked.

Three things people set up first

• Quiet during checkout — hide chat on /checkout so nothing interrupts a payment.
• Read-only on admin pages — let the assistant answer questions on /admin but not click anything.
• Pricing suggestions — show your own starter questions on /pricing.

Worth knowing

• Changes reach visitors within about five minutes. Config is cached at the edge, so a save is not instant.
• On sites that switch pages without reloading, rules re-apply as the visitor moves between pages — the assistant follows the route change. A router that changes the address in an unusual way may not be detected; a full page load always applies the right rule.
• Your address patterns are sent to every browser that loads your site, so the assistant can tell which page it is on. Don't put anything secret in one — an unreleased product path in a pattern is readable by anyone who looks.
• Voice and blocked actions are decided on our servers, which only see the page's path — not the full address, and not anything after a ?. A rule written as a full address (https://yoursite.com/checkout) will not change the voice or block actions; write it as a path (/checkout) instead. The editor warns you when a rule has this problem.
• Up to 200 rules per workspace. There is also a size limit on the rules as a whole, since they are sent to every visitor — the ones carrying a custom look or their own suggestions are the largest.