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:

  • Hosted link — Copy the /c/ URL and share it via email, chat, or documentation
  • Embed widget — Paste the JS snippet from the channel's settings into your site. It adds a floating feedback button that opens the intake form in an overlay — no redirect required.
  • Public portal — Share the /portal/ URL for a read-only view of submitted issues, so your users can track the status of their feedback.
  • Support page or docs — Link to your feedback channel from your help center or release notes
  • 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
  • A form to enter their name and email
  • Category selection (if the channel has multiple categories configured)
  • 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, access is controlled via the link itself. The access code is passed as a ?code= URL parameter — share the full link with authorized users and they go straight to the form. Visitors who arrive without a valid code see a closed-access message and cannot proceed.

Note
Because access is encoded in the URL, there's no code-entry form to fill out. For team-internal channels, this provides a lightweight access control mechanism without requiring user accounts.

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.