Halfway through launch day: your top questions so far
Dani here 👋 We're about halfway through launch day and the questions have been great. A few keep coming up, so here are the answers in one place for anyone just arriving.
"If someone copies my Managed widget onto their site, does it use my credits?"
No. The widget checks which site it's on before it loads. If that site isn't on your allowed list, it doesn't appear at all, so there are no messages and no credits used.
"Does it keep the conversation if a visitor comes back?"
Yes. History is saved in the visitor's browser, so it survives reloads and return visits on the same device. If you'd rather start fresh each time, there's a setting for that.
"Can it know who the logged-in user is?"
Yes. Pass the user's details as metadata and your n8n workflow gets them with every message.
"Can I control what files people upload?"
Yes, for each widget: file types, maximum size and number of files.
"Can a person take over the chat?"
The most-asked one so far. Today a person can answer through the workflow (n8n's Slack "send and wait" works if they reply quickly), but a proper live takeover isn't there yet. Enough of you have asked that it's moving up our list.
We're here for the rest of the day, so keep the questions coming. What should we answer next? 👇
— Dani
Replies
If two people use the same browser, does signing out clear the saved chat before the next person signs in? That matters if the workflow returns order or account details.
@al_kub Good question, and an important one. Not automatically: the widget doesn't know when someone signs out of your site, so it won't clear anything by itself. If your workflow returns order or account details, you'll want to set up two things:
1. Give each signed-in user their own session key. Set it to something like their user ID. Each user then gets their own saved conversation and their own session ID in n8n, so person B never sees person A's chat in the window.
2. Clear the saved data when someone signs out. The conversation is stored in the browser's local storage under the session key followed by _CHAT. Your sign-out code should remove that entry. Also remove the chatInputHistory entry, or turn off "input history" in the widget settings. That feature remembers the last few messages a person typed (press the up arrow to reuse one), and it's shared across the browser, not stored per user.
Also worth doing: don't let the workflow trust the browser alone. Before returning order or account details, check a signed token from your backend that proves who's signed in. Then even if something stays on a shared computer, the workflow won't hand one person's details to another.
A simple "clear chat" call you can run on sign-out would make this easier. That's a good suggestion, and we're adding it to our list.
— Dani