Skip to main content
Senderz sends on five channels. They share the same contacts, the same suppression list and the same set of send rules. You build the audience once and choose how to reach it. What differs between channels is where you can use them, how they are paid for, and which legal timing rules apply.

Email

Marketing and transactional email from your own verified domain, with open and click tracking built in.

SMS

Prepaid credits, an approved Sender name, automatic link shortening and STOP handling.

WhatsApp

Approved WhatsApp templates sent from an automation. Billed from the same credit balance as SMS.

Web push

Browser notifications with no app. Free to send, and switched on by the Senderz team.

Voice

Spoken one-time passcodes over the phone. Transactional only today.

​
Where you can use each channel

This is the first thing to know, because it decides what you can build.
A campaign is either email or SMS. There is no WhatsApp campaign, no push campaign and no voice campaign. WhatsApp and push reach contacts through an automation step. Voice is transactional only today, through the one-time passcode API. The Voice step has been retired from the automation builder.
Test sends live in the template editor. Open a template, then use Send test. Email and SMS both support it. There is no test button for WhatsApp or voice, and a test push can only be triggered through the API.

​
How each channel is paid for

SMS, WhatsApp and voice all draw down the same credit balance, but they count it differently. SMS counts characters, WhatsApp is a flat rate per conversation, and voice counts carrier message parts. A short Hebrew voice message costs several times what the same text costs as an SMS. Do not budget for them as one line.
Credits are bought separately from your plan. No plan bundles a monthly SMS allowance. See SMS for pack sizes, what counts toward a credit, and what happens when the balance runs out. A contact can be subscribed to email and not SMS, or the reverse. Each channel keeps its own consent state, with its own timestamp and its own record of where the consent came from. Four channels have their own consent record: email, SMS, WhatsApp and push. You can see and set all four on the contact profile.
Voice has no consent record of its own. It falls back to the contact’s SMS consent, SMS suppression and the SMS frequency cap. Passcodes are transactional, so they skip consent anyway, but a number that replied STOP is still never called.
Each consent record is one of four states. Marketing sends check the state for that channel only. An SMS STOP does not touch WhatsApp consent on the same number, and unsubscribing from email does not stop push. More detail in Consent and unsubscribes.

​
Quiet hours and Shabbat

Marketing SMS, WhatsApp, push and voice to Israeli recipients are held during quiet hours (20:00 to 08:00 local) and during Shabbat.
Held is not the same as dropped. A message that lands inside a closed window is deferred, then sent when the window opens. Senderz retries in steps of at least 15 minutes, up to 16 attempts across 4 days. Only if no window opens in that time does the message finally fail, reported as Send window expired. You do not need to reschedule it yourself.
Email is exempt from the legal Israeli window. Marketing email is not carrier-regulated the way SMS is, and you are the one paying for your sending reputation, so you decide when your email fires.
Email is exempt from the legal window only. Email is still deferred by two settings you control yourself: your workspace quiet hours in Settings → Sending Settings, and a block window set on an individual campaign. If your marketing email is not going out at the hour you expect, check those two before anything else.
Transactional messages skip quiet hours entirely on every channel. Full detail in Quiet hours and Israeli compliance.

​
Frequency caps

Every contact has a cap on how many marketing messages they can receive per channel. Caps are counted in Israel local time.
Voice has no cap of its own. It has no consent record either. Anything non-transactional sent by voice would count against the contact’s SMS cap. Passcodes are transactional, so in practice they are not capped at all.
A contact past their cap is skipped for that send and reported as Frequency cap reached. Transactional messages are not capped.

​
Smart sending

Smart sending skips a contact who was messaged very recently on the same channel, even if they are well inside their frequency cap. It is a switch on the individual campaign or automation step, on by default for a new campaign. The waiting windows it uses are a workspace setting, in Settings → Sending Settings. There are four of them. Smart sending covers email and SMS. WhatsApp, push and voice are governed by the frequency caps above.

​
What stops marketing on every channel

Some rules apply to all five channels at once. If a send is skipped for one of these, changing the channel will not help.
All sending is frozen, marketing and transactional alike. Contact support.
Marketing is stopped across every channel because bounce or complaint levels crossed a safety threshold. This one is sticky. It does not clear on its own and only the Senderz team can lift it. Transactional messages keep going. See Deliverability.
Your workspace holds more contacts than your plan covers. The contacts over the cap are parked and excluded from marketing until you upgrade. They are not deleted.
The channel switch for your workspace is off. Note that the SMS switch also covers voice, so turning SMS off stops voice calls too. Contact support to have a channel switched on.
A recipient can choose Pause on your unsubscribe page instead of leaving. While the pause runs they are skipped on every marketing channel. There is deliberately no override for this. The pause expires on its own, or the recipient lifts it by opting back in.
The address or number is on your suppression list, from a hard bounce, a spam complaint, repeated soft bounces, an unsubscribe or a STOP. This is the one rule a transactional message still obeys.

​
Transactional messages

Order confirmations, password resets and one-time codes are transactional. They are available on email, SMS and voice. Transactional messages skip marketing consent, frequency caps, smart sending and quiet hours, because the recipient asked for them.
Transactional messages still respect suppression. An address that hard bounced, or a number that replied STOP, will not receive an order confirmation either. Suppression is checked before anything else.

​
Seeing why a message was not sent

Every skipped recipient is recorded with a reason. You can read it in two places.
1

The campaign summary

A campaign that could not send shows a banner with the reason and what to do about it, for example Not enough SMS credits or Send window expired.
2

The contact's activity

Open the contact and read their activity. Each message shows its channel, its status and, if it was skipped, why.