Engagement · SaaS

Maqetin emails an account that is close to its plan limit.

For an account close to its plan limit. It leads with the account's own numbers and names what the next plan adds. A journey sends it with no wait.

The email.

A sample to adapt: change the names, the product and the button to yours.

FromShelfwise <hello@mail.shelfwise.app>SubjectYou have used 9 of 10 shopsPreviewThe next plan covers up to 25.

Hi Sarah,

Shelfwise now runs 9 of the 10 shops your plan includes. The next plan covers up to 25 and adds stock alerts.

Compare plans
Shelfwise, Austin

Sample workspace: Shelfwise, stock and invoicing software for independent shops, based in Austin.

How it is sent.

The journey starts when your app sends limit.approaching and sends the email with no wait.

Trigger
Limit approaching
limit.approaching
Send email
Send the next plan
Exit
Exit

Events to send.

Your app sends one event.

limit.approaching
Starts the journey. Send used and limit with it, and the email can print the numbers.

Check before you send.

  • Lead with their numbers. Send the count and the limit in the properties of the event.
  • Choose the re-entry rule. With "once", an account gets one prompt. With "every N days", it can enter the journey again after N days.
  • Reach the person who pays. Save the payer's user id as a trait of the person in the journey. The payer needs a profile with an email address. Set the email step to send to that trait.

More engagement templates.

Tell accounts about the next plan before they need it.