All emails and SMS messages sent by the platform go through the same delivery services, using a shared domain.
This is shared across all Pinpoint users, so we need to make sure we manage the volumes in some way to avoid the messages sent from being marked as spam.
Overview
When configuring a Send Email/SMS (Application) or Send Marketing Email/SMS automation action in the platform, you’ll see a note that reads:
"Sending a large number of marketing emails/SMS messages may result in this email/SMS action being temporarily disabled."
Because the sending domain is shared, if one user’s automation triggers a flood of unsolicited messages that recipients mark as spam or junk, it can hurt deliverability for everyone.
These two automation types are high-risk because:
Send Email/SMS (Application) sends messages automatically for every matching application, which could mean thousands of emails going out at once if the trigger conditions are broad.
Send Marketing SMS sends messages to Talent Pipeline candidates or job seekers proactively, which is more like a whole campaign than a one-to-one email. It's closer to marketing behaviour, which providers are more likely to flag.
Behavior
If the delivery service detects that an address/number bounced hard or was marked as spam, it suppresses that address/number - meaning no further messages go to that candidate. These emails will also not appear in the Messages tab.
If this happens enough times, Pinpoint may step in and temporarily disable the automation action itself to stop further messages from going out.
Recommendations
Having said all that, we don’t want to put a hard limit to what you do with message actions!
The note is a heads-up rather than a traditional warning, and it’s there to prompt you to have a look at how you target these specific automations.
To avoid running into a problem, we recommend:
Narrowing message triggers
Personalising the content
Including opt-out checks
This helps you send out bulk messages that are less likely to be flagged as spam.