Skip to content

Share for Feedback

Once the first version works in Live Test, start a small controlled rollout. The practical sequence is: publish the Agent version, create and publish the Web channel, open the web client yourself, then ask a few stakeholders to try it and leave feedback on exact replies.

Step 1: Publish the Agent Version First

The channel and the Agent version are published separately. Before you create or share the channel, go to Edit Agents, open Consultation Desk, and click Publish in the Agent Editor.

After the version is live, the button changes to Unpublish. That is the signal that the web client can actually load the Agent.

Consultation Desk after the Agent version has been published in the editor

If the web client says No agents available

The channel is live, but the Agent version is not. Return to Edit Agents, publish the current version, then refresh the published URL.

If you change the Agent later, click Publish again so the web client uses the updated version.

Step 2: Create a Web Channel

  1. Open the Channels tab in your workspace.
  2. Click New Channel.
  3. Create a channel for Consultation Desk.

Channels empty state in the current workspace UI

Step 3: Choose a Clear Slug

When you create the channel, fill in:

  • Name: Consultation Desk
  • Slug: Something simple, such as consultation-desk
  • Type: Web Application

Use Auto-fill from name if you want a starting point. The published URL uses this slug, so choose one you are comfortable sharing.

Create New Channel dialog with name, slug, and type filled in

Step 4: Publish the Channel

After the channel is created:

  1. Open the channel details.
  2. Review the Overview tab and confirm the slug-based URL.
  3. Click Publish.
  4. Copy the published URL and keep it ready for testers.

Publish Status showing the live URL for the channel

Step 5: Open the Web Client Once Yourself

Before you send the link to anyone else:

  1. Open the published URL.
  2. Confirm you can see the Agent name, description, and chat box.
  3. Send one simple message to make sure the public experience is actually working.

This is the exact view your stakeholders should see when the setup is correct.

Published Consultation Desk web client responding to a first test question

Step 6: Ask Stakeholders to Try It and Leave Feedback

Ask 3 or 4 stakeholders to try the same pilot flow from different angles:

  • One normal customer question
  • One vague question that requires clarification
  • One risky or unrealistic question
  • Feedback whenever a specific reply feels unclear, generic, overconfident, or incomplete

When a reply feels wrong, ask stakeholders to click Improve on that exact response and say what felt off in plain language. They do not need to diagnose the root cause. A short note like Too generic. Offer human callback earlier. is enough for the operator and Copilot to work from.

Stakeholder feedback being left directly on a reply in the published web client

This first round should stay small and controlled. Start with a few key stakeholders, not a broad release.

What Good External Feedback Looks Like

The most useful stakeholder comments usually answer one of these questions:

  • Which exact reply felt wrong?
  • Should the Agent ask a different question, hand off sooner, or sound less generic?
  • Did it imply anything your team has not approved?
  • From the stakeholder's point of view, what would a better answer have done instead?

Controlled Rollout Later

For this first pilot, keep the audience small. If you later need tighter access control, use Audience Access and whitelist mode.

Optional Upgrade: Request Form

If the Consultation Desk should collect structured intake or booking details inside the conversation, add a Request Form. Keep it out of the first pass unless structured data is part of the core workflow.

Advanced Publishing

If you need to call the Agent from your own product or backend, use API Access. For a first pilot, start with Channels.

Next Steps