Select the GitHub documents your support agent can use.
Import selected .md, .mdx and .txt files. Public documents work without a GitHub token; private repositories require a server-side token and a workspace-specific allowlist. Imported content needs review and approval, including after every sync.
Add a separate widget for support or sales.
The generated script opens a browser voice widget on an allowed website origin. Choose the channel, label and settings for the page where it appears. Provider credentials remain on the server and are not included in the embed.
Let trusted agents maintain the workspace.
The authenticated MCP endpoint and REST API expose knowledge, agent settings, conversation records and installation details. Workspace-scoped tokens let your own tools carry out management work against the same records as the dashboard.
These tokens grant management access. Give them only to trusted tools and revoke them when access is no longer needed. Adding a source and approving it are separate operations.
Configure a human phone destination for handoff.
The optional Twilio handoff flow connects a browser caller to a configured team number after a private briefing. Support and sales can use different destinations. The human handoff page explains the flow and its current verification status.
Common questions
Can I import my whole website?
Website URL imports are disabled in the current Node deployment. Add website content as manual sales notes and review it before approval.
Are there ready-made help desk or CRM connectors?
The current integration set is website embeds, GitHub support documents, REST, MCP and optional Twilio phone handoff. A help desk or CRM connection would need separate integration work.