Frequently asked — honestly answered

Your first SMS goes out minutes after signup — from the dashboard or the API. Production email takes as long as your DNS: add the SPF/DKIM/DMARC records we generate, and the built-in checker verifies them live. Most teams send their first real campaign within the first week.

Prepaid balance, per-message rates by channel and destination, and your exact rates are always visible via the API — what it returns is what sends deduct. Plans add monthly quotas; pay-as-you-go has no subscription at all. No seat fees, no contact-count surprises hidden in fine print.

Yes — and in the right order. Import your suppression list first (bulk import is built in), then contacts via CSV or an integration; duplicates merge on email/phone instead of multiplying. Consent state comes along where the source provides it, so you never message someone who already said no.

The platform monitors every vendor's live delivery performance per destination. When a route degrades, sends fail over to the next-best route automatically, the incident is visible in vendor health, and messages that ultimately fail wait in a dead-letter queue for retry — they don't disappear.

No. Full data export as structured JSON is one API call, usage exports as CSV, and warehouse sync can stream profiles and events to your own database continuously. An exit-friendly platform is a platform you can trust while you stay.

Not for the daily work: campaigns, journeys, segments, templates and forms are all visual, and the wiki's animated guides walk through every flow click by click. Developers plug in where you want depth — the API covers everything the dashboard does, and an AI assistant can integrate it for you from our machine-readable docs.

In the EU. GDPR tooling is built into the product — export, anonymisation, retention policies and an audit log — not sold as an add-on. See the DPA and sub-processor list under legal.

Because contact-based pricing punishes you for growing your list and rewards keeping dead contacts. We bill for what you actually send. Contacts are free up to 20,000 (60,000 on Scale) — grow your list as much as you like.

Each family has three price points with the same features, users and contact limit — only the included send volume grows. You pick a higher band to get more to send for, and move up a tier only when you need more CDP features, channels or seats.

It depends on the region. In North America, Europe and Oceania every plan includes an SMS/RCS quota, and overage is billed per message at transparent rates. In other regions SMS/RCS is pay-as-you-go from message one, at a flat local rate — because carrier costs there make bundling impossible. See the regional breakdown below.

Annual is 12× the monthly price — no price discount, because our prices are already low. Instead you get +10% included send volume (email and SMS/RCS) for the whole year. Available on Growth, Business and Scale.

Only above 20,000 contacts (Growth/Business) or 60,000 (Scale). It's a small monthly step — +99, +249, +499 or +899 DKK — independent of your volume band, and still far below what contact-priced tools charge at the same list size. Free is exempt entirely.

Yes — EU data residency is the default on every plan, with dedicated residency options on Enterprise. See Trust & security for the full picture.

SMS, RCS, WhatsApp Business, email, programmable voice and mobile push — all through the same send endpoint.

You define an ordered fallback list per message or template. If delivery isn't confirmed within your window, WeZend retries on the next channel automatically.

Yes. WeZend supports bring-your-own SMPP and vendor credentials alongside built-in providers, with per-route cost control.

190+ countries with local routing and compliance handling. Coverage and per-route pricing are visible in your dashboard.

Yes — low-latency transactional routes are prioritised for one-time passwords, with delivery analytics per route.

Yes — WeZend uses the WhatsApp Cloud API. You get compliant messaging, template approval and conversation-based pricing visibility.

Absolutely. Route inbound WhatsApp into an AI agent that reads the customer profile and responds, hands off to a human when needed.

Yes. Point WeZend at your own SMTP/API endpoint, or use our sending infrastructure — the deliverability tooling works either way.

Double opt-in, granular consent and one-click unsubscribe are built in and enforced before every marketing send.

A warehouse stores data for analysis; the CDP resolves identity and serves a live profile that automation and messaging act on in real time. WeZend can sync to your warehouse too.

In the EU by default, with data-residency controls, retention policies and full GDPR export/erasure support.

