Skip to main content

​
Multi-Gateway Sender Pooling for High Throughput

Attempting to broadcast 25,000 text messages through a single Virtual Long Number (VLN) causes severe telecom carrier throttling. Standard 10DLC or long-code numbers are throttled at 1 to 10 messages per second by wireless carriers (such as Verizon, AT&T, and Vodafone), causing delivery backlogs that delay urgent price-sensitive real estate announcements. BrokerOS resolves this bottleneck through Multi-Gateway Sender Pooling (CampaignSmsSenderPoolConfig) and an automated Pre-Flight Delivery Verification engine (SmsPreFlightModal.tsx).

​
Sender Pool Architecture

​
Sender Pool Allocation Modes

When configuring an SMS broadcast in the Campaign Wizard, marketing managers can distribute audience volume across multiple verified phone numbers and sender IDs:

​
Pre-Flight Verification Modal

Before executing a broadcast, the Pre-Flight Modal (SmsPreFlightModal.tsx) performs a mandatory delivery and financial audit:

​
Automated Segment Analysis

Evaluates the message text to identify the exact character encoding and segment boundaries:
  • Character Count: Exact count of characters in the message body.
  • Encoding Type: Identifies whether the copy uses standard GSM-7 (up to 160 characters for single segment) or Unicode (reduced to 70 characters due to emojis or special characters).
  • Total Billable Segments: Computes total segments across the entire audience (Total Leads×Segments per Lead\text{Total Leads} \times \text{Segments per Lead}).

​
Gateway Cost Estimation Breakdown

Calculates projected telecommunication expenditure across selected gateways based on standard benchmark rates (SMS_PROVIDER_PRICING_ESTIMATES):

​
Provider Rate Throttling in BullMQ Workers

The background processor (marketing-sms.processor.ts) respects provider-specific throughput limits (SMS_PROVIDER_THROTTLE_LIMITS) to ensure carrier compliance:
  • Twilio: Paced to stay within MPS (Messages Per Second) limits allocated to the Messaging Service SID.
  • AWS SNS: Regulated according to AWS account spend quotas and destination country throughput.
  • Gupshup: Paced to comply with Indian telecom DLT promotional throughput rules.
  • Automatic Recovery: Transient carrier failures or 429 Too Many Requests responses are rescheduled with exponential backoff.