Channels & embed
Channels & embed puts Harriet in front of people who never open the console: visitors on your website and members of public chat channels. The same skills you approve for Endpoint AI answer there, scoped to what each surface should know.
What lives in Channels & embed
Open Channels & embed in the console. Its sidebar carries the subtitle "Website widget & public channels" and has these sections:
| Section | What it does |
|---|---|
| Surfaces | The list of every place Harriet appears publicly. Add a website widget or register a public channel id, then open a row to configure skills, instructions, and knowledge scope. |
| Embed documentation | Copy-paste install snippets for the website widget, with your real customer id filled in, plus signing examples for Python, Node.js, and Salesforce Apex. |
| Credentials | The embed signing secret your server uses to sign widget requests. Generate, reveal, copy, and rotate it here. |
| Browser origins | The allowlist of hostnames permitted to load the widget in a browser. Shown when the public widget feature is enabled for your organization. |
| Embed export | Download public widget users and conversation statistics as Excel. Shown to people who can export data. |
Same skills, a different audience
Endpoint AI provisions skills to your employees' enrolled devices. Channels & embed reuses those same skills for a different audience: website visitors and channel members who are not signed into Harriet. Because these people are outside your organization's trust boundary, each surface gets its own scope instead of the full employee experience.
Two controls define that scope. Which documents Harriet can use on a surface is driven by the specialist channel lists on your user groups, including public-… entries that tie a widget to a knowledge scope. Which skills are on or off in a given context is controlled in Skills → Channel assignments, and per surface from the Surfaces list. This lets a "Billing" widget draw only on billing documents while a general entry point stays broader.
Escalation to a human inbox
Sometimes a conversation should become work for a person. Each website widget has Escalation groups: only groups with Ticket inbox enabled can be selected, and conversations the visitor escalates land as tickets in those groups' inboxes. Conversations in connected Slack, Teams, or Google Chat channels can escalate into the same ticket system your team already uses, and where your organization has connected them, work can flow into tools such as Jira or Salesforce.
Configure each surface
Embed Harriet chat on your site: install the script, pick which skills answer, and style the panel.
Register Slack, Teams, or Google Chat channels so Harriet answers with the right context in each one.
The signing secret, HMAC-signed embeds, the browser origin allowlist, and rotation.
Chat apps need one extra step outside Harriet: the Harriet app must be a member of the Slack channel, Teams channel, or Google Chat space where it should work. Configuration in Harriet alone is not enough. See Public channels for the per-platform steps.