Skip to content

PopSQL: limited support.

Migrate now →

Campaigns

One send to lists, over e-mail, WhatsApp or Telegram, with a template, variables, tracking — and what has to be in place before the first one leaves.

Before the first send

  • The workspace owner must have confirmed their e-mail. Until then the Send button answers "confirm your e-mail" and a scheduled send goes back to draft — this is what protects the reputation of the shared sending domain.
  • A sending channel: the workspace e-mail account (or a verified sender domain), the WhatsApp Cloud API, or a Telegram bot.
  • Plan quota: 500 e-mails/month on Solo, 5,000 on Pro, 50,000 on Team, 500,000 on Business.

Compose

A campaign starts from a template (the whole HTML document) or from a body written in the visual editor. Variables `{{name}}`, `{{company}}` and any custom field are filled per recipient, and the value is frozen at send time — editing the contact afterwards does not change what already went out. The e-mail AI, with the workspace's own key, writes or rewrites the body.

All HTML is scanned before it is accepted: scripts, hidden forms and disguised links are refused with the reason.

Send and follow

Send now or schedule. Every message produces a receipt: sent, opened (pixel), clicked, failed and why. The campaign report adds the receipts up per recipient and per list.