← All features

Operations · Communications

Send the right message to the right members.

The pool closes Thursday. That note goes to the people who swim on Thursdays, not to everyone with an email address, because the list is built from what they actually do here.

What it helps with

What your team can do here.

Scheduled sends

Write it Tuesday, send it Thursday.

Schedule a one-off message for a date and time, or set up a standing one that keeps going without you. The standing ones are a short list you pick from rather than a builder you have to learn: welcome a new member, welcome a new portal signup, remind people about a trip, wish someone a happy birthday, or reach out to members who have stopped coming.

  • One-off sends, scheduled for the date you choose
  • Five standing recipes, each with your own template
  • Pause one when it stops being the right message

Audiences

Everyone who has not been in since March.

Twenty-one things you can filter on, and they are the things you would ask out loud: who is in this group, who joined in the last sixty days, who has not been seen in ninety, who is registered for something coming up, who owes money, what tier they are, how old they are, what zip code they live in, whether we even have an email for them. Stack them together and save the result under a name you will recognize next month.

  • Not seen in ninety days, joined in the last sixty, active this week
  • In a group, registered for something upcoming, carrying an unpaid balance
  • Tier, age, household, city, state, zip, and demographic fields you collect

Templates

The closure notice you already wrote once.

Save the bulletin, the closure notice, the welcome, and the trip reminder as formats you reopen instead of rewrite. Merge fields put the member's own name and your organization's details into the text, so the greeting is a name and not a placeholder that went out as one to four hundred people.

  • A template library that belongs to your workspace
  • Merge fields for member and organization details
  • Sender name and reply-to set once, for every message

What happened after

The address that bounced comes off the list.

Your provider reports back on every message: delivered, bounced, or marked as spam. A hard bounce or a spam complaint suppresses that address automatically, with the reason recorded, so you are not sending to a dead mailbox for two years. What you will not see is opens or click-through, because NestPoint does not track them. Anyone quoting you an open rate is quoting a number that stopped meaning much some time ago.

  • Delivered, bounced, and spam-complaint results per recipient
  • Hard bounces and complaints suppressed automatically, with the reason
  • No open tracking and no click tracking, deliberately

A typical workflow

Write it once. Send it to the right people.

The list is not a spreadsheet someone maintains. It is a question asked of the records at the moment you send.

  1. Open the template. Start from the closure notice or the bulletin you already wrote, and change what is different this time.

  2. Build the audience. Stack the conditions until the count at the bottom looks like the group you had in mind.

  3. Look at the count. Four hundred when you expected forty means the audience is wrong, and it is much cheaper to find out here.

  4. Schedule it. Now, or Thursday at seven, when people actually read things.

  5. Check what came back. Delivered, bounced, complained. The bad addresses take themselves off the list.

Common questions

What teams ask before getting started.

The newsletter nobody had to mail-merge.

See how an audience, a template, and a send date turn into a message that went to exactly who it should have.

Card required. Cancel anytime.