A chat should not ask for sensitive information just because it can.
The idea
Collect only what your team needs to answer the question. Do not request passwords, payment-card details, government IDs or medical histories in a general website chat. Tell visitors when they are speaking to an automated assistant and how a person can continue. Your published privacy notice should accurately describe your actual data practices; have qualified counsel review compliance questions for your business.
Put it into practice
- Remove unnecessary fields from the initial chat flow.
- Write a clear handoff path for sensitive or account-specific requests.
- Check that site notices match what the widget and inbox really collect.
What this looks like
A clinic's general site chat can explain office hours and contact paths, but should direct patient-specific medical information to an approved private channel.
What to measure
Audit a sample of conversations for requests the assistant should have redirected and update rules promptly.
WHERE ZU WEB FITS
ZU Web is best configured with narrow, approved topics and a human escalation route for anything sensitive.
Choose ZU Web for $2.99/month Standard plan includes 100 new chat conversations per month. See current plan details before buying.