Docs/Channels/Sharing Channels

Sharing Channels

Share feedback forms with your users

Once you've created a channel, you can share it with your users so they can start submitting feedback. Each channel has a unique URL that serves a branded feedback form.

Channel URL format

Every channel has a public URL in this format:

https://yourapp.com/c/{workspace-slug}/{channel-slug}

For example, if your workspace slug is acme-corp and your channel slug is bug-reports, the URL would be:

https://yourapp.com/c/acme-corp/bug-reports

How to share

There are several ways to share your feedback channel:

  • Direct link — Copy the URL and share it via email, chat, or documentation
  • In-app link — Add a "Give Feedback" button in your product that opens the channel URL
  • Support page — Link to your feedback channels from your support or help center
  • Slack or Teams — Pin the link in a channel where your users or team collaborate

What submitters see

When someone visits your channel URL, they'll see a branded feedback form with:

  • Your workspace logo and name
  • Your brand accent color applied to buttons and highlights
  • A form to enter their name and email
  • Category selection (if the channel has multiple categories enabled)
  • The dark or light theme configured for the channel

After entering their details, the AI assistant begins a conversation to gather feedback. The conversation is streamed in real-time for a natural chat experience.

Private channels

If your channel visibility is set to private, visitors will be asked to enter an access code before they can proceed to the feedback form. You set this access code in the channel settings and share it separately with authorized users.

Note
The access code is a simple passphrase — it's not tied to user accounts. Anyone with the code can submit feedback. For team-internal channels, this provides a lightweight access control mechanism.

Paused channels

If a channel is paused, visitors will see a message indicating that feedback is not currently being accepted. This is useful when you need to temporarily stop collecting feedback — for example, during a major release or when your team is at capacity.