Skip to main content
Avoca controls outbound volume at multiple layers so campaigns stay compliant and avoid carrier filtering.

​
Workflow-Level Throttling

  • Every workflow node includes batching metadata—batch size, delay, and business-hour windows.
  • The execution engine only dequeues a limited number of contacts per cycle, keeping sends within defined hours and preventing sudden spikes.
  • Today, we also allow teams to set daily send caps so total outbound volume stays within agreed thresholds.

​
Messaging Queue Controls

  • Text jobs are grouped by team or use case, then pushed through a rate-limited queue with fixed concurrency and per-second caps.
  • Base delivery is powered by our carrier partner (Twilio), whose messaging services enforce throughput and spam-detection guardrails; invalid jobs (missing numbers, failed validation) are rejected immediately, while valid jobs flow forward in controlled bursts.
  • We’re adding additional in-house throttling layers that will let admins tune per-workflow and per-channel rates beyond the current carrier-level controls.

​
Deliverability Safeguards

  • Admins can enable features like Sticky Sender, long-message-to-MMS conversion, smart encoding, area-code geomatching, and fallback routes.
  • These switches stabilize sender reputation, keep conversations on consistent numbers, and reduce the chance of carrier filtering.
Together, pacing, queue-level throttles, and reputation tools ensure high delivery rates even for large or time-sensitive campaigns. For tuning advice, contact [email protected].