What is a page playbook (page-aware AI chat)?

Every chat widget on the internet opens the same way: an empty box, and some version of "Hi! How can I help you today?"

It is a strange thing to do. The visitor has just spent two minutes reading a specific page. The site knows exactly which one. And then the conversation starts by asking them to explain themselves from scratch.

A page playbook is the fix: a small briefing attached to a page, so the agent arrives already knowing where it is.

Three parts, and only two are visible

Background — what the agent should know before the first message. This one is not shown to the visitor. It is the private note you would give a colleague before sending them into a meeting: this page is about our enterprise tier, the buyer is usually technical, we cannot quote custom pricing here.

An opening line — what the visitor actually sees.

Up to four suggested questions — the ones that page reliably raises, so someone who has not formed their question yet can just pick one.

How the right one gets chosen

You almost never wire this up page by page. A playbook can carry a URL pattern — /solutions/* — and any page matching it inherits that briefing. A static site needs no code changes at all; single-page apps that have no distinct URL per view can name a playbook explicitly instead.

Patterns are globs rather than regular expressions, deliberately. Asking a law firm's marketing manager to write a regex is a poor trade, and this pattern is matched against input from the open internet, where a badly written regex is a denial-of-service waiting to happen.

When nothing matches, a default playbook catches the rest — so no page ever falls back to the blank box.

Why this is the part people underestimate

It looks like a nicety. It is closer to the difference between a shop assistant who watched you walk to the returns desk and one who greets you at the door with no idea why you came in.

Concretely: the opener is the only sentence guaranteed to be read. A generic one converts a page visit into nothing. A specific one — "You're looking at Pro. Want me to work out where overage would start for your volume?" — converts it into a conversation about the thing they were already thinking about.

Where it sits among the other pieces

A playbook decides how the conversation opens. What happens next is the rest of the machinery: what it may answer from is the knowledge base, what procedures it can run are its Skills, and who it is while doing so is the soul. The playbook only ever supplies the situation.

Which is why the background field is worth more thought than the greeting. "This page is our enterprise tier; buyers here are usually technical; we cannot quote custom pricing in chat" changes every answer in the conversation, not just the first line.