Vocabulary

Vocabulary is a list of phrases — your business's jargon, product names, shorthand — mapped to where they live on your site. It overrides fuzzy matching, so when a visitor says "show me the Pro plan" Friday goes straight to /pricing#pro instead of guessing.

When you need it

• You use internal terms that don't appear on the page heading ("the dashboard" when the page is titled "Console").
• Two pages have nearly identical text and Friday picks the wrong one.
• You have a CTA the visitor commonly asks for by name ("book a demo", "talk to sales").
• You sell things with names a language model wouldn't know (a SKU, a product family).

How it works

When Friday is deciding what to do for a visitor message, she runs the message against vocabulary first. If any phrase matches (case-insensitive, whole word), the corresponding target gets a strong boost over anything the scanner found. Vocabulary entries beat fuzzy matches but don't override Deny action rules — your action policy still has the final say.

Setting it up

1. Open Dashboard → Vocabulary.
2. Click Add term.
3. Fill in:
   • Phrases — comma-separated. Add the variations visitors might say.
   • Target — a URL (relative or absolute), or a CSS selector if the target is a button on the current page.
   • Action — what Friday should do when matched. Usually navigate or click.
4. Save. Changes apply to the next page load — no redeploy.

Examples

• "pricing", "plans", "how much" → /pricing (navigate).
• "book a demo", "talk to sales" → a[data-cta="demo"] (click).
• "refund", "money back" → /help/refunds (navigate).

Tips

• Keep phrases short — 1 to 3 words. Long phrases rarely match what visitors actually type.
• Add the obvious typo / shorthand. "pricing", "price", "prices".
• If two entries could match the same message, the longer phrase wins.
• Review the audit log monthly to see which messages Friday didn't have a vocabulary entry for — that's your shortlist.