Product overview
Navigic builds managed AI support agents for customer support and internal support, grounded in approved knowledge and served through reviewable channels.
The problem
Customer and internal support need approved knowledge, a known serving channel, and a review trail for issues that require a person.
Core value
Create a support agent, attach source material, publish a revision, bind it to Website Support, and review activity after visitors ask questions.
Attach reviewed product, pricing, policy, limitation, and handoff material before a support agent answers visitors.
Publish a versioned agent revision and bind it to Website Support so the public widget serves the intended agent.
Use channel activity and quality signals to inspect responses, knowledge use, errors, retries, and escalation paths.
Jobs it helps with
Navigic is for support work where product detail, policy boundaries, prior conversations, and escalation paths need to stay attached.
Serve website visitors with an agent grounded in the product, pricing, policies, limitations, and contact paths you approve.
Use the same knowledge-grounded model for internal support when the channel, source material, and escalation rules are clear.
Check configuration, publish a new revision, and bind that revision from Website Support before treating changes as live.
Keep account-specific, billing, refund, policy exception, and sensitive requests visible for a person to own.
Add the Website Support widget with one script tag after the support agent is published and the channel is serving it.
How it works
Start in Agent Studio with a focused agent that matches the channel and support scope.
Add support files and instructions that define what the agent may answer from and when it should hand off.
Publish a versioned revision and bind it from Website Support so the widget serves the intended agent.
Inspect channel activity, quality signals, and handoffs after test and production conversations.
Current product surface
Website Support is the public customer-support channel for the embedded website widget. Agent Studio is where teams create, check, publish, and maintain the support agent that channel serves.
Argo for Mac remains available for native research workflows, but the current public product story should begin with managed support agents.
Channels
The channel should make the serving agent, allowed origin, active revision, and escalation path visible before customers depend on it.
Embed the widget on approved origins after publishing the support-agent revision you want visitors to use.
Check channel activity, recent conversations, tool failures, and handoff events from the same managed workspace.
Use internal or team-facing support channels when the knowledge, access rules, and escalation ownership are explicit.
Begin
Create the support agent, add approved knowledge, publish the revision, bind Website Support, and verify the widget with real support questions before broader rollout.