Store each member's birthday and join date in date fields, then use the Custom Date Reminder trigger to send a birthday text and a membership anniversary note on the right day. GoHighLevel supports both a month and day birthday field and a full date field, and it can run the message before, on, or after the date. The bottom line: these messages work because they are personal and expected, so they should be short, honest, and sent only to members who agreed to receive marketing.
What the trigger supports
HighLevel's help article lists Birthday (MM/DD) and Birthday (MM/DD/YYYY) as example field types, and says the trigger starts before, on, or after a date field you select. You can set a number of days before or after, and filter by day, month, or tag. The page says contacts with an empty date field will not trigger the workflow, and that there is no dedicated anniversary field, so create your own date field called Join Date. It also describes a Match on Year option for yearly repeats, but the page gives conflicting descriptions of how it works, so test it on a sample contact before you rely on it.
Message ideas that fit a gym
| Date | Message | What it does |
|---|---|---|
| Birthday | Happy birthday from the club, with an invitation to a free class for the member or a guest | Brings the member in for a visit and may introduce a friend |
| One month after joining | A thank you and a link to book a progress check with a coach | Starts the habit of a regular review |
| One year after joining | A thank you with the number of visits if you track it, and an offer to book a goal session | Marks the year and checks goals for year two |
| 30 days before the contract renewal | Renewal terms in plain words, if the member has a term contract | Meets renewal notice rules where they apply and avoids surprise |
Rules to check before sending
- Marketing texts need prior consent, so only include members who agreed. A birthday offer is marketing if it promotes a purchase or visit.
- Do not give a prize in exchange for a review. The FTC reviews rule bars giving something of value in exchange for a review, so keep birthday offers separate from review requests.
- Collect the birthday with a reason, such as a birthday class, and store only month and day if you do not need the age.
- Send inside the allowed hours, 8 a.m. to 9 p.m. recipient local time as a baseline.
Build it in HighLevel
- Add two date fields to the contact form: Birthday (MM/DD) and Join Date. Make them optional, and explain why you ask.
- Create a workflow that starts with the Custom Date Reminder trigger on Birthday, set to run on the date, with a filter for members with the tag marketing consent.
- Send a short text with a link to book the free class, and add a task for staff to wave at the member on their next visit.
- Create a second workflow on Join Date that runs 30 days after for the progress check note, and another that runs on the one year mark.
- Remove members who cancel from both workflows by tag, so former members do not get birthday texts.
Sample messages
- Birthday: Happy birthday, {{contact.first_name}}. Bring a friend to any class this week, free. Book here: [link]. Reply STOP to opt out.
- One month: You joined us 1 month ago, {{contact.first_name}}. Want to book a 15 minute progress check with a coach? [link].
- One year: One year with {{location.name}}, {{contact.first_name}}. Thank you. Let us set goals for year two. Book a session here: [link].
Keep each message short, with one link. A birthday text should feel like a note from a person at the club, so sign it with a real name when you can.
Collecting the dates in the first place
- Ask for the birthday on the trial form, with a line that says what you use it for.
- Store the join date automatically when the membership starts, using a workflow action that updates the Join Date field.
- Do not collect the birth year unless you need it. Month and day are enough for a message.
- Offer a way to opt out of birthday messages, and honor it.
What to measure
| Measure | Why |
|---|---|
| Birthday text to booking rate | Shows whether the offer brings members in |
| Guests who visit and later join | Shows whether the friend offer produces members |
| Opt out rate on date messages | A high rate means the offer or timing is off |
| Progress check bookings at one month | Shows whether members want coaching contact |
Common mistakes
- Sending a birthday offer to a member who cancelled last month. Use the tag to exclude them.
- Forgetting that contacts with an empty date field do not trigger the workflow.
- Mixing a birthday offer with a review request. Keep them separate so the offer cannot look like payment for a review.
Questions people ask
Which HighLevel trigger sends a birthday message?
The Custom Date Reminder trigger, using a Birthday date field on the contact.
Does HighLevel have an anniversary field?
No dedicated one. Create your own date field, such as Join Date, and use it with the same trigger.
Do birthday texts need consent?
If the message promotes a visit or purchase, treat it as marketing and send only to members who agreed to receive it.
To build the birthday and anniversary messages, start a GoHighLevel account here. The workflows are shown in our capabilities demo.
