Bulk Publishing with Service Email Accounts: Best Practices

Updated 

Sprinklr supports service email accounts such as Gmail, Microsoft Exchange, and Amazon SES for sending and receiving emails.

These accounts are designed for:

  • Customer support interactions
  • One-to-one communication

They are not intended for bulk publishing or email marketing.

If you need to send high volumes of email (for example, through Journey Facilitator or campaigns), use Sprinklr Email Marketing. Using service email accounts for bulk sending can lead to throttling, delays, or failed deliveries.

Choose the Right Email Setup

Use Case

Recommended Option

Customer support conversations

Gmail, Exchange, or SES service email account

One-to-one communication

Gmail, Exchange, or SES service email account

Responding to customer emails

Gmail, Exchange, or SES service email account

Bulk publishing (Journey Facilitator)

Sprinklr Email Marketing

Marketing campaigns

Sprinklr Email Marketing

Promotions and newsletters

Sprinklr Email Marketing

Important: Service email accounts are optimized for conversational workflows, not bulk email distribution.

Why Bulk Publishing Can Fail

Bulk sending through service email accounts is subject to provider limits. You may experience:

  • API throttling
  • Sending rate limits
  • Delayed delivery
  • Temporary failures
  • Provider-side quota restrictions

These limits are enforced by the email provider and cannot be controlled by Sprinklr.

Provider-Specific Considerations

Gmail

Gmail enforces its own sending limits and API quotas. These limits may change over time.

Refer to: Gmail sending limits in Google Workspace

Microsoft Exchange

Exchange Online applies tenant-specific throttling policies.

As a practical guideline:

  • Sending more than ~30 emails per minute per account may trigger throttling

Note:

  • One email can generate multiple API calls
  • Emails with attachments increase API usage
  • Throttling can occur even at lower volumes

Refer to: Exchange Online limits

Amazon SES

SES supports high throughput but is designed for transactional and customer communication, not bulk campaigns.

For bulk use cases:

  • Do not use SES with Journey Facilitator
  • Do not rely on SES for large-scale campaigns
  • Use Sprinklr Email Marketing instead

Note: SES sending capacity varies by environment and cannot be fixed or guaranteed.

Before You Contact Support

Verify the following:

Check

Recommendation

Is this a bulk use case?

Use Sprinklr Email Marketing

Using Gmail?

Review Google’s sending limits

Using Exchange?

Check tenant throttling policies

Sending at high frequency?

Reduce sending rate

Sending large attachments?

Expect higher API usage

Using SES for campaigns?

Switch to Email Marketing

Best Practices

  • Use service email accounts for support and one-to-one communication
  • Use Sprinklr Email Marketing for bulk or campaign emails
  • Expect provider throttling for Gmail and Exchange
  • Avoid relying on fixed send limits
  • Always refer to provider documentation for current limits