Skip to content

Launch Safely

Going live is not just turning on a channel. For a first release, the real job is to launch the right version, with the right audience, under the right level of control.

For Consultation Desk, a safe launch usually has five parts:

  • publish the agent version you trust
  • choose the surface people will actually use
  • set the right audience access model
  • collect feedback from real conversations
  • expand only after the behavior is stable

Published web channel with live URL and running status

The launch loop

  1. Publish the agent version from Editor.
  2. Create or update the channel that exposes it.
  3. Set audience access for the current phase.
  4. Share the live surface with a controlled audience.
  5. Review real conversations and feedback in Histories.
  6. Tighten the behavior before you expand the rollout.

Publish the agent before the channel

If the channel opens but there is no usable agent behind it, go back to Editor and publish the agent version first. Agent publish and channel publish are separate actions.

Channels

Channel Best for What you manage
Web channel Stakeholder review, pilots, hosted chat Slug, web experience, access settings, live URL
Widget channel Chat inside your own website or product Widget settings, allowed origins, login mode, embed snippet
LINE channel Audiences who already chat in LINE Messaging API credentials, LIFF entry, email binding, bound agent
Slack channel Internal team workflows in Slack Slack credentials, installation, bound agent

Other launch surfaces

API Access is not a hosted channel. Use it when you want to connect Codeer to your own product or backend and manage the client experience yourself.

  • Start with a Web channel when you want the fastest hosted rollout.
  • Choose Widget when you already have your own website or product page and want the conversation to stay there.
  • Choose LINE instead when the real audience already lives in LINE and you want onboarding to happen inside LINE.
  • Add Slack if the team already works in Slack.
  • Use API Access when you are ready to own the client experience yourself.

In this section

Channels

Other launch work