Admin Reference
AI Assistant Route Reference
Understand the route-aware office copilot, conversation context, and how assistant launches preserve the current admin desk state.
Before you start
- AI Assistant is enabled for the workspace and you need route-aware help rather than freeform chat alone.
Expected outcome
You can launch or reopen the assistant with useful context instead of losing your current scheduling, CRM, or review slice.
What this route is for
AI Assistant is the route-aware office copilot workspace. It preserves the current admin desk context so admins can ask for help without rebuilding the planner, CRM, or record slice manually.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | ai-assistant |
| Visibility | Customer-facing only when AI Assistant capability is enabled. |
| Capability notes | The route understands many admin desks, but a platform-only AI operations workspace remains outside this public reference. |
| Direct inbound | Scheduling, CRM, sites, inspections, defects, quotes, work orders, assets, systems, and shell navigation when the route is exposed. |
Main regions, dialogs, and controls
| Surface | What it does |
|---|---|
| Conversation rail | Existing conversations and new-chat entry. |
| Transcript | Current assistant conversation. |
| Composer | Prompt entry and action confirmation area. |
| Context rail | Shows the entity or route slice passed into the assistant. |
| Delete confirmation | Removes a conversation when no longer needed. |
Key actions
- Start a new chat.
- Reopen an existing conversation.
- Launch the assistant from a route-aware context.
- Confirm assistant-driven actions where the workflow allows them.
- Delete conversations you no longer need.
Filters and URL state
| State group | Params |
|---|---|
| Conversation | conversationId, origin, draft |
| Entity context | entityType, entityId, selection |
| Planner slice | start, end, engineerId, siteId, jobType, status, q |
| Route context | pageId, pageTitle |
- The route is highly URL-aware because context preservation is the main product value.
- Different launching desks seed different subsets of these params.
Outputs and side effects
- Saves conversation history.
- Preserves and reuses route context for later prompts.
- Can open assistant-led actions or suggestions, but it does not become the owning desk for the original record.
Inbound links
- Scheduler guidance or ask-AI actions.
- CRM route-aware launches.
- Context-aware actions from sites, inspections, defects, quotes, work orders, assets, and systems.
Outbound links
- A platform-only AI operations link may appear in the header but is outside this customer-facing set.
- Most movement stays within the assistant route until the user decides to return to an owning desk.
Indirect handoffs
- AI Assistant helps the office reason across routes, but actual record changes still belong to the operational desks.
- Route context is only as good as the source desk’s current hash state and selected entity.
Troubleshooting
| Symptom | What to check |
|---|---|
| The assistant opens without the expected context | Re-check the launching route and the route-context params in the hash. |
| A conversation opens the wrong slice | Confirm conversationId and current context params were not mixed from an older launch. |
| The assistant can explain but not act | That usually means the owning record still lives in another desk or the workspace lacks the needed AI capability. |