Skip to main content
SMS in Senderz is platform-managed. You send through Senderz’s own Israeli carrier accounts (019 as the primary route, CommPeak as failover) and your credit balance pays the carrier. There is no carrier API for you to plug in and no per-workspace carrier contract. SMS is one of only two campaign channels. A campaign is either email or SMS. Every other channel (push, voice, WhatsApp) is available inside automations only.
Turning the SMS channel off for a workspace also turns off voice calls. The two share one channel switch.

​
How SMS is paid for

SMS is prepaid credits, bought separately. Credits are never bundled with your plan and no plan includes a monthly SMS allowance. Your plan pays for contacts and email sends. SMS is its own line. Buy credits from Plans and Billing, in packs of 500, 2,500, 10,000 or 50,000. Credits are added right after checkout and they never expire.

Every send is authorised first

Campaign, automation, test or transactional, no SMS reaches a carrier without the wallet approving it first. A hold is placed before the carrier call and settled when the carrier acknowledges the message.

The balance never goes negative

If two sends race for the last credits, one of them is declined. The balance cannot be pushed below zero.

Failures are refunded

A hard carrier rejection (invalid number, blacklist, refused message) releases the hold. A hold left behind by a crash expires on its own after 5 minutes. A carrier delivery report that reports failure also returns the credits.

Low balance warning

The dashboard and Plans and Billing flag the wallet once the balance drops below your low balance threshold (100 credits by default). There is no automatic top up.
If credits run out mid-campaign the remaining recipients are skipped, not queued. The campaign reports Not enough SMS credits. Top up, then send again.
The only SMS Senderz pays for itself is the login and two-factor code sent to you and your team. Those are a platform cost and never touch your wallet. Every message you send to a contact is billed to you, including test sends.

​
Credits, characters and carrier parts

These are two different counts and they are easy to confuse.
One credit covers up to 268 billable characters per recipient. Every recipient costs at least one credit. Past 268 characters it becomes two credits, past 536 it becomes three, and so on.Links and the unsubscribe line count toward those 268 characters.
A few characters cost double in Latin text: ^ { } \ [ ~ ] | and the euro sign. A single Hebrew letter or emoji anywhere in the message switches the whole message to the smaller 70 character budget. Worked examples, using the default unsubscribe line:
The second row is the one that surprises people. An English message with the default Hebrew unsubscribe line becomes a non-Latin message, so its per-part budget drops from 160 to 70 and it arrives as two parts. The credit cost is unchanged.

​
Sender names

The From name on an SMS is a Sender name, also called a sender ID. Because every workspace sends through one shared carrier account, Sender names are screened so one merchant cannot send as another merchant’s brand, or as a bank.
An approved branded Sender name is mandatory. There is no shared default and no fallback. A send with no Sender name set is rejected with SMS Sender name required. SENDER, INFO and SHOP are reserved for Senderz’s own login codes, cannot be requested, and are rejected the same way if you set one on a message.
1

Request one

Go to Settings → SMS Sender names and request your brand. The format is 3 to 11 characters, letters, numbers and hyphens, no spaces. Only an owner or admin can request or remove a Sender name.
2

Screening decides instantly

Most names activate straight away. A name that could impersonate someone is held for review instead, usually cleared within 24 to 48 hours. You get an email either way.
3

Pick it on the message

Choose it in the SMS composer or on the SMS template. The picker only offers names that are currently active.

​
What gets held for review

Screening is case insensitive, ignores hyphens, and unfolds common letter-for-digit swaps, so B4NK reads as bank. A name is held for review when it:
  • contains a bank, card or payments term (bank, Hapoalim, Poalim, Leumi, Mizrahi, Tefahot, Benleumi, Discount, Isracard, Mastercard, Visa, PayPal, Paybox)
  • contains a government, police or military term (gov, Mishtara, police, Tzahal, Bituach)
  • contains a carrier or courier term (Cellcom, Pelephone, Bezeq, Partner, Golan, Israelpost, Doar, FedEx, DHL)
  • contains a trust word (verify, verification, secure, security) or looks like Senderz itself (sender, senderz)
  • is exactly one of cal, max, bit, hot, ups, idf, otp, code, pin, alert, admin
  • is already active for a different workspace

​
After a name is active

An active Sender name can be revoked by Senderz if it turns out to be a problem. Once revoked, sends using it fail with Sender name not approved until you switch your campaigns and automations to a different name. You are emailed when this happens. A name that was rejected or revoked cannot be deleted and requested again. Request a different name instead. Pending names can be removed freely.
The SMS step in the automation builder stays locked until your workspace has at least one active Sender name. The locked step links straight to Settings → SMS Sender names.
More on the request and review flow in Sender IDs.

​
Writing the message

SMS content lives in an SMS template, or you can write it directly in the SMS campaign composer. Both use the same editor. The editor gives you a Sender name picker, the message body, and four insert menus:
  • Variables inserts a contact field, for example a first name, with a fallback.
  • Coupons inserts a unique per-recipient code from a dynamic coupon pool.
  • Emoji inserts an emoji. Remember that one emoji switches the whole message to the smaller 70 character carrier budget.
  • Unsubscribe is not a menu item. To place the opt-out link mid-message, type %%UNSUBSCRIBE_URL%% in the body where you want it.
Under the body you get a live count: billable characters, carrier SMS parts and credits per recipient. That count already includes everything Senderz adds at send time, so it reflects what you actually pay:
  • links shown at their shortened length, not the length you typed
  • the unsubscribe line, unless you turned it off on this template
  • a sample coupon code where a coupon token sits
There is no separate tracked link field. That was removed. Put your URL in the message body and Senderz handles the rest. Every URL in the body of a marketing SMS is rewritten to a short tracked link on track.senderz.app before the message goes out. You do nothing.
A 7 character short link, for example https://track.senderz.app/r/a1b2c3d. Tapping it records a click against the contact and the campaign or automation, then redirects to your original URL.
Up to 5 links per message are shortened. A sixth link is left as you typed it. Short links stay valid for 400 days.
Transactional SMS is never shortened or tracked. Test sends are not shortened either, although the composer preview shows you the shortened length so the count stays honest.
The unsubscribe link gets its own separate short link, so it can never be dropped by the 5 link limit. Clicks on it are deliberately not attributed to the campaign.

​
The unsubscribe line

Every marketing and test SMS ends with an unsubscribe line carrying the recipient’s own opt-out link. This is how the message stays compliant with Israeli marketing rules.
The unsubscribe line is billed. It is added before the credits are counted, so its characters come out of your 268 character credit budget. The default line adds about 42 characters, and because it is Hebrew it also switches an otherwise Latin message to the smaller 70 character carrier budget.

​
Editing the line

The whole line is one editable field at Settings → Sending Settings → SMS unsubscribe line. It applies to every marketing SMS in the workspace, so only an owner or admin should change it. Inside that field, %%UNSUBSCRIBE_URL%% marks where each recipient’s personal opt-out link goes. The wording, the separator and the position of the link within the line are all yours. The default is להסרה: %%UNSUBSCRIBE_URL%%. The field is capped at 80 characters and cannot contain a line break. A preview beside it shows the finished line and how many characters it adds.
Leaving the token out does not remove the link. A line with no %%UNSUBSCRIBE_URL%% is treated as a plain label and rendered as your label: link, so the opt-out link is still there. Deleting the token is not a way to drop it.
There is one way to lose the link by accident. If you put your own web address into the unsubscribe line, Senderz treats that address as the opt-out destination and does not add its own link. Your URL will not unsubscribe anyone. Do not put a URL of your own in this field.
Type %%UNSUBSCRIBE_URL%% anywhere in the message body and the link is placed there instead. Nothing is appended at the end. The composer preview shows this immediately.

​
Turning it off

The SMS template editor has an Include unsubscribe link switch, on by default. Turning it off for a template stops the line being added to messages built from that template, and removes it from the credit count.
Only turn this off when the message is genuinely not marketing. Israeli law requires an opt-out on marketing SMS, and Senderz will not add one back for you.

​
Test sends

Send a test from the campaign to a phone number you control. A test SMS:
  • costs credits, at the same rate as a real send
  • goes out under your approved Sender name, and fails if the name is not approved
  • is checked against the suppression list, so a number that opted out will not receive one
  • carries the unsubscribe line, so what you see is what recipients get
  • skips consent, quiet hours and frequency caps, because you are previewing your own message
Body links in a test are not shortened, so the test message can be slightly longer than the real send. Marketing SMS to Israeli numbers is regulated. Senderz enforces it at send time, not in the interface, so nothing you build in a campaign can produce a non compliant send.
A marketing SMS to a contact who is not subscribed on the SMS channel is skipped with No marketing consent. Every consent change is written to the contact’s consent log with its source, time and channel. See Consent.
A reply of stop, stopall, unsubscribe, cancel, end, quit, הסר or הסרה unsubscribes the number within seconds. The reply must be that word on its own. Extra words in the reply are not treated as a STOP.A STOP suppresses the SMS channel only. Email, push and WhatsApp consent for the same person is untouched, because those are separate permissions.One STOP is honoured across every workspace holding that number, up to 50 workspaces.
A suppressed number is skipped before anything else, before consent and before the wallet, so it never costs a credit. Numbers land on the suppression list from a STOP reply, a manual unsubscribe, an invalid number reported by the carrier, or an operator blocklist entry.A number that soft bounces 3 times within 30 days is suppressed automatically.Review and lift entries under Contacts → Suppression list.
A contact receives at most 3 marketing SMS per day and 10 per week, counted in Israel time. Over the cap, the send is skipped with Frequency cap reached. Transactional messages do not count and are not capped.

​
Quiet hours and Shabbat

Marketing SMS to Israeli numbers does not go out between 20:00 and 08:00 local time, or during Shabbat. Shabbat is calculated from real Jerusalem sunset, with candle lighting and havdalah offsets, not a fixed clock time.
These messages are deferred, not dropped. The send waits and goes out when the window opens. Senderz retries in steps of at least 15 minutes, up to 16 attempts across 4 days. Only if the window never opens in that time does the message finally fail, reported as Send window expired.
You can narrow the window further under Settings → Sending Settings, and per campaign. A workspace window can only add blocked hours. It can never reopen an hour the law closes. Full detail in Quiet hours and Israeli compliance.

​
Transactional SMS

Transactional SMS covers messages the recipient asked for: order updates, delivery notices, one-time codes. Send them through the Public API with POST /public/messages/sms, or send codes through the OTP API. Transactional SMS still goes through:
  • the SMS credit wallet, at the same credit rate
  • the Sender name check, so an unapproved name still fails
  • the suppression list, so a number that replied STOP will not receive one
Transactional SMS skips:
  • the marketing consent check
  • quiet hours and Shabbat
  • frequency caps
  • the unsubscribe line
  • automatic link shortening and click tracking
Do not send marketing content through the transactional path. It is a compliance question, not a technical one, and suppression is the only guard that still applies.

​
Why a send fails or is skipped

Every message that does not go out is recorded against the campaign with a reason. The common SMS ones: Skipped messages do not cost credits. A hold placed before a carrier rejection is released automatically.

Sender IDs

The full request, review and revoke flow.

Campaigns

Build and schedule a one-time SMS send.

Automations

Trigger SMS from behaviour.

Consent

Opt-in, opt-out and the consent log.