In real time. As soon as an event changes a customer's eligibility, their membership updates and any attached journey can trigger.

Yes — a single journey can send email, then SMS, then WhatsApp, branching on whether the customer engaged with each.

AI runs on your data within your EU tenant, respects consent and retention rules, and never trains shared models on your data.

Yes. Set confidence thresholds so low-certainty actions require approval, and route any conversation to a human at any point.

Yes — export to your warehouse (BigQuery, Snowflake, Redshift) or pull via API for your own BI tools.

The message falls back to SMS automatically, so every recipient still gets it.

Yes — voice OTP is a reliable fallback when SMS can't be delivered, using text-to-speech.

Yes — push is a first-class channel node, so a journey can move from push to email to SMS.

Yes — the platform checks consent, quiet hours and frequency caps before every send.

Snowflake, BigQuery and Redshift, with more via the open API. Sync runs both ways.

A randomly withheld set of customers who receive nothing, so you can measure what your messaging genuinely added.

Claude (claude.ai remote MCP connectors, Claude Desktop and Claude Code via the @wezend/mcp bridge), ChatGPT (a GPT Action generated from /v1/mcp/openapi.json in one click) — and any other client that speaks MCP or plain REST.

No. The three tools that send or activate refuse to run without an explicit confirm parameter, and even confirmed sends pass every dashboard guard: suppression lists, quota, budget caps, card-on-file and the audit log.

By your API key: the account identity always comes from the key, never from the model, so an assistant can only see and touch the account the key belongs to. Keys are created and revoked on the Connect AI page in the dashboard.

No. AI Studio always produces a draft — a human reviews and sends. It reuses the platform's segment, copywriting and send-time engines, so the draft is real and editable, not a throwaway.

Yes — the same generation is exposed through Connect AI, so you can draft campaigns and journeys from your own assistant and review them in the dashboard.

They receive the message at a sensible default time. As their event history builds, the timing sharpens automatically.

Yes — the voice profile is per account, so each brand (or each white-label client on the partner track) carries its own voice.

Your product catalog lives in the platform (synced from your store or added directly), and recommendations match CDP behaviour against it. Keep the catalog current and the picks stay relevant.

You generate them in your e-commerce or POS system as single-use codes, then upload the list into a pool. WeZend hands them out; your store validates them at checkout.

Top it up with more codes before a large send. The platform claims one per recipient, so size the pool to your audience.

It narrates your real digest numbers, and the fallback path is fully deterministic rules over those numbers. The recommendation is a starting point for judgement, not a command — you stay in the driver's seat.

A customer texting your keyword is an explicit, documented opt-in — among the strongest consent signals available. The platform records when and what they sent. As always, confirm your specifics with your own legal advice.

Delivery and opens are tracked automatically. Automated inbox-vs-spam folder detection needs IMAP access to your seed inboxes; until that ops step is set up for your account, folder placement is recorded manually.

Pages publish to a hosted URL out of the box. Custom-domain and white-label options are part of the partner track — talk to us about your setup.

Owners and admins — anyone with the `approve` capability. Members can create and submit but not release their own sends.

Yes — build a template once and reuse it. The gallery gives you a head start; your own saved templates keep your team consistent.

Mailbox providers send them to the address in your DMARC record's `rua=` tag. Point that at an inbox you collect, then upload the reports to WeZend to read them.

No — it's a pragmatic pre-flight against common signals, not a verdict from Gmail. Placement also depends on domain reputation, authentication and engagement. Use it to catch obvious problems early.

DMARC at enforcement (p=quarantine or p=reject), a square SVG logo hosted on your domain, and a BIMI DNS record. Some inboxes also require a verified mark certificate.

Each request is signed with an HMAC of the timestamp and payload using your endpoint's secret. Recompute the signature on your side and compare — if it matches, it's genuine and untampered.

You own the brand and the relationship. Clients never see a third party, you set the price and keep the margin, and you get six channels plus a real CDP — not email-plus-a-little-SMS. And your clients' data sits in the EU, which most contact-priced US tools can't promise cleanly.

You take a volume discount across all your sub-accounts (or a revenue share), so your cost is below the public list price — and you decide what to charge each client on top. The regional SMS model applies per client's destinations. Talk to us and we'll model it on your actual client mix.

Yes — campaigns, journeys, segments, templates and forms are all visual, per client. Developers only plug in where a client wants custom event tracking or a deep integration, and even that an AI assistant can wire from our machine-readable docs.

A real white-label. Your clients use the platform on your domain, under your brand, and never encounter WeZend — plus you choose revenue share or a volume discount as the commercial model. The multi-tenant partner engine is already in the platform, not a promise.

You get one consolidated invoice with a per-client breakdown. What you charge each client is entirely yours to set — WeZend bills the partner account at your agreed partner rates, and the regional SMS model applies per client's destinations.

Yes — partner onboarding includes a migration plan, and the same step-by-step guides that cover Klaviyo, Mailchimp, Twilio and the rest apply per client. Suppressions first, parallel running, honest warm-up.

Flows are rebuilt as WeZend journeys — the concepts map 1:1 (triggers, delays, conditional splits, goals). The migration guide walks through each standard flow type, and the AI copilot can draft them from a plain-language description.

The import itself is free on every plan, including Free. Most teams run both platforms in parallel for one billing cycle while warming the new email domain — the pricing calculator shows exactly what your volume costs on WeZend.

The basics are the same: import contacts, pick a template, send. The depth (CDP, journeys, experiments) is there when you need it, with guided flows and product tours — and you can run the whole platform in plain language via Connect AI.

Rebuild them as WeZend lead forms (hosted or embedded) with double opt-in built in, and switch the endpoints your site posts to. The migration guide covers the cut-over order so no signup is lost.

Small: the send call maps nearly field-for-field (the migration guide has side-by-side examples), and delivery webhooks follow the same pattern. Most teams swap the client in a day and spend the rest of the week deleting the tooling they no longer need.

Alphanumeric sender IDs are re-registered on WeZend (a quick approval step). Number porting depends on the number type and country — ask us before you migrate and we'll map it out.

For most mid-market workloads, yes — same event-driven architecture, same experiment discipline. If you're orchestrating billions of messages monthly across dozens of brands, run a pilot first; the Enterprise tier exists for exactly that conversation.

Technically any time — the import is a data export away. Commercially, most teams start the pilot a quarter before renewal so the switch decision lands with real numbers on the table.

Templates port over as HTML with variable substitution — the migration guide maps SendGrid's substitution syntax to WeZend's. Test sends against a seed list before switching the API key.

Not at all if you sequence it: verify your domain on WeZend (new selectors, so nothing collides), warm it up alongside SendGrid, then move traffic gradually. The DNS checker validates every record live.

For contacts, suppressions and lists, yes — the migration wizard maps Brevo's export directly. Templates and automations are rebuilt (usually the same week), and the guide sequences the cut-over so nothing sends twice.

Yes — Free includes unlimited contacts and a monthly send allowance, no credit card required. Paid tiers start at 79 kr/month.

The standard ones (welcome, abandoned cart, win-back, post-purchase) exist as journey patterns you can adapt, and the AI copilot drafts custom ones from a description. The migration guide maps ActiveCampaign concepts to WeZend's.

WeZend is a messaging and customer-data platform, not a sales CRM. Keep your CRM (or ActiveCampaign's, or HubSpot's free tier) and connect it as an inbound source — deals and stages flow in as events and fields.

No — WeZend attributes revenue to campaigns and journeys from its own event stream, and conversions can be posted back to HubSpot as events, so both report the same truth from their own angle.

Not at all. Most teams move one program first — often SMS or the newsletter — prove the economics, then migrate the rest at their own pace. The sync keeps both sides consistent throughout.