The spam filter and "No Access" Submissions
SALT's spam filter blocks Submissions that match patterns associated with abusive activity — duplicate IPs, emails, or phones submitted within a short window, or Twilio-flagged invalid phones. Blocked Submissions show "No Access" and are filterable in the list. You can review and clear them from staff workflows.
In short: “No Access” means the spam filter blocked the Submission. Find them by filtering the Submissions list. Review the details — if legitimate, clear the block; if not, leave them filtered out.
What “No Access” means
SALT runs every consumer-submitted Submission through a spam filter. When the filter trips, the Submission is marked “No Access” instead of completing normally:
- The consumer sees a “no access” page (not an error, not a confirmation).
- Your agency’s list shows the Submission with the No Access label, hidden by default.
- No notifications fire for No Access Submissions.
This protects you from being flooded with bot, abusive, or duplicate submissions while still preserving the record for review.
What triggers the filter
The filter looks for patterns within a recent window (typically a few hours) on a per-account, per-Form basis:
- Duplicate IP address — many Submissions from the same IP
- Duplicate email — the same email submitted repeatedly
- Duplicate phone number — the same phone repeatedly
- Invalid phone number — flagged via Twilio’s phone validation lookup
- Excessive submission rate — a single source submitting too quickly
Each signal contributes; multiple signals together raise confidence. The filter only runs for unauthenticated consumer submissions — it doesn’t apply to logged-in agents creating Submissions internally.
Find No Access Submissions
The Submissions list filters No Access out by default. To see them:
-
1
Open the Submissions list.
-
2
Add a filter for No Access (or “Spam,” depending on your agency’s labeling).
-
3
Review the Submissions that appear.
Each No Access Submission carries the data the consumer entered — you can review it, look for false positives, and decide what to do.
Clearing a legitimate “No Access” Submission
If you find a legitimate consumer was caught by the filter:
- Review the contact info to confirm it’s not a duplicate or abusive pattern.
- Clear the block to bring the Submission into normal flow (the exact action depends on your role and agency configuration).
- Reach out to the consumer if their original session left them confused — send them a Continue Link so they don’t have to start over.
For complex situations or repeat false positives, contact support.
When to leave a “No Access” Submission filtered out
- It’s clearly bot traffic (random characters, no real contact info, suspicious patterns).
- It’s a duplicate of a legitimate Submission already in your list.
- It’s an obvious test or spam attempt.
In those cases, leaving the No Access label in place is the right call. The Submission stays in your records but doesn’t pollute your active list.
Common questions
Can I disable the spam filter? The filter is generally on by default to protect your agency. If false positives are a recurring problem on a specific Form or campaign, contact support to discuss alternatives — see Spam mitigation (where applicable).
Will my legitimate consumer get a confirmation if their Submission was blocked? No. No Access Submissions don’t trigger confirmations.
What if the consumer says they tried to submit but never heard back? Check the No Access filter first. If they’re there and legitimate, clear the block and follow up. If they’re not there at all, they may have abandoned the Form before completing — ask them to try again.
Does the spam filter slow down legitimate consumers? Filtering happens server-side after the consumer hits submit. They don’t see additional friction unless they trip the filter — and even then, they just see the No Access page instead of the confirmation.