Campaigns – Max 1,000 Recipients and Batch Handling

When you create a campaign in Vendion, you quickly see how many recipients the segment contains. If there are more than 1,000 – read on. Here we explain why the limit exists, how the system handles the send technically, and what workflows you can use for larger bases.

The limit: 1,000 recipients per campaign batch

The current maximum is 1,000 recipients per campaign. This is a performance limit, not a business limit. The reason: ClickSend (our SMS provider) is happy to accept higher volumes, but if we send everything at once we risk timeouts. Each batch is sent with a short pause between messages to keep the system stable.

What happens when you have more than 1,000 recipients in your segment?

Today (March 2026) we have two modes:

Mode 1: Campaign with 1-1,000 recipients Sent in a single batch. Typical completion time:

• 100 SMS → ~10 seconds
• 500 SMS → ~45 seconds
• 1,000 SMS → ~90 seconds

Mode 2: Campaign with >1,000 recipients The Send button is disabled. The UI shows a warning: "The segment contains 2,347 recipients. Max 1,000 per campaign. Split into multiple campaigns or contact support for help."

Three ways to send to larger lists:

Option A – Split the segment with filters (recommended)

1. Create two segments covering different groups. Example: segment "A-K" uses the filter "name starts with A-K" (coming), or split by date – "first visit within 90 days" + "first visit more than 90 days ago".
2. Create one campaign per segment. Same text, same schedule, different target groups.
3. Check that the total adds up. 600 + 800 = 1,400 recipients total.

Advantages: Clear who got what, easy to compare results, no limit to hit.

Option B – Schedule campaigns in time series

1. Campaign 1: Send now to 1,000 recipients (randomly from the segment – used in beta).
2. Campaign 2: Scheduled 10 minutes later to the next 1,000.
3. Campaign 3: Scheduled another 10 minutes later to the last 347.

Advantages: Loads ClickSend evenly. Recipients don't notice the difference.

Disadvantage: Important that no one ends up in two campaigns (use deduplication or exclusion filters).

Option C – Import via Brevo (for email)

If the recipient list is too large and it is email – use Brevo instead of Vendion. See the separate article "Brevo – Newsletter Integration". Brevo has no 1,000 limit and is built for large newsletters.

Cost to consider

Even if you technically can send 5,000 SMS in a series, check the cost:

• 5,000 × 0.89 kr = 4,450 kr in SMS cost

For large campaigns it can pay off to:

• Switch to email (included in Vendion, no extra cost)
• Filter more aggressively (maybe just "VIP + loyal" is enough, not everyone)
• Use Brevo for newsletters and Vendion for targeted campaigns

When will the limit be raised?

On the roadmap (Q3 2026):

• Automatic batching of large campaigns (you see one campaign, the system splits the send behind the scenes)
• Retry mechanism if a batch fails
• Queue-based handling with progressive back-off

What NOT to do:

• Try to bypass the limit by going outside Vendion and sending directly via ClickSend – then you lose statistics, GDPR log, and unsubscribe handling.
• Create "flash campaigns" with the same text but split recipients without marking them up – you lose overview.
• Forget the segment's natural growth – a segment that was 800 recipients last month may be 1,200 this month.

Monitoring during large sends

When you start a large campaign:

1. Let the page load for at least 2 minutes before navigating away. The system works in the background and updates campaign status continuously.
2. Go to Marketing → Campaigns → [your campaign] to see live updates:
   • Sent: 234 / 1,000
   • Delivered: 198 / 234
   • Failed: 2 (inspected)
3. On a failed row – check the error message (usually an invalid phone number).

Troubleshooting: "My campaign is stuck on Sending"

• Normal: Campaigns under 1,000 take up to 2 minutes.
• Abnormal: The campaign remains as "Sending" after 10 minutes.
• Action: Contact support@vendion.com – we can troubleshoot and manually restart the batch.