Help centre · Event organisers

How the API behaves under load for event organisers

Schedule changes reach the audience too late. Can I push a big batch at once? Yes. Send recipients in batches rather than one call per number and the queue handles the pacing for you.

Event organisers
How the API behaves under load
Plain English
Live in 5 minutes

The short answer

Yes. Send recipients in batches rather than one call per number and the queue handles the pacing for you.

Why event organisers ask this

Schedule changes reach the audience too late. It usually surfaces the first time a real list goes out, when ticket details, gate changes and on-sale announcements stop being a plan and become a send.

What it changes for you

Get this right and the outcome is an audience that knows before it arrives. Get it wrong and the cost shows up quietly, in messages nobody read and money already spent.

Doing it in the platform

The compose screen shows the segment count, the cost and the sender name before anything leaves, so the decision is made before the money moves.

Getting started

Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.

FAQ

Can I push a big batch at once?

Yes. Send recipients in batches rather than one call per number and the queue handles the pacing for you.

Is this different for event organisers?

The mechanics are the same. What changes is the volume and the timing, because event organisers mostly send ticket details, gate changes and on-sale announcements.

How do I get started?

Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.

Related pages

Messaging for event organisers

Support on Telegram at @exerioco sets you up in under five minutes.