An action is a single step your campaign timeline performs for one person. Think of it as one line item on your event's to-do list, done on your behalf.

Each of these is an action:

If your timeline does something for someone, that something is an action.

An action is counted each time AEvent does something for one person. So one email to 1,000 registrants uses 1,000 actions, not one. Think of it as 1,000 little jobs done on your behalf, one for each person who received it.

The same idea stacks across action types. If you send an email, a text, and a tag to the same 500 people, that is three actions per person, or 1,500 in total.

An easy one to miss: actions you set to fire at registration count too, and each connected destination counts its own. If a new registrant is synced to more than one place at sign-up, that is an action for each. It is a common blind spot, so include your registration actions when you picture your total.

One friendly exception: autochats. Because an autochat is a single message broadcast to your live room, it counts as one action per message, no matter how many people are watching, not one per attendee. Emails and texts count once per recipient; an autochat counts once per message. It is a genuinely cheap way to reach a full room.

Autochats are not the only friendly exception. A few actions, like ringless voicemail and certain bulk sends, also count once per batch rather than once per person. Your Usage panel always shows your real number, so you never have to guess.

Encores (like-live replays) send their actions again, so those sends count again, the same way the first send did.

Because most actions count simply one per person per send, your usage is predictable: multiply who receives an action by how many actions reach them, and that is your total, with those few per-batch exceptions coming in even lower. Your plan's monthly allowance is built with this in mind.

Only the outbound send is metered. Everything you do to prepare and target that send is free.

A few of these, autochats, ringless voicemail, and some bulk sends, count once per batch or broadcast, not once per person.

A quick note on autochats: an autochat is a single message broadcast to your live room, so it counts as one action per message, not one per attendee. Sending it to 5 people or 5,000 is still one action. Everything else on the right column is part of setting up a send, so it never touches your allowance.

"Sent" means AEvent handed the action to the provider. People who are skipped before a send, such as a registrant with no valid phone number for a text, are not counted.

The data and targeting work is where a lot of your event's value lives, and it is all native and free. Only the outbound send is metered.

That means you can do all of this at no cost to your action allowance:

You only spend an action when a message actually goes out. All the shaping that makes it land well is included.

Every plan comes with a monthly allowance of actions. Your plan includes the amount below, plus any add-on action packs you have, which stack on top.

Your allowance resets each billing cycle, on your billing date, so you start fresh every month.

Where to see your usage: open the Usage panel in the app. It shows your actions used this cycle, alongside your other meters.

Actions are not webinar hours. These are separate meters. Actions measure the sends your timeline performs; webinar hours measure broadcast-server time. When you automate a Zoom or GoToWebinar event, AEvent streams your video into that platform from our own broadcast servers for the length of the event, and that server time is what webinar hours count. AStream, our native player, delivers your video directly to your attendees without using those broadcast servers, so AStream events do not use webinar hours. If you need more, you can add server hours. Running low on one does not affect the other. In all, the Usage panel tracks four separate meters, Actions, Webinar Hours, Storage, and Campaigns, each with its own limit.

As you approach your limit: keep an eye on the Usage panel, and upgrade your plan or add an action pack before you exceed your allowance. It is best to stay ahead of your limit rather than run past it, and the Usage panel is the best place to watch your pace through the cycle.

An AEvent action is the same basic idea as a "task" in Zapier or an "operation" in Make: one automated step. Tools price this differently, and some offer unlimited models, so the honest comparison depends on the tool. The distinction worth knowing is that AEvent only meters the actual send. The audience and data work that shapes it is native and free here, where in some setups that would be extra steps.

A few simple habits keep your usage comfortable and predictable:

Does a no-show still count?
An action counts for each person it is actually sent to. If your timeline sends a follow-up to your no-shows, that is one action per no-show it goes to.

Is one long SMS one action or several?
One action per recipient, regardless of message length. Your SMS provider may bill a longer message as multiple segments, but that is their billing, separate from AEvent actions.

How are autochats counted?
One action per message you send to the room, not one per attendee. Because an autochat is a single broadcast into your live chat, sending it to 5 people or 5,000 is still one action.

Do failed sends count?
Actions are counted when AEvent sends them out to the destination. People who are skipped before a send, such as a registrant with an invalid phone number, are not counted.

Do Encores (like-live replays) count?
Yes. An Encore sends its actions again, so those sends count again, the same way the first send did.

Does downloading my attendance list count?
No. Exporting or downloading your attendance report is free. It is not an action.

Where do I check my usage?
The Usage panel in the app, which shows Actions, Webinar Hours, Storage, and your other meters.

I have sub-accounts (or a team) - whose actions count?
All of them. Sub-account and team-member actions draw from your plan's shared action pool, so your whole workspace counts against one allowance.