Copilot

Copilot lets you deploy Scout chat experiences on your website or in your app with an embeddable widget.

If you want to put an agent in front of customers, prospects or internal teams, Copilot is the standard way to do it.

Deploy an Agent with Copilot

To deploy an agent from Scout Studio:

1. Open the agent you want to publish
2. Go to Settings and open Deployments
3. Create a new Copilot deployment
4. Configure the widget settings for that deployment
5. Copy the generated embed snippet and add it to your site

Each deployment has its own settings and embed snippet.

Examples:

• A marketing-site copilot for product questions
• A support copilot for logged-in customers
• An internal copilot for sales or success teams

How Agent Revisions Work

Copilot deployments use the agent’s active revision.

• Updating and promoting your agent can change how the Copilot behaves
• You do not need to replace the embed snippet when the active revision changes
• Your website experience should be tested after important agent changes

Public Deployment Checklist

Before you embed an agent on a public site, review what the agent can do.

Review Integrations and Tools

Anything enabled on the agent may become reachable through a public-facing chat experience.

Check for:

• CRM or ticketing tools that can read or mutate customer data
• Email, Slack or messaging tools that can send outbound messages
• Internal knowledge sources that should not be exposed broadly
• Code execution, web access or other broad capabilities that need tighter instructions
• Tools that trigger side effects in downstream systems

Tighten Instructions

Public copilots need stricter instructions than internal agents.

Good practices:

• Tell the agent what kinds of requests it should refuse
• Limit when it should call tools versus answer directly
• Require explicit confirmation before high-impact actions
• Instruct it to avoid revealing sensitive internal information
• Keep responses concise and user-facing

Decide Where the Copilot Lives

Different placements usually need different deployments.

For example:

• Public homepage copilot
• Authenticated in-app assistant
• Customer support portal copilot
• Internal-only knowledge assistant

Using separate deployments makes it easier to tailor messaging, behavior and rollout strategy for each surface.

Configuration

After you create a deployment, Scout generates a deployment-specific embed snippet. Copy it from Studio and place it where you want the widget to appear.

Example: Enable TTS

<scout-copilot
  copilot-id="your-copilot-id"
  tts-enabled="true"
></scout-copilot>

If you are using the snippet generated by Studio, add tts-enabled="true" to enable spoken playback for assistant responses.

Multiple Deployments for One Agent

Agents can have more than one Copilot deployment. This is useful when you want to vary:

• Welcome messaging
• Branding or presentation
• Embedded location
• Operational rollout across environments or teams

Treat each deployment as a separate channel into the same agent.

Text-to-Speech (TTS)

Copilot supports reading assistant messages aloud for accessibility. When enabled, a speaker icon appears next to each assistant message.

How It Works

• Per-message control: Click the speaker icon on any assistant message to hear it read aloud
• One at a time: Starting a new message stops any currently playing message
• Locale-aware: Voice automatically matches your Copilot’s configured locale
• Keyboard accessible: Tab to the control and press Enter to play or stop

Browser Support

TTS uses the browser’s Web Speech API. Supported in:

• Chrome 33+
• Safari 7+
• Edge 14+
• Firefox 49+

If TTS is enabled but the browser does not support it, the speaker control appears disabled with an accessible message.

Privacy

TTS runs entirely client-side. Message content is not sent to any third party for speech synthesis.

Next Steps

• Getting Started with Agents — Build and test your first agent
• Integrations — Review connected systems before public deployment
• Code Execution — Understand higher-risk capabilities before public deployment

Updated: March 2026 | PRO-6767