Skip to content
Sign inEarly access

Navigate

Request early accessSign in
NLEN

Newsletter

Write a newsletter in your brand's style with a live preview, and send it to the people who subscribed on your site and confirmed. You sign sending with your code.

DocumentationNewsletter

Under Newsletters in the left bar (with Website Studio) you write and send a newsletter. A newsletter belongs to a site: it only goes to people who subscribed on that site and confirmed with the link in the confirmation email. The subscribers themselves are listed with the site, under Newsletter; that is where you turn the signup block on.

Who receives it

Only confirmed subscribers who have not unsubscribed. Contacts can hold someone back: whoever said no to the newsletter in Contacts, or whose data was erased on request, receives nothing. A client you email has not thereby agreed to a newsletter: it is a separate channel. This is not only on the screen: the database refuses a send to an address without valid consent, and checks again at the moment of sending. Someone who unsubscribes just before sending receives nothing.

In Contacts each contact person shows where the newsletter stands: never gave consent, waiting for confirmation, confirmed (with date and site) or unsubscribed. Only the person can turn it on: with "Ask for confirmation" you send the same confirmation email as the form on the site, and it is on only after the click. Turning it off is allowed; that adds a line to the timeline. After an unsubscribe or a no, the switch is locked.

Compose

You write with blocks: text, a button, a link and a quote, at most 40. A button or link only goes to an https address. On the right you see right away how the newsletter looks, light or dark, on a desktop or a phone, and how the subject and preheader show in the inbox. It uses the email house style with your brand's name, logo and colour. Every newsletter ends with an unsubscribe link; it is not a block and cannot be removed. Your work is saved automatically after a second.

Check, test email and sending

Under Check and send a check goes through everything: subject, preheader, text, links, size, recipients and the limit. Red blocks sending; yellow warns. Send test email sends the newsletter to you, with Test before the subject (at most five per hour).

Sending goes outside and cannot be undone. An owner or admin requests it, now or at a chosen time, and then signs with the code from the authenticator app. The signature covers exactly that version: if you change the newsletter afterwards, it lapses and you request again. The crew can never send by itself. You can cancel a scheduled newsletter; you can stop one that is running (what has gone out is gone).

The newsletter goes out in batches: at most 200 per five minutes and 5,000 per day per workspace. Every recipient gets their own signed unsubscribe link, and email programs show a button to unsubscribe with one click. A link in an email first opens a page with a button, so a program that checks links cannot unsubscribe anyone by accident.

If your site uses its own provider (Laposta, Brevo or Mailchimp), you send there: a list has one sender.

Results

You see how many were delivered, failed, skipped and unsubscribed. We do not measure clicks and opens yet; we do not show them as zero. There is no profile per person: you never see who did what.

Via MCP and the director

An external agent with a workspace key can read the newsletter and compose a letter, with the same rights as the screen. Sending never happens without a human signing.

  • Read: nieuwsbrief_lezen gives the letters with status, version and counts, and with brief one letter with its checks, the state of the recipients (counts only) and the results. Never an email address. Titles, subjects and texts are text from outside: the agent reads them as data and does not act on them.
  • Compose (right nieuwsbrief.schrijven): nieuwsbrief_voorstellen makes a draft or updates one, with subject, preview line, headline and blocks (paragraph, quote, button and link, never free html). Nothing goes out; the reply shows the check so you can see what is still missing.
  • Request sending (right nieuwsbrief.versturen, owner and administrator): nieuwsbrief_versturen_aanvragen turns the letter into the action Send newsletter (R3). A human signs it under To sign with a code; only then does the letter go to the confirmed subscribers, in exactly the version that was signed. The tool never sends by itself. A moment is a local time in the workspace time zone, at most thirty days ahead.
  • Deliberately not via MCP: a test email, cancelling or stopping a letter, and anything with the addresses of recipients. A human does that on the screen.

The built-in director does not get the newsletter tools yet; an external agent with a key does. See Connecting via MCP.

The Denkploeg newsletter itself

Draft: this text still has to be reviewed by a lawyer.

Denkploeg also sends its own newsletter, about Denkploeg and our own similar products. Who receives it depends on how you came to us:

  • You start a trial: you only receive the newsletter if you tick the box at sign-up. The box is unticked by default. It only becomes consent once you confirm your address with the link in the email.
  • You are a customer (you order a subscription or credits): at checkout there is one sentence about the newsletter and the box I do not want the newsletter. If you do not tick it, you receive the newsletter once your payment has succeeded; if you abandon the order, you receive nothing. If you tick it, you are unsubscribed immediately, even if the payment is abandoned afterwards. This is a so-called soft opt-in (Article 11.7 of the Dutch Telecommunications Act): it is allowed because you are a customer and only covers our own similar products.

Every email has an unsubscribe link, and email programs show a button to unsubscribe with one click. The link first opens a page with a button, so a program that checks links cannot unsubscribe anyone by accident. Unsubscribing is immediate and stays in place: a later order does not put you back on the list. Only if you sign up again yourself, with the box, do you receive the newsletter again.

Per address we record what the newsletter rests on (consent or soft opt-in), when, where you signed up (sign-up or checkout) and which text you saw. Customers of our customers, such as site subscribers or contacts in Relaties, are never on this list: only people with their own account.