Tutorials
Use this curated map to find the right docs for support-agent launch, approved knowledge, website channels, visitor identity, escalation, and quality review.
Start here
Use the full docs path to create a support-focused agent, attach reviewed knowledge, deploy Website Support, and verify the first visitor conversation.
A public website support channel has a published agent, approved knowledge, an embed key, allowed origins, and a reviewed test conversation.
Open guideFind the docs guidance for turning product answers, policies, contact paths, limitations, and escalation rules into concise agent knowledge.
The agent has a small, current source set and clear instructions for unsupported, sensitive, or account-specific requests.
Open guideDocs-backed path / Website Support / 25 min
This resource page helps evaluators choose a path. The detailed implementation steps stay in docs, where the launch guide covers the pieces that make a first support agent safe to try.
Open the launch guideBy workflow
Scan the support-agent map, then jump into the docs guide or outline that matches the launch, review, or improvement job in front of you.
Use the full docs path to create a support-focused agent, attach reviewed knowledge, deploy Website Support, and verify the first visitor conversation.
A public website support channel has a published agent, approved knowledge, an embed key, allowed origins, and a reviewed test conversation.
Find the docs guidance for turning product answers, policies, contact paths, limitations, and escalation rules into concise agent knowledge.
The agent has a small, current source set and clear instructions for unsupported, sensitive, or account-specific requests.
Open the channel docs for assigning a published agent to Website Support, creating an embed key, restricting origins, and installing the script.
Visitors can reach the support agent from an authorized site without exposing secret keys or internal-only context.
Review the identity docs when the widget should recognize signed-in users while keeping the secret key on your server.
Known visitors can keep conversation continuity across sessions without putting verification secrets in browser code.
Read the review guidance for deciding when the agent should answer, ask a clarifying question, stop, or route to a teammate.
Refunds, billing disputes, security questions, low-confidence answers, and customer commitments have visible human review paths.
Use activity docs to inspect which agent version served each response and which failed conversations should update knowledge.
The team has a review rhythm for incorrect answers, missing articles, escalation misses, and expansion readiness.
Use this preview outline to scope an internal-support agent for IT, operations, or HR questions before Slack rollout is enabled for a workspace.
Internal knowledge, employee-facing boundaries, approval points, and escalation owners are defined before the agent enters a team channel.
Tutorial standard
A production support agent is more than a chat box. Each path should lead to docs that name the scope, source knowledge, channel, human review point, and signal that tells the team what to improve next.