Skip to main content
A voice message is a text-to-speech phone call. You give Senderz a line of text, Senderz places the call through the same Israeli carrier account that sends your SMS, and a synthesised voice reads it out. Nobody records anything and there is no audio file to upload. Voice runs on the 019 route only. SMS falls back to a second carrier if 019 is unreachable. Voice does not, so a 019 outage stops voice calls outright.

​
Where voice can be used today

Voice is a transactional channel only. The one supported way to place a voice call is the OTP API, by setting the channel to voice on a send. There is no voice campaign and, as of today, no Voice step in the automation builder.
The Voice call step has been retired from the automation builder. It is not in the step palette, so you cannot add one. If an automation you built earlier still contains a voice step, the builder removes it the moment you open that automation and reconnects the steps either side of it. The next save makes that permanent. The sending engine still knows how to place a voice call, which is what the OTP API uses. But there is no screen that lets you schedule one to a marketing audience, and voice is not one of the two campaign channels.
Campaigns are email or SMS. See the channel overview for what each channel can be used for.

​
Voice for one-time passcodes

The OTP API sends a numeric passcode to a phone number and verifies it back. It normally sends by SMS. Set the channel to voice on the send and the same code is delivered as a phone call instead. This is the useful case for voice. A recipient with a landline, a blocked SMS route or a number that simply is not receiving text messages can still be verified.
1

Request a code

Call the send endpoint with the phone number and the voice channel. You get back a verification ID.
2

Senderz calls the number

The code is spoken digit by digit, so “482913” is read out as separate numbers rather than as four hundred and eighty two thousand. The whole message is read out twice.
3

Verify what the caller typed

Send the verification ID and the code the person entered to the verify endpoint.
Because this is transactional, marketing consent, quiet hours, Shabbat and frequency caps do not apply. The recipient asked for the code. The sender name check and the credit charge still apply.

​
OTP limits

A number that is not a valid Israeli mobile is rejected before anything is spent. Local format and international format both work and are normalised for you.

​
The caller ID

A voice call goes out under an approved Sender name, the same list that SMS uses. It has to be one of your own approved names. The shared platform names are rejected for voice, exactly as they are for SMS. If you have no approved name of your own, the send is refused before any credits are held. Request a Sender name under Settings → SMS Sender names. See Sender names for how approval works.

​
How voice is billed

Voice draws down the same SMS credit balance as SMS, but it is counted differently, and the difference matters. A segment is 160 characters for plain Latin text, or 70 characters if the message contains Hebrew. Longer messages are split into 153 or 67 character parts and each part is a segment. That means a short Hebrew voice message costs roughly four times what the same text costs as an SMS. Budget for voice as its own line, not as a variant of SMS.
There is no separate voice wallet, no voice pack and no voice price list. Buy SMS credits under Settings → Plans & Billing and voice draws from the same balance. If the balance cannot cover the call, the send is refused and nothing is charged.

​
Limits of the voice channel

Every call uses the carrier defaults: a Hebrew male voice, the message read out twice, at normal speed. There is no setting for any of this anywhere in the product, and the OTP API does not accept voice options either.
Templates are email, SMS or push. There is no voice option. The OTP API takes its text inline on the send instead.
Voice sits behind the SMS channel switch, not a switch of its own. If SMS is switched off for your workspace, voice stops with it.
Anything past 1,005 characters is cut off before the call is placed. This is far longer than a passcode needs, but it is a hard ceiling.
SMS has a failover route. Voice has one route. If it is down, voice calls fail and there is nowhere else for them to go. Keep SMS available as the default passcode channel and treat voice as the exception you offer when SMS has not arrived.

​
If a voice send does run through an automation

An automation created before the step was retired can still hold a voice step until someone opens it in the builder. If one runs, it passes the same checks a marketing SMS passes, using the contact’s SMS state throughout:
1

Workspace checks

A suspended workspace, a contact parked over your plan’s contact limit, or the SMS channel being switched off all stop the call.
2

Sender name check

The caller ID has to be an approved name. This runs before any credits are reserved, so a rejected name never costs anything.
3

Suppression and consent

The contact’s phone number is checked against your SMS suppression list, and their SMS consent has to be subscribed. Someone who replied STOP to an SMS will not be called.
4

Frequency caps

Voice counts against the SMS cap of 3 per day and 10 per week, not a cap of its own. A contact who already received their SMS allowance that day will not be called.
5

Quiet hours and Shabbat

Marketing voice to Israeli numbers respects quiet hours and Shabbat.
6

Credits held, then charged

Credits are held before the carrier is called and charged when the carrier accepts the call. If the carrier refuses, the hold is released.

​
Quiet hours delay a call, they do not cancel it

A marketing call that lands inside quiet hours or Shabbat is not dropped. It is queued and retried when the window opens, at least 15 minutes apart, for up to 4 days across up to 16 attempts. Only then is it given up on. See Israeli quiet hours.

​
If the carrier goes quiet mid-call

If the carrier connection drops after Senderz has handed over the call, Senderz cannot tell whether the call was placed. It marks the message failed, releases the credits, and does not try again. One uncertain call is better than two real ones to the same person.

​
Where voice shows up in reporting

Voice has its own message channel, so a voice message is recorded separately from SMS in message history, in analytics and in the audit log, even though the two share a credit balance, a consent state and a Sender name list.

OTP API

The endpoints, parameters and error codes for sending a code by voice.

SMS

The credit wallet, Sender names and consent rules voice shares.

Sender names

Requesting and getting approval for the caller ID.

Israeli quiet hours

The windows a marketing call has to wait out.