Lookup Tables¶
Overview¶
Lookup tables let Rose answer structured-coverage questions against your own data — the lists your team already maintains for sales and marketing. When a visitor mentions something covered by a table (an industry, a country, a plan tier, an integration), Rose matches it against the entries, knows whether it's "in scope" or "out of scope", and uses that verdict to ground its reply and decide whether to push the demo CTA.
Two things happen on every match:
- Voice — Rose answers using your canonical wording (e.g. the official industry name, the plan tier label) instead of paraphrasing.
- Qualification — entries flagged as out of scope block the demo CTA, even if the visitor later asks for one. Deliberate exclusions stay deliberate.
Example use cases¶
Common lookup tables clients run today:
| Table | What it does | Used by |
|---|---|---|
Sales territories (sales_territories) |
Maps a visitor's country to the account executive who owns that region. Used by the routing skill when handing off. | Lead routing, email handoff |
Pricing plans (pricing_plans) |
Source of truth for pricing answers given by the Website agent. Update here and the agent picks up the new tiers. | Website agent, pricing FAQ |
Industry → persona (industry_personas) |
Picks the right talk-track when the agent detects the visitor's industry. Sales engineering uses this to tailor the demo flow. | Website agent, demo flow |
Opt-out domains (opt_out_domains) |
Visitor email domains that should never be enrolled into nurturing. Compliance keeps this list. | Nurturing agent |
| Supported industries | Declares which sectors qualify for a demo and which are out of scope (e.g. Healthcare → covered, Gambling → uncovered). | Website agent, CTA gating |
| Country coverage | Tells the agent which countries you sell into. Out-of-scope countries get a polite "not yet available here" instead of the demo CTA. | Website agent, CTA gating |
| Integrations | The list of third-party tools you natively integrate with. Lets the agent answer "do you connect to X?" authoritatively. | Website agent |
| French CCNs (collective bargaining agreements) | Maps a visitor's industry to the IDCC code Rose should recognize, for payroll / HR products. | Website agent, qualification |
If your team already maintains a "supported X / not supported X" list in a spreadsheet, it's a candidate for a lookup table.
When a lookup table is the right tool¶
Three conditions:
- You have a structured list of entries with a clear in-scope / out-of-scope verdict per entry.
- Visitors will mention the topic in chat and expect a definitive answer.
- The list is long (>10 entries) or expected to change over time.
If all three hold, a lookup table is better than encoding the same information in a static FAQ — the matcher catches mentions even when the visitor phrases things loosely, the verdict is authoritative, and you can update the data without changing any prompts.
What lookup tables are NOT¶
- Not a knowledge base. For long-form content (product pages, case studies, blog posts) use the knowledge base instead. Lookup tables are for short structured entries with a verdict.
- Not a landing-page registry. If you want the agent to surface a specific page when a topic comes up, that's curated content recommendation, not lookup.
- Not a substitute for qualification questions. Lookup feeds qualification when the visitor mentions a known entry; it doesn't replace the qualification questions Rose may ask.
Setup¶
Set up by your account manager
Lookup tables are configured by your Rose account manager. Send them the list (a spreadsheet works) along with the verdict per entry (covered / uncovered / etc.) and any aliases visitors might use. They'll import the table, wire it into the right agent, and confirm the verdict semantics with you before it goes live.
What your account manager needs from you to set up a table:
- The list of entries with their canonical names.
- For each entry, the verdict (e.g.
covered/uncovered, or your own categories). - Aliases — alternate phrasings visitors might use (e.g. "hospital", "clinic" → Healthcare).
- For each verdict, whether matching it should allow or block the demo CTA.
Updates work the same way — send the new spreadsheet and your account manager re-imports it. No code change, no widget redeploy.