Spam and Abuse Protection
Stoked protects your community site’s public forms from bots, fake messages and abuse. It’s always on, and there’s nothing to set up.
What’s Protected
- The message form on advocate profiles.
- Your advocate application form (
/join). - Event RSVPs.
- The rest of your community site, against bots that load pages too fast or probe for weaknesses.
Visitors never have to solve a CAPTCHA puzzle. The protections below work in the background.
How It Works
Verification before a message is delivered
A new visitor’s message isn’t sent to the advocate right away. The visitor first confirms their phone number or email address with a code, and only then does the advocate get the message. Until then, the conversation waits in your Activity Inbox as Awaiting [prospect]’s Verification.
This also stops people from messaging under someone else’s name:
- If a visitor enters a phone number or email that belongs to someone else, the code goes to the real owner, so the message is never delivered.
- If that person already has a conversation with the same advocate, the visitor is asked to log in instead.
- Verifying never releases waiting messages on its own. If a prospect verified somewhere else, they see Send your message to [advocate] and have to click it. An admin can also release it (see What You Can Do).
Phone number checks
Before a code is texted, Stoked rejects numbers that are invalid, are landlines, or are outside the countries your community operates in. See International Settings.
Limits on repeated submissions
Stoked limits how often one connection can start conversations or submit applications in a short period, and how many new conversations and verification texts one community can get in a day. It also limits how fast a single connection can load pages. The limits reset on their own. Real visitors rarely reach them.
Hidden spam trap
The message, application and RSVP forms include a hidden field that people never see. Simple bots fill in every field, so a filled-in hidden field marks the submission as likely spam.
Stoked records that signal but still accepts the submission. Some browsers autofill hidden fields, so throwing the submission away could cost you a real application or message.
Message safety screening
Every message is screened automatically for harmful content. A flagged message isn’t delivered. Admins can still read it in the conversation, where it shows in red. Screening is always on; see AI Assistance.
Blocking scanners
Connections that probe your site for common website weaknesses, or request lots of pages that don’t exist, are blocked for a while.
Stoked manages all of these protections, including the limits. They aren’t adjustable from your admin portal.
What a Real Visitor Sees If Caught
If a limit stops a real person, they see one of these messages. None of them is permanent.
| What the visitor sees | Why | What to tell them |
|---|---|---|
| Too many application attempts. Please try again in an hour. | Several applications came from the same connection recently. | Wait an hour, or switch from Wi-Fi to mobile data. |
| Attempting to create too many conversations! Please try again later. | Several new conversations came from the same connection recently. | Try again later, or switch networks. |
| Too many conversations have been created for this community today! Please try again tomorrow. | Your community reached its daily limit on new conversations. | Try again tomorrow. |
| Too many verification requests have been made for this community today. Please try again tomorrow. | Your community reached its daily limit on verification texts. | Try again tomorrow, or choose email if the form offers it. |
| A plain page reading Rate limit exceeded. Retry later. | The connection loaded pages very fast. | Wait a few minutes and reload. |
| A plain page reading Forbidden. | The connection was blocked for scanner-like behavior. | Try again later or from another network. |
The per-connection limits count everyone sharing that connection. At an event, store or office where many people sign up on the same Wi-Fi, a few may see a “too many” message. Ask them to use mobile data.
If you expect an unusually large burst of new conversations in one day, such as a big launch, let Stoked know ahead of time.
The hidden spam trap never shows anything to visitors. Their message or application goes through as normal.
What You Can Do
- Leave unverified conversations alone. A conversation marked Awaiting [prospect]’s Verification hasn’t reached the advocate. If the prospect never verifies, nothing is delivered.
- Only activate people you recognize. A conversation marked Awaiting Activation is from a verified prospect whose message hasn’t been released. Click Activate in the Activity Inbox to send it to the advocate.
- Block a prospect who sends spam or abusive messages in a conversation. See Blocking and Unblocking Prospects.
- Close spam conversations with a close reason so they don’t skew your reports. See Close Reasons.
- Tell Stoked if you see a wave of spam getting through.
Related: Managing Prospects · Using the Activity Inbox · AI Assistance · Privacy & Safety (for prospects)