Shared Inbox

Every ask in one place. The misses tell you what to write next.

Open the inbox and you see what visitors asked: what the agent cited, what it could not, and which threads a teammate should email. You do not need a ticket queue to know what your site is missing.

Inbox · acme.com
How do I reset my password?citedWhat’s your refund SLA?gapCan a human help with this order?handoff

The inbox

Tuesday’s questions, in one list.

The widget is the visitor’s surface. The inbox is yours. Cited threads confirm the index is working. Unanswered ones name the gap. Handoffs arrive with enough context that a teammate can email without replaying the chat from scratch.

Content gaps

Unanswered chats are the list of pages worth writing next.

  • When the agent cannot cite a source, the thread is flagged instead of silently failing.
  • Those flags are a backlog: refund SLAs, sizing charts, onboarding steps you thought were obvious.
  • Write the missing page, re-index, and the next visitor with that question can get a cited answer.

How teams use it

Read, write, hand off.

  1. step 01

    Read the asks

    Scan questions as they come in. Cited threads confirm coverage. Unanswered ones name the gap.

  2. step 02

    Close the gap

    Publish the missing page, then re-run the source so the agent can cite it next time.

  3. step 03

    Take the handoff

    When a dossier lands, a teammate emails the visitor. The widget does not pretend a human is inside it.

Handoff summary

The next person should not re-read fifty messages.

Rinhelp collects an email and writes a dossier: the problem, what the visitor wanted, what the agent tried, and which pages it retrieved. Follow-up is email. The original thread stays in the inbox.

problemAnnual plan refund window is not on the siteemailjordan@studio.exampleurgencyurgent

Questions

How the inbox actually works

Where do Rinhelp conversations go?

Every live visitor chat lands in the workspace inbox. Teammates with access can open the thread, see citations, and see which messages were unsupported.

What is a content gap in Rinhelp?

A content gap is a conversation the indexed pages could not support. The inbox flags those threads so you know which help article, policy, or product page to write next.

What is in a human handoff summary?

The dossier includes the visitor’s email, an optional note, the problem in plain language, what the agent tried, retrieved sources, and why the handoff fired. Follow-up is async over email.

Do I pay for unanswered conversations?

No. Unresolved conversations are free. A conversation counts as a resolution when it ends with a grounded, cited answer and the visitor does not need more help.

Is the inbox a ticketing product?

No. It is a shared view of widget conversations plus handoff dossiers. There is no SLA, assignment workflow, or omnichannel suite. The point is to see asks and gaps, then write better source pages.

Keep exploring

The rest of the loop.

Start with the support questions your website can already answer.

Add your site, style the chat, and paste one line into your page. By the end of the afternoon you will know what your content already answers — and, from the flagged conversations, exactly what it is missing.