Orderverse DocsAI Assistant Overview
Understand how the AI assistant works across the dashboard and order portal — what it can do, how to enable it, and how it routes requests.
What is the AI Assistant?
Orderverse includes a built-in AI assistant powered by Groq. It operates in two contexts:
| Context | Who uses it | Access point |
|---|---|---|
| Dashboard AI | Suppliers (you) | Floating button → right-side panel |
| Portal AI | Your customers | Floating button → chat overlay on the order page |
The two contexts are independent — each has its own system prompt, tool set, and data access scope.
Dashboard AI
Available on every dashboard page. Opens as a side panel without leaving your current screen.
What it can do:
- Answer questions about Orderverse using the built-in documentation
- Search your orders, customers, and products
- Create a manual order on your behalf (with a confirmation step)
- Parse pasted messenger or email text into a structured order draft (Sales Rep page)
See Dashboard AI for full details.
Portal AI
Available on the customer order portal. Opens as a chat overlay in the bottom-right corner.
What it can do:
- Find products by name, category, or description
- Add products to the customer's cart
- Repeat a previous order with changes ("same as last order but remove X")
- Check order status
- Answer questions about shipping, returns, or policies
- Learn and remember workspace-specific product nicknames (aliases)
See Portal AI for full details.
How to enable
Both AI features are enabled by default when a GROQ_API_KEY is configured in the environment.
Per-workspace toggles are available in Configuration → AI → Settings:
| Toggle | Effect |
|---|---|
| Dashboard AI | Shows or hides the AI panel for dashboard users |
| Portal AI | Shows or hides the AI button on the order portal |
| Alias Learning | Allows portal customers to save new product aliases via chat |
| Knowledge Base | Injects your workspace Knowledge Base into AI responses |
These toggles persist per workspace. Changes take effect immediately without a redeploy.
Model architecture
The assistant uses a two-tier routing strategy to manage API usage efficiently:
| Tier | Model | Role |
|---|---|---|
| Main | llama-4-scout-17b-16e-instruct | Tool calls, docs Q&A, multi-step reasoning |
| Fast | llama-3.1-8b-instant | Simple greetings and straightforward queries (answered directly, no second call) |
Simple requests are completed in one API call by the fast model. Complex requests are handed off to the main model for tool execution and reasoning.
Data access and security
Dashboard AI authenticates using your existing session token and only accesses data within your workspace. Write operations (order creation) require a confirmation step before execution.
Portal AI operates within the public order portal context. It can only read products, pricing, and policies that are already visible to the customer. Cart modifications happen client-side — the AI cannot submit orders without the customer reviewing and confirming.