Follow-up point
BRP Configuration → Marketing activities → Follow-up point
- 1 Description
- 2 Filter
- 3 Variables for messages
- 4 Templates for Messages (examples)
- 4.1 Birthday greeting
- 4.2 New customers
- 4.3 Overdue invoice
- 4.4 Overdue invoice (recurring card payment)
- 4.5 Missing valid direct debit E-consent
- 4.6 Value card expires in X days
- 4.7 Subscription expires in X days
- 4.8 Price list expires
- 4.9 Payment Card Expires
- 4.10 Missing Approved Card Consent
- 4.11 Event Starts
- 4.12 Contract Reminder
- 4.13 Unsigned Digital Agreement Reminder
- 4.14 Booking Reminder
- 4.14.1 Channel: SMS
- 4.14.2 Channel: Email
- 4.14.3 Channel: Push notification
- 4.15 Faulty Autogiro Consents (direct debit)
- 4.16 Subscription Already Exists (via partner)
- 5 Marketing Activity
- 6 Test
- 7 Error Messages
Description
This feature is used to send automated messages or create marketing activities. For example, it can be used to send birthday greetings or reminders to customers who haven’t trained in a while.
Contact BRP Support for assistance in activating Automatic Follow-up.
Name
Enter a name of this follow-up point.
Active
Determines whether the follow-up point should be used or not.
Channel
SMS, Email, Push notification, Carma, MailChimp, or a marketing activity assigned to the customer’s account manager. Customers with the “No mass communication” flag will be excluded from SMS, Email, and Push notifications. Customers without an email, mobile number, or the app will not receive messages via those respective channels.
Filter
Predefined selection template used to determine which people will be included in the sendout.
Parameters
Parameters sent to the filter. The available parameters depend on the selected filter (see “Filter” above).
Time point to run each day
Specifies the time of day the follow-up should run — e.g., SMS sent at 10:00 AM.
Each follow-up point is configured to run only once per day. If the scheduled time is changed after it has already run, it will not trigger another sendout on the same day. This prevents the risk of unintentionally spamming customers with multiple reminders of the same type.
Companies
Specify which companies should be included in the follow-up point (if needed).
Facilities
Specify which facilties should be included in the follow-up point (if needed).
Product label
Only includes people who have a subscription with the selected product label. (Note: There are exceptions where product labels are used for other purposes—see below.)
Person group
Only includes people who belong to the selected person group.
Person categories
Only includes people who belong to the selected person categories.
Send even if consent for mass sending is missing
Enables messages to be sent even if the customer has not given consent to mass communication.
Messages
Specify the specific message that should be used. It is possible to add one per language, see the “Message examples” section below.
When a follow-up point is executed, SMS, Email, Push notifications, or marketing activities are generated based on the selected channel. For SMS, Email, and Push, a marketing activity is also created for the customer for follow-up purposes.
To see which people will be included in a follow-up point, click "Test selection". This will run the selection filter and display the results in a person list.
To preview the message, select it and click "Test message".
Filter
Each filter defines criteria for selecting which individuals should be included in automated communications like reminders, notices, or internal tasks.
Name | Selection | Parameters |
|---|---|---|
Birthday Greeting | People with birthdays today and active subscriptions. Ignores product labels. | – |
Booking Reminder | Person with a service or group activity booking in X days. Optionally filter by booking creation time. |
|
Contract Reminder | Person has a contract time booked in X days. |
|
Customer Type Expires | Active subscribers with selected customer type ending in X days. |
|
Due but not sent invoice | The person has an unpaid, not sent invoice with a minimum amount of Y and due date has passed with at least X days. Should only be used for invoice type 2 & 4 (direct debit and RCP). If noOrganizations=true, the invoice reminder will only be sent to invoices without an organization connection. |
Values on the types parameter is entered with & *=all, regardless of type |
Due invoice (recurring card payment) | Overdue recurring card invoice passed due date by X days. |
|
Due Invoice (Organization) | Unpaid invoice for organization expired X days ago. |
|
Due invoice reminder with invoice report - Email Only | Sends copy of invoice (a PDF of the invoice is attached to the email) X days before or after the due date of the invoice. The only available channel for this follow-up point is email. It is also mandatory to select which report template that should be used (most likely the Invoice report template) since the invoice is attached to the email. |
Values on the types parameter is entered with & *=all, regardless of type To send an invoice copy 7 days before due date, set:
|
Due invoice to responsible |
|
|
Erroneous Direct Debit Consents | Invalid mandate error codes found in past 24 hours. |
|
Event Starts | Participants in an event starting in X days. Uses product label to determine applicable events. |
|
Expiry date for credit card | Persons with a subscription paid with recurring card payments, where the card is expiring next month. It is not possible to filter on product labels for this follow-up point. |
|
Freezing Ends in X Days | Persons with a subscription wutg a freeze period that ends in X days. |
|
Late Invoice Person | Unpaid personal invoice with due date passed by X days. |
|
Membership ends in X days | Persons with a subscription that ends in X days and is not set to renew automatically. Subscriptions must have a ‘debited until’ date. Subscriptions with saved days are always excluded from this filter.
Steps to resolve this:
Canceled subscriptions are not included in the selection. |
|
Missing Profile Images | Users without uploaded profile pictures. | – |
Missing valid Stripe Bacs mandate | This person is the payer for an active subscription that requires a Stripe Bacs mandate but lacks a registered mandate or the mandate's validity date has passed. |
|
Missing Valid Card Consent | Missing or expired recurring card consent. |
|
Missing Valid Direct Debit E-Consent (SE) | Active subscription in Sweden missing autogiro mandate. |
|
Missing E-Invoice Consent (FI) | Missing e-invoice consent for Finland. |
|
Missing PBS Mandate (DK) | Missing e-invoice consent for Finland. |
|
Monthly Message to Employees | Sends message to staff on specified day of month. |
|
New Customers | Created within X days; optionally requires first internet receipt. |
|
New Member | Subscription started X days ago. No prior subscription within maxGap. |
|
New Member X Days Ago and has visited between Y and Z Times | Filter above, with visit count range. |
|
New Person with Lead Source Created | Newly created person with lead source. |
|
No Valid AvtaleGiro (NO) | Active subscription in Norway missing AvtaleGiro mandate. |
|
No visits during past X days | Active subscription but no entry for X days. |
|
Organization connection expires | Organization connection expires in X days. |
|
Overdue invoice reminder | Sent invoice with due date passed X days. |
|
Price List Expires | Subscription with price list expiring in X days. |
|
Price warranty end reminder | Price warranty expires in X days. |
|
Purchased subscription through partner program despite existing | Persons who bought a subscription through a partner program, e.g., Benify or Actiway, despite already having a subscription |
5=Benify
0= if all active subscriptions should be checked |
Reminder of not signed agreement | Agreement requested X days ago but not signed. |
|
Subscription - First Debit Made | Triggered after first charge on subscription. |
|
The product was purchased {0} days ago | Product bought X days ago. The person purchased a product x days ago. Note: Recurring payments are also classified as purchases and will trigger this follow-up point, such as charges for ongoing subscriptions. |
|
Unlocked time report reminder | Reminder to employees with unlocked time reports. |
|
Overdue invoice reminder | Invoice overdue by X days. |
|
Unpaid overdue invoice counting bank days | Invoice overdue by X banking days. |
|
Value Card Expires in X Days | Value card expiring in X days with min amount left. |
|
Variables for messages
All filters include the parameters person, organization, and unit, which represent the full Person, Organization, and Facility (Unit) objects.
The unit is retrieved from the person. Note that person and organization are never set at the same time.
The data available for use across all filters is described below:
Variable | Description |
|---|---|
${person.firstName} | The person’s first name |
${person.lastName} | The person’s last name |
${person.customerNumber} | The person’s customer number |
${person.priceList} | The person’s price list |
${organization.name} | The name of the organization |
${organization.orgnumber} | The organization number |
${organization.homePage} | The organization website |
${unit.name} | The name of the facility |
Filter-Specific Variables
Some variables may not always contain a value, for instance internetInfo is empty if it’s not configured for the event. For such variables, insert an exclamation mark like $!{internetInfo}, otherwise the tag itself (${internetInfo}) will be visible.
Filter Name | Parameter Name / Description |
|---|---|
Birthday Greeting |
|
New Member X Days Ago |
|
Not Trained in X Days |
|
Subscription Expires in X Days |
|
Value Card Expires in X Days |
|
Missing Approved Autogiro Consent (SE) |
|
Missing Approved AvtaleGiro (NO) |
|
Overdue Invoice |
|
Overdue Invoice (Organization) | Same parameters and notes as Overdue Invoice |
Overdue Invoice (Recurring Card Payment) |
|
Price List Expires |
|
Customer Type Expires |
|
Missing Approved Card Consent |
|
Event Starts |
|
Contract Reminder |
|
Unsigned Digital Agreement Reminder |