Works with the help center and support tools you already have
Nuri reads your help center, hands visitors over to your own support tool when it can’t help, and tells your team in Slack. Each card says what it does and where it stops.
Help centers Nuri answers from
The four help-center connectors import article by article and re-sync every day: changed articles are re-read, removed ones leave the knowledge base.
Zendesk Guide
Imported article by article from your help center address, no token needed.
Public articles only, in the language of the address. Drafts and articles for signed-in users or agents are never imported.
Intercom
Imported from your public help center pages, or through the Articles API with an access token (US, EU or Australian workspace).
Published articles only.
Freshdesk
Imported through the solutions API with an agent API key.
Folders visible to all users only. Without a key, add the portal as a plain docs URL: it is crawled, and not re-synced daily.
Help Scout Docs
Imported through the Docs API with an API key.
Public collections only. Without a key, add the Docs site as a plain docs URL: it is crawled, and not re-synced daily.
Any docs site
A docs address or a sitemap is crawled; Markdown, text and HTML files or pasted text work too.
Crawled sources are read again when you click Sync now. The daily re-sync applies only to the four help-center connectors above.
API tokens are stored encrypted and never shown again. Only public help content is read; anything in the knowledge base may be quoted to any visitor. A source can be limited to some roles or plans (see role-scoped content). Help-center import isn’t on every plan: see pricing.
Support handoff
When Nuri can’t help, a Contact support button opens your own tool. The summary of what Nuri tried is built in the visitor’s browser and goes straight to that tool, not through us.
Intercom
Opens the messenger already on your page with the visitor’s goal, then a summary of what Nuri tried, as the first message.
The goal goes in as the visitor typed it, not masked (the summary is masked). The visitor can edit the message before sending.
Zendesk messaging
Opens the messenger already on your page.
The goal is not typed in. The summary reaches Zendesk only through a custom ticket field you name. Optional tags (wayhint, wayhint-failed…) only label how the guide ended.
Crisp
Opens the chatbox with the goal and the summary in the message box, plus a reference in the session data.
HubSpot chat
Opens the chat widget already on your page.
It opens without a prefilled message: HubSpot’s widget API has no way to prefill one.
Freshchat
Opens the widget with the goal and the summary in the reply box.
Freshdesk help widget
Opens its contact form with the goal as the subject and the summary as the description.
Help Scout Beacon
Opens its message form with the goal as the subject and the summary as the message.
Needs messaging (the contact form) turned on in the Beacon.
Opens a chat with your WhatsApp Business number, with the goal and the summary typed in.
The visitor sends it from their own WhatsApp. The goal is masked, as it travels in a link.
Opens the visitor’s email app with the goal as the subject and the summary as the message.
Your support page
Opens any URL, optionally with the goal and summary as query parameters to prefill your form.
Query parameters are off by default, because URLs can end up in logs.
Wayhint doesn’t install these messengers: they must already be on your page. The button tries the ones you ticked in order, then WhatsApp, email and your support URL, so a visitor whose ad blocker stopped your chat still gets a way to reach you. The summary can be turned off. Each handoff counts as an escalation in analytics, with the channel it opened.
Alerts and events for your team
Where to act, without opening the dashboard.
Slack
Alerts when a visitor needs a person, and a weekly digest, through an incoming webhook.
Mattermost and Discord (its /slack webhook) accept the same format. Microsoft Teams Workflows webhooks are not supported yet.
Webhooks
Goal, feedback and weekly account events as JSON, signed with HMAC-SHA256, to your CS platform, CRM, Zapier, Make or n8n.
Up to 5 webhooks per site, retried 3 times.
Alerts and events carry the question masked, the account when you track accounts, and a link to the conversation. No event identifies a user. More in customer success.
Install on any web app
One script tag, or one of these guides:
Your site sends a strict Content Security Policy? The widget needs no 'unsafe-inline' and works with Trusted Types: see security.
These integrations are new, and we haven’t tested them against live vendor accounts yet. If your setup behaves differently, tell us and we’ll fix it or say so on this page.
Let Nuri take it from here.
Free for 3 months for design partners. We set it up with you; you paste one script tag.