Bring assistance, navigation and page actions into one conversation. Give authorized agents structured application knowledge, and give product owners control over the path to a verified result.
Prototype Implemented in the current prototype; validate it in your application.
Integration required Requires app knowledge, published workflows, permissions or an adapter.
Roadmap Planned work; not a currently delivered capability.
PEOPLE
One conversation for your users
Ask, understand, navigate and request an action without switching between separate assistant tabs.
Prototype
Customer SDK packages and recorded analytics
The platform owner assigns a different feature list to each company or application.
Details and setup
Assist, Operate, Connected and custom packages control SDK APIs and refresh open widgets.
Site admins see recorded browser IDs, sessions, agent-labelled runs, heatmaps, navigation flow and presence for owned applications.
Browser sessions are not proof of human identity; agent labels are not independently verified provider identities.
Prototype
Unified chat workspace
One chat-style interface combines assistance, navigation, workflow guidance and page-agent commands.
Details and setup
A shared message history and composer keep questions and results together.
Automatic routing selects the appropriate help engine from the request.
Workflow, recording, form-fill and element-search tools are available inside the same panel.
Prototype
Expressive floating companion
Choose a bot appearance that reacts to activity and validation.
Details and setup
Site admins select each application’s default in Bot Appearance, create animated bots in the portal studio, preview expressions, import/export Avatar Lab definitions and control visitor choice.
Typing, search, listening and validation expressions update locally without model calls. Optional contextual tips request an explanation only after a visitor clicks Explain this. App-only results use a documented success/error event.
Drag or use arrow keys to move the launcher; reduced motion and browser-local appearance preferences are supported.
The separately licensed AGPL renderer ships with notices and downloadable corresponding source.
Prototype
Voice input, replies and restart
Speak the same requests you can type, optionally hear replies, and start a fresh conversation.
Details and setup
Microphone input requires browser speech-recognition support and permission; text remains available when speech is unsupported or fails.
Voice transcripts use the same routing and page-action review as typed messages.
Use Restart or say ‘restart Smart365Guide’ to stop listening and pending guidance. Completed changes, saved workflows and account permissions are preserved.
Integration required
Explain the current page
Help people understand controls, terminology and the page they are working on.
Details and setup
Use supplied product knowledge and observed page structure for contextual answers.
Show explanations alongside the user's conversation.
Answer quality depends on the knowledge, metadata and model configuration supplied by the owner.
Integration required
Navigate to a known destination
Turn ‘take me to settings’ into a destination or sequence of navigation steps.
Details and setup
Use known routes and recorded transitions to find a destination.
Show the proposed destination or steps for review and continuation.
Navigation does not bypass sign-in or host application permissions.
Integration required
Guided workflow playback
Follow published workflows with highlights, instructions and step controls.
Details and setup
Pick a saved workflow or ask for guidance in the shared chat.
Highlight relevant controls and move through recorded steps with the user.
The owner maintains workflows as routes, selectors and business rules change.
Integration required
Reviewed page actions and form help
Request a page command, review it, then run it in the current browser session.
Details and setup
Page commands require a Run page command click. Cancelling leaves the command unexecuted.
Form tools discover fields, propose values and let the user review and apply them.
Host backends remain responsible for authorization. Browser confirmation does not replace server permissions or prove a saved business outcome.
AI AGENTS
Structured context for authorized agents
Give compatible agents relevant application knowledge and typed business actions through an MCP or custom adapter.
Prototype
Private agent information exchange
Registered agents exchange information through contracts approved by both companies.
Details and setup
Company admins register application-bound agents, publish typed input/output fields and approve private sharing invitations.
A server SDK and separate MCP endpoint support a bounded request/reply inbox. Your provider worker supplies real information and enforces record-level access.
Exchange-only credentials, encrypted expiring payloads, request budgets, revocation and scoped metadata audits are enforced. Responses are untrusted data, not independently verified facts.
Integration required
Application guide and action manifest
Describe your app and its published action references in a structured guide.
Details and setup
Register the application's name, version and approved action references through the SDK.
The adapter resolves references to current authorized contracts.
The guide supplies knowledge; it does not grant execution permission.
Integration required
Bounded, fresh context
Supply selected context instead of repeatedly making an agent rediscover the application.
Details and setup
The host provides fresh context through a callback within the guide's size limits.
Include relevant entity references, field information and choices the user may see.
Dynamic dropdown values and role-dependent data require host updates; the SDK does not automatically know every backend record.
Integration required
Typed actions and required inputs
Expose precise input schemas, descriptions and policies for published capabilities.
Details and setup
Define required fields and expected outcomes for each business action.
SDK helpers expose app-listed actions that have an authorized server contract.
Compact responses keep unnecessary diagnostics outside normal agent context.
Integration required
REST and MCP provider connections
Connect a product backend to the capability gateway with scoped provider access.
Details and setup
Configure a supported REST or MCP provider and publish bounded capabilities.
Agent-side adapters translate the licensed guide into tool calls.
Keep delegated credentials in the server or adapter. A public browser license is not an agent execution credential.
Integration required
Retry protection and result verification
Avoid duplicate writes and check saved business outcomes through the gateway.
Details and setup
Execution uses request identifiers and input-bound idempotency checks.
Published verification rules read back saved provider state independently of an agent's claim.
Verification may fail or remain uncertain. A chat success message alone is not proof of completion.
Integration required
Compatible model clients
Connect compatible tool-calling agents through MCP or custom adapters.
Details and setup
Codex is the tested reference integration and benchmarked client.
Claude, ChatGPT and local model clients need compatible tooling, adapter configuration and their own validation.
Compatibility does not imply identical performance or automatic support for every client.
PRODUCT TEAMS
Application knowledge and workflow building
Build your guide from observed structure, curated knowledge and workflows your team reviews.
Prototype
Site graph foundations
Connect known routes, page elements, forms and observed transitions in an application graph.
Details and setup
Ingest licensed page snapshots and structural metadata.
Store route and element relationships that support navigation and explanations.
