If the chat bubble on your clinic’s website has started filling your inbox with gibberish messages, fake phone numbers, or “leads” that never answer a follow-up text, you’re not imagining it \u2014 bots have found your site. OneSystemCRM now includes built-in Spam Protection for your website Chat Widget, so junk submissions get caught and quarantined before they ever reach your front desk or burn through your text and email sending reputation.<\/p>\n\n\n\n
For a clinic, this matters more than it sounds. Every bot submission that slips through triggers your normal new-lead workflow: a confirmation text, an intake email, maybe a task for your front desk to call back. Do that a few dozen times a day and you’re not just wasting staff minutes \u2014 you’re teaching SMS and email providers that your number and domain send messages nobody wants, which can hurt deliverability for the real patients messaging you.<\/p>\n\n\n\n
Spam Protection watches chat widget submissions for the patterns bots leave behind \u2014 no CAPTCHA puzzle required. When a submission looks automated, OneSystemCRM can do one of three things, depending on how you configure it:<\/p>\n\n\n\n
Nothing is deleted. Flagged contacts stay in your CRM under a review tag, so if the system gets it wrong and a real patient gets flagged, you can find them and clear it manually.<\/p>\n\n\n\n
[SCREENSHOT: Chat widget on a clinic website with a chat bubble open, showing a suspicious auto-generated message]<\/p>\n\n\n\n
From your OneSystemCRM dashboard, go to Sites<\/strong>, then open the website that has your chat widget installed. Click into the Chat Widget<\/strong> settings for that site.<\/p>\n\n\n\n [SCREENSHOT: Sites menu with the clinic’s website selected and Chat Widget settings panel open]<\/p>\n\n\n\n Inside the Chat Widget settings, find the Spam Protection<\/strong> toggle and switch it on. This starts screening new chat submissions immediately \u2014 there’s nothing else required to activate detection itself.<\/p>\n\n\n\n [SCREENSHOT: Spam Protection toggle switched to the “on” position]<\/p>\n\n\n\n Once it’s on, pick an action from the dropdown:<\/p>\n\n\n\n Most clinics start with Tag only<\/strong> for a few days, confirm the flagged submissions really are junk, then switch to Pause Both<\/strong> once they trust it.<\/p>\n\n\n\n [SCREENSHOT: Action dropdown showing Tag only, Pause SMS, Pause Email, and Pause Both options]<\/p>\n\n\n\n Flagged contacts are marked with a review tag in your CRM. Go to Contacts<\/strong>, filter by that tag, and scan the list every few days. You’re checking for two things: that the flags are actually spam, and that no real patient got caught by mistake. Clear the tag from any contact you’ve confirmed is legitimate so normal messaging resumes for them.<\/p>\n\n\n\n [SCREENSHOT: Contacts list filtered by the spam review tag]<\/p>\n\n\n\n Bright Smile Dental added a chat widget to their homepage so people could ask about appointment availability without calling. Within a month, their front desk coordinator was starting each morning by clearing eight to fifteen chat submissions that were obviously not real \u2014 foreign phone numbers, single-letter names, messages that were just a string of links.<\/p>\n\n\n\n Every one of those had already triggered the practice’s new-lead text and confirmation email before anyone caught it manually. The office manager turned on Spam Protection, ran it in Tag only<\/strong> mode for four days to confirm the flagged contacts really were bots, then switched to Pause Both<\/strong>. The front desk coordinator went from clearing a stack of fake leads every morning to spot-checking a short tagged list twice a week \u2014 and the practice’s text deliverability to actual patients improved within the same month, since fewer messages were bouncing off dead numbers.<\/p>\n\n\n\n Why did a real patient get flagged as spam?<\/strong>\nNo spam filter is perfect. If someone typed very quickly, pasted their message from another app, or used a VPN, they can occasionally match bot-like patterns. Check the contact under your review tag, confirm it’s a real person, and remove the tag \u2014 their messaging will resume normally.<\/p>\n\n\n\n Will Spam Protection block real patients from using the chat widget?<\/strong>\nNo. The chat widget still accepts every submission. Spam Protection only changes what happens after<\/em> a submission comes in \u2014 whether it’s tagged for review or has automated messaging paused \u2014 it never stops someone from sending a message in the first place.<\/p>\n\n\n\n I turned it on but I’m not seeing any flagged contacts. Is it working?<\/strong>\nGive it a few days. Bot traffic isn’t constant, and a low-traffic clinic site may simply not be getting hit yet. You can confirm the toggle is on by returning to Chat Widget settings \u2014 if it’s active, detection is running even with nothing flagged yet.<\/p>\n\n\n\n Can I set different rules for different sites if I run more than one location?<\/strong>\nYes. Spam Protection is configured per site, so a multi-location practice can turn it on independently for each location’s chat widget and even choose a different action for each.<\/p>\n\n\n\n Does this replace after-hours auto-replies or my AI chat assistant?<\/strong>\nNo \u2014 it works alongside them. Spam Protection only filters out likely bot submissions; it doesn’t change how you handle legitimate after-hours messages. See How to Set After-Hours Rules for Your Clinic’s AI Chat Assistant<\/a> if you haven’t configured that yet.<\/p>\n\n\n\nStep 2: Turn On the Spam Protection Toggle<\/h3>\n\n\n\n
Step 3: Choose What Happens to Flagged Leads<\/h3>\n\n\n\n
\n
Step 4: Review Flagged Contacts<\/h3>\n\n\n\n
Clinic Use Case: A Dental Practice Stops Losing Front-Desk Time to Bots<\/h2>\n\n\n\n
Troubleshooting & FAQ<\/h2>\n\n\n\n