Keep these design considerations in mind when you set up multisite quoting headlessly with AI tools.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
- Setup state can be hard to read across all connections, so the agent sometimes needs node-by-node fallback checks to confirm the baseline.
- Some setup-node transitions have a manual UI dependency.
- Role-to-permission mapping can differ by org model.
- Sharing model complexity can require org-specific tuning.
- Decision table template quality or version mismatch can break downstream flow logic.
- Misaligned context binding is a common at run time blocker.
- Layout and flow routing is typically manual and UI-heavy.
- There's no single consolidated view of the entire setup state, so end-state verification can span multiple setup nodes.
- Known issue: If the agent is blocked at the provisioning layer when running the multisite quoting recipe, run the preconfig recipe first. See the provisioning-block fallback prompt in Agentic Tips.
- Out of scope for this setup path: Experience Cloud external user rollout hardening, advanced channel orchestration, and unrelated Sales for Energy & Utilities features.