Consent with date and source
When you switch consent on in the contact card, Elbuz saves the date and the source. Later you can show when the customer agreed.
Sales and customers department one of the departments in your AI company
Ecommerce email marketing, SMS campaigns and Telegram broadcasts straight from your Elbuz customer base: pick recipients with a filter, start sending and see who read it.

Email marketing for ecommerce without a separate newsletter tool: Elbuz collects the addresses that have consent and sends the emails itself.


Emails go out from your connected mailbox. Recipients, orders and purchase history live in the same database.
Marketing emails need a lawful basis in the EU and a working opt-out everywhere. Elbuz records when and where consent came from and removes it on unsubscribe.
When you switch consent on in the contact card, Elbuz saves the date and the source. Later you can show when the customer agreed.
The newsletter goes only to contacts with active consent. Anyone who unsubscribed drops out of every next campaign.
Gmail and Yahoo show their own “Unsubscribe” button on Elbuz newsletters, and you add an unsubscribe link to your template. The date and source of the opt-out are kept in the card.
In the EU, the GDPR requires you to be able to show that a person consented (Art. 7(1)) and to make withdrawing consent as easy as giving it (Art. 7(3)); national rules based on the ePrivacy Directive generally require prior consent for marketing emails and texts, with an exception for existing customers and similar products. In the US, the CAN-SPAM Act does not require prior consent for email, but every commercial message needs a clear way to opt out, a valid postal address, and opt-out requests must be honored within 10 business days.
As of 01.11.2026. Sources: Regulation (EU) 2016/679 (GDPR) on EUR-Lex, CAN-SPAM Act: A Compliance Guide for Business (FTC). Not legal advice.
SMS campaigns and order texts through the SMS gateway you already use.
Twilio, Infobip, SendPulse or eSputnik: enter the service, the key and the sender once, and texts go out on their own.
Through Infobip or eSputnik a message can go to Viber first and only then, if it is not delivered there, as a regular SMS.
Every attempt and every response from the service: no balance, wrong sender name, no phone number.

For marketing texts the same rule applies as for email: get consent first. In the US, carriers and the TCPA expect prior express written consent for promotional SMS.
The message goes where the customer already buys and chats.
If your store runs on Elbuz CMS with a Telegram bot connected, you reach the customers of your Telegram store: text, an image and a link button to everyone who started the bot, with a test send to yourself and a log. People who blocked the bot get nothing.
Replies to your campaigns from WhatsApp, Instagram, Messenger, Telegram and Viber arrive in one window next to the website chat. You answer through the same channel, see customer service.
Messages that go out on their own: after an event, not on a schedule.
A confirmation email or an SMS with the order number as soon as the status changes.
The reminder to customers who leave products in the cart is sent by the store on Elbuz CMS itself, with a CMS module.
Personal emails to customers who have not bought for a long time, suggested in AI Pulse.
Event-based messages are set up with automation rules: on a new or changed order, Elbuz sends the email or SMS from your template.
Sending newsletters, offers and reminders to the customers of your own store and seeing who read them. In Elbuz you do it straight from the store's customer base, without a separate newsletter tool: pick recipients with a filter, and the report shows who received and opened each email.
Filter people in “Contacts” by group, stage or purchases. Elbuz takes only addresses with consent, removes duplicates and sends the emails itself with pauses, so they do not land in spam. Emails go out from your connected mailbox.
For sending to your own customer base, yes: recipient filter, queue with pauses (up to 20 emails per run), a “Sent” and “Viewed” report for every recipient, and unsubscribe. Everything runs on the same database as orders and purchase history. Elbuz does not sell or rent email lists.
Elbuz gives you the tools: consent with date and source in the contact card, sending only to contacts with consent, and one-click unsubscribe that removes consent. The GDPR requires you to be able to prove consent and to make withdrawal as easy as giving it. Whether you have a lawful basis for a given campaign is your responsibility as the sender.
Twilio, Infobip, SendPulse and eSputnik, among others. Connecting takes three fields: service, key and sender. Through Infobip or eSputnik a message can go to Viber first and then as a regular SMS. The log shows every send and the reason if the service refused.
Yes, if your store runs on Elbuz CMS with a Telegram bot connected: a broadcast to the bot's subscribers with text, an image and a link button, a test send to yourself and a log. People who blocked the bot do not receive it.
With a rule: when a customer order is added or changed, Elbuz sends the customer an email or SMS from your template. The abandoned cart reminder in a store on Elbuz CMS is sent by a CMS module.
Sending has no separate fee: it is part of one Elbuz plan together with the CRM, catalog and feeds. Plans start at €87 a month and depend on the number of products and users; one user is included in the base plan. SMS are paid to your SMS gateway at its rates. See pricing.
Yes. The first 14 days after sign-up are free, and you get €50 on your balance, enough to send the first newsletter to your own customer base.
14 days free
The sales and customers department joins your AI company along with every other department. €50 on your balance after sign-up and 14 days for the first campaign.