Introduction
This will give you the details on how the Automation rule (event) 'User has visited club' works.
Before you begin
This Automation rule is designed to send notifications when a club member has visited the club. This rule is different to the 'Last club visit' Automation rule as the trigger is when the club member visits the club at the time of visit.
When does the rule trigger
This Automation rule will trigger at the time of a club member's visit to the club. This will only trigger on club members who have an active main contract.
Instruction
To design the template, you will need to go to PGM->Automation ->Automation Rules
Press Add automation rule to add a new notification
In Name create a unique name for the automation rule which will briefly describe what the rule is about.
In Action this must be set as Notification (to describe what you want to do; send a notification).
In Event this must be set as User has visited the club.
When this is complete, additional options will appear to customise the rule to suit your needs.
Conditions
Displays what conditions need to be met before the rule can run. Leaving this area blank (i.e. no conditions) means the event will run each time the event happens. Whereas, adding a condition means the event will only run when both the event and that condition are met.
- Match all - This requires all conditions selected to match.
- Match any - This requires at least one condition to match.
Do not use this with "Does not equal" filters
| Token | Value | Example | Notes |
|---|---|---|---|
| [DAYS_AFTER_CONTRACT_START_COUNT] | Numeric | 30 | This condition will trigger the rule based on how many days after the main active contract has started. |
| [ENTRY_DATE] | Date | 31/12/2022 | This condition will trigger the rule based on the entry date, it will only trigger where the entry date equals the token selected. |
| [TOTAL_CLUB_VISITS_COUNT] | Numeric | 100 | This condition will trigger the rule based on how many times the club member has visited the club. Note it is recommended to only use the value 'Equals'. If you use greater than or less than this will trigger the rule each time the club member visits before or after the value set in the condition. |
| [USER_AGE] | Numeric | ||
| [USER_EMAIL] | String | ||
| [USER_FIRST_NAME] | String | ||
| [USER_HOME_CLUB_NAME] | Drop down list | This condition will trigger the rule based on the selection of the club the club member is located in. This is set in the club member profile. | |
| [USER_LAST_NAME] | String | ||
| [USER_NAME] | String | ||
| [USER_NUMBER] | String | ||
| [USER_PHONE_NUMBER] | String | ||
| [VISITED_CLUB_NAME] | Drop down list | This condition will trigger the rule based on the selection of the club the club member last visited. | |
| [PAYMENT_PLAN_NAME] | Drop down list | This condition will trigger the rule based on the selection of the payment plan name. | |
| [PAYMENT_PLAN_CATEGORY] | Drop down list | This condition will trigger the rule based on the selection of the payment plan category. | |
| [PAYMENT_PLAN_TYPE_NAME] | Drop down list | This condition will trigger the rule based on the selection of the plan type. |
Action Details
Describes how the notification will be sent.
- E-Mail is through the email channel, you can add header and footer details to make this personalised.
- SMS is through mobile phone text messaging, please note this is an extra charge per SMS. More information can be found here.
- Push Notification is to send notifications through to the PerfectGym Go 2 App. Please contact PerfectGym if you want to enable the app; this is an additional cost.
- Post is by normal post. It will create a separate template and leave in notifications. This option is removed in version R88.
If you are planning to send out both an SMS and an E-mail, create two separate Automation Rules
From Email – Specify which email the notification is coming from. New email addresses can be set up in PGM->Automation->From email configuration.
From Name – Specify the name of the sender when channel 'E-mail' is selected.
Notification Recipients – This will send the notification to the specified recipient. This list will change depending on the channel selected.
- Users - This will send the notification to the club member the contract was created for.
- Parents - This will send the notification to the parent of the club member the contract was created for. Only available for channel 'E-mail'.
- Reception - This will send the notification to the email address set in PGM->Clubs->List of Clubs. Only available for channel 'E-mail'.
If the member does not have a value in Email or SMS where the notification is being sent to, the notification will not generate.
User Agreement - This field will appear if the Notification Recipient is 'Users or Parents'. This will send the notification to the club member where they have agreed to the user agreement selected.
- If this is left blank, it will send the notification regardless of what user agreements are ticked.
- If this has an agreement set, this notification will only send if the club member has ticked this specific agreement box during registration or when editing their profile. This will also add information on how to unsubscribe to the email where the tag [TEMPLATE_UNSUBSCRIBE_LINK] is used.
Not recommended for use in SMS
Send notifications From/To (HH:MM) - This will allow you to set the timeframes the notifications will be sent. If a notification is to be sent outside of these hours, it will be held until the next time the rule can be sent. If left blank this will automatically send when the rule is triggered.
Delay Notification - This will delay the sending of the notification, this will generate the email first and hold it for that period of time. The time unit determines if the unit is measured in minutes, hours or days. Do not set delays larger than 27 days for this event.
The notification is generated and delayed in a queue, therefore if there is a change during the delay period (even if that makes this notification obsolete), this will not be taken into account, and the original notification generated at the time the event was first triggered will still be sent to the club member.
Send notification not more often than (in days) - This will prevent the notification being sent multiple times in the number of days specified.
Notification content
Press Add content template to create the message you want to send to the club member.
Content template (For Email)
Choose the Language
Create a Subject header
Template (Email only) will allow you to create headers and footers for the email to send
Content - Allows you to create the template content for your notification. If you want to grab information from the system to make it more personalised (like club member name) use the tags below the footer.
Using the text editor, you can also create some additional looks to your text using bold, italic, underline, colours and other functions of the text editor tool.
Press Submit to continue.
Content Template (For SMS / Push Notification)
Similar to the email template above, however you do not need to worry about template. Just remember with SMS that there is a cost per SMS charge (each SMS consisting of 154 characters, so exceeding this will split the message into multiple SMS’s and spaces count as characters).
Editing content
If you need to edit existing content, edit the Automation rule by clicking on the pencil icon Edit to the right of the rule, scroll down to Notification Content and press the edit button as highlighted below.