The chat widget — Tips

• Point the widget at the same table your form and your email address already use — one queue, three doors. • List your own site's origins on the widget and a phishing page can't wear your support chat; leaving it blank means anywhere, which is the honest default for something built to be embedded. • Give the table an Auto number field so chat tickets carry the same reference as everything else in the queue. • Map the opening message to a Long text field and the grid shows what was asked without anyone opening the ticket. • Promise the reply time you can actually keep. "A few hours" kept beats "a few minutes" missed - the point of stating it is that nobody sits watching an empty box. • Label only the statuses a customer benefits from seeing. Three good ones read better than every option in your workflow. • Answers come from your table, never from RowFold's own help — your visitors should never be reading our documentation. • Start with the ten questions your team answers most. A knowledge base earns its keep at about that size, not at a hundred articles.