Domain Groups & Auto Domain Selection

WisdomAI organizes context into domains, so that a question about billing draws only on billing tables and billing definitions, and a question about product usage draws only on product tables and product definitions. That isolation is deliberate: it’s what makes each domain’s answers precise, scoped to the right business area, and correctly permissioned. Some questions, however, legitimately span more than one domain: “Is churn related to a drop in product engagement?” needs a retention domain and a product-usage domain at once. Two features let WisdomAI answer those questions without abandoning domain isolation:

• Auto Domain Selection, which routes a question to the right domain automatically at runtime.
• Domain Groups, which let an admin pre-declare that specific domains are related.

This page covers:

• Why it matters: The two distinct problems cross-domain questions raise
• Auto Domain Selection: What it is, and when to use it
• Domain Groups: What it is, and when to use it
• An FAQ comparing the two features directly

​

Why it matters

Domain isolation is what makes a domain trustworthy, an answer is grounded in that domain’s own metric definitions, synonyms, and entities, not assembled from whatever else happens to be in the workspace. But it also means a domain’s own context describes its data, not how its metrics relate to another domain’s. Cross-domain questions surface two distinct problems:

1. Routing: Given a question, which domain(s) should answer it? This is open-ended: the right domain depends on the question, and a large workspace may have dozens of candidates. Auto Domain Selection addresses this.
2. Relationships: Once two or more domains are known to be asked about together, how do their metrics and entities line up? Domain Groups address this by giving admins a place to document shared definitions and cross-domain logic once, at the group level, instead of duplicating them into every domain that needs them. Approved cross-domain queries are saved to the group’s own reviewed-query library for the same reason, a query spanning domains only makes sense in that combined context.

​

Auto Domain Selection

Auto mode reads the current question and conversation, then routes it to the most relevant domain or group automatically, without you selecting one first. Nothing is declared in advance. WisdomAI considers any domain it’s permitted to see and picks at runtime. Use it when:

• You work across many domains and don’t always know which to pick
• Questions shift topics mid-conversation
• You’re exploring data without a specific domain in mind

Because the candidate set isn’t fixed ahead of time, routing accuracy naturally degrades as the domain catalog grows, this is the tradeoff of an unbounded approach.

​

Domain Groups

A domain group combines two or more domains into a single unit. Selecting a group in chat gives WisdomAI access to all tables from every domain in the group, reasoned over together with the group’s own shared context layer. An admin who already knows that two domains are frequently asked about together, churn and retention, say, or CRM and billing, declares that relationship as a group ahead of time. Restricting the candidate set to only those domains increases the likelihood that the LLM stays inside the right context, compared to reasoning across the entire workspace. Example groups:

​

FAQ

​

Tips

• Name groups by business question, not by system. “Revenue 360” is more useful than “Salesforce + Stripe.”
• Auto mode routes better when domains have clear names and descriptions, since WisdomAI uses domain metadata to route questions.
• If Auto mode consistently reaches across the same two domains, create a group for them. A recurring cross-domain pattern is a relationship worth bounding explicitly rather than re-solving at runtime.
• Groups and Auto mode work together. When Auto mode is on, WisdomAI can select a domain group, not just individual domains.

​

Next steps