Continue Conversations Across Pages

How to get there: Go to Settings → Business, select your business, then open Profile → Preferences → Visitor Experience.

Turn on Use cookies to let visitors continue a recent chat on the same website and browser. Boei sets its visitor cookie only after the visitor starts a conversation themselves. Loading a page or opening the widget does not set it.

With cookies on

  • Visitors can continue chatting after moving to another page.
  • An open chat can reopen on the next page.
  • In the chat widget, visitors can open the three-dot menu and choose Recent chats. They can select a conversation to continue it or choose New conversation to start fresh.
  • Access lasts up to 96 hours after conversation activity. Browsers may remove cookies sooner.
  • After access expires, Boei does not copy the old visitor's name or email into a new chat.

Starting a new conversation is separate from forgetting the visitor. On a shared computer, a website should call Boei.reset() when its user logs out.

With cookies off

The Recent chats menu option is hidden. The current chat works while the page stays open. Boei holds visitor details in memory, without visitor cookies, localStorage or sessionStorage. Reloading or leaving the page starts fresh. Messages already sent remain in your Boei inbox.

For welcome messages set to appear only once, Boei uses the previous page's address when available. This can stop the message repeating while someone browses your site. It cannot reliably recognise a returning visitor without storage.

If a chat starts fresh on every page

  1. Check Use cookies for the correct website.
  2. Send a message, then move to another page on the same website.
  3. Check whether your cookie banner has set Boei({ cookies: false }).
  4. Check whether the browser blocks or removes cookies.

Direct iframe embeds without the website script keep chat in memory only. Use the website script to carry conversations between pages.

See Cookies for the cookie name, lifetime, cookie-banner connection and logout action. Visits and conversation access use separate IDs. Turning cookies on does not turn page visits into a unique-person count.