How does bulk messaging and consent compliance work?
Bulk messaging checks every recipient’s consent status before an email goes out to a segment, and drops anyone without consent from the send list — that is a block, not a warning. Templates, quota and delivery state sit on one screen, so a fine that lands on you is prevented by a system that lets you NOT send rather than one that hopes you remember to check.
Who uses it
Any business that emails announcements, reminders or campaigns to its customer base: hotels and restaurants sending booking reminders, agencies announcing campaigns, schools sending attendance notices. The shared need: knowing who has actually consented before you send, and proof that a send really went out.
How it works: the consent gate, İYS compliance, transactional vs. commercial
A consent gate runs at send time: a recipient with no e-mail-channel consent recorded in consent management never triggers a provider call — there is no override flag. Under Law No. 6563 on the Regulation of Electronic Commerce, sending a commercial electronic message to a recipient requires prior consent, and that consent is collected in one national record run by the Turkish Ministry of Trade — İYS (İleti Yönetim Sistemi, the “message management system”); service providers must query this record before sending, and recipients can grant or withdraw consent from a single point (see the Ministry of Trade’s İYS page). Rotenta’s send gate works against this national record, not just its own local ledger: even a locally-consented recipient is dropped if İYS shows no matching consent.
Every commercial message body must carry an opt-out link; a message built without one is refused at creation time, and an incoming opt-out closes that channel’s consent immediately. A transactional message (say, a booking confirmation) is exempt from this consent gate — a required message like a school attendance notice must not get stuck behind the same gate as a marketing campaign, so the transactional/commercial classification is a mandatory field on every message.
Delivery state is kept as evidence — queued/sent/delivered/failed — and a queued message is never shown as “sent.” Two customer cards sharing the same e-mail address count as one recipient in the send preview. Templates are versioned and the sent body is archived, so editing a template later never rewrites a past send.
Example
Example: A hotel prepares a seasonal campaign for an 800-person list of past guests. The send preview shows how many are consented, how many will be dropped as unconsented, and how much of the monthly send cap this uses — nothing goes out at this stage. The campaign sends to 620 consented recipients; 3 click the opt-out link, and that closes their channel consent the same day. The send report lists, with evidence, who received it and who bounced.
How it is done in Rotenta
- Marketing builds a recipient list on the Bulk Messaging tab inside customer management, filtering by tag or segment.
- A versioned template is picked or written; a body with no opt-out link cannot be saved.
- The preview shows the deduplicated recipient count, how many will be dropped as unconsented or unconfirmed in İYS, and the remaining monthly quota — nothing sends at this step.
- The send starts; each recipient’s state (queued/sent/delivered/failed) shows in real time on the card.
- An incoming opt-out closes that channel’s consent immediately inside the consent management ledger.
- The send report exports from reports with per-recipient status; personal-data columns show or hide by permission.
- A recurring send (say, a T-1 reminder) binds to a trigger inside workflow automation instead of being rebuilt by hand every time.
Quota, export and evidence
Before sending, the preview shows how much of that month’s send quota it will use; the quota is a firm setting, and hitting it stops the send with a machine-readable message instead of a surprise extra charge. Every template is versioned and the sent body is archived, so editing a template later never rewrites a past campaign. The send report, along with who prepared and approved it, also lands in the record roles, permissions and audit trail produces — so an audit’s “who sent this, when, with what approval” question has an evidenced answer.
Frequently asked questions
Can I send a campaign to a recipient with no consent?
No. The consent gate runs at send time; a recipient without consent never triggers a provider call. This is a code-level block, not a warning.
Is it enough if my local consent record is up to date?
No. Sending is checked against İYS, the national record; even if your local ledger shows consent, the recipient is dropped if İYS has no matching record or the last confirmation is stale.
Does a school attendance notice go through the same consent gate?
No. Transactional messages — attendance notices, trip notifications, anything you’re required to send — are exempt from the commercial consent gate; classification is a mandatory field on every message.
What happens when an opt-out comes in?
That recipient’s consent on that channel closes immediately and the change is recorded in consent management; no further commercial message goes to that recipient.
Can I export the send report?
Yes, with per-recipient status; personal-data columns show or hide based on your permission. See how the module connects to the rest of the platform in our module guide, check coverage on pricing, or reach us through contact.
More in this category
- How does vehicle and driver document tracking work?
Warns on an expired or upcoming vehicle/driver document, and blocks trip assignment when a required one has lapsed.
- How does the vehicle and driver (fleet) module work?
One ledger for your vehicles and drivers that trips assign from and that answers who is available, when.
- How does recurring shuttle planning work?
A route and weekly plan are defined once; public holidays are skipped, one-off exceptions post as billing deductions, and off-plan extra trips enter the statement as their own line.
- How is e-invoicing (e-Fatura/e-Arşiv) integrated?
Tax ID and scenario data carried on the invoice record flow straight through; send status and the tax authority's reference show on the panel in real time.
- How does the Excel data import module work?
A module that validates and previews your existing spreadsheets, isolates the bad rows, and can undo an import if needed.
- How is workflow automation set up?
Trigger + condition + action rules ship as ready templates, every run is recorded as evidence, and a rule bound to a closed module shows as visibly inactive, never silent.
- How does the consent management module work?
Records customer consent per channel, ties sensitive fields to explicit consent, and exports to Turkey's İYS registry.
- How does the customer management (CRM) module work?
One card for people and companies, encrypted sensitive fields, tagging and notes — how Rotenta's CRM module is laid out on screen.
- How does the accounting module: accounts, invoices, cash work?
Current account, invoice, cash and instalment tracking brought together in one accounting module, from proforma to day-close.
- How do PDF outputs and letterhead documents work?
One core engine that puts your letterhead on invoices, statements, receipts and passenger lists, and logs every document it produces.
- How are staff shifts and timesheets managed?
Timesheets are produced from realised trips, deductions carry evidence and a dispute path, staff on leave cannot be reassigned, and period close freezes the past.
- How do reports and profitability analysis work?
Every list you own exports at full fidelity, aging buckets of 0-30/30-60/60-90/90+ days sit on one screen, and period profitability drills all the way down to the source trip.
- How does booking and capacity management work?
A resource x time-slot booking engine that blocks double-selling, tracks option deadlines and converts a confirmed request straight into a trip or service record.
- How do roles, permissions and the audit trail work?
Roles decide who can see what, and the audit trail keeps a permanent record of who changed what and when.
- How does the trip and transfer operations module work?
One record that follows a trip from planning to completion, carrying its passengers, driver, vehicle and price lines together.
- How do contracts and progress billing work?
The contract is the single price source; progress billing is calculated automatically from trip records, penalty clauses apply on their own, and an approved statement becomes an invoice in one click.
- How do quotes and proposals work?
Quote lines read from the published rate list, margin is visible to authorised users, a five-state lifecycle is tracked, and an accepted quote converts to an invoice in one click.
- How is U-ETDS reporting done?
Every trip already carries the fields U-ETDS reporting needs; send status shows on the trip card and never shows an optimistic 'sent' before it is confirmed.
- How does the AI assistant module work inside the panel?
An in-panel assistant that works within your own permissions, masks personal data, and asks approval before every write.