Quick answer
Use an email blast for a deliberate one-off message to a selected audience. Use an automation for a repeatable event or lifecycle moment, then check that another system is not already sending the same communication.
Before you begin
A defined message purpose, one intended audience and the consent basis appropriate to that message.
Accurate studio sender details, brand links and a test inbox on both desktop and mobile.
A list of messages already sent by Junocal and connected marketing tools so you can avoid duplicates.
You'll know it worked when
The final recipient count matches the audience you intended before any live send.
A test email renders correctly, uses working links and does not expose placeholder or incorrect client data.
An automation has one clear trigger, eligibility rule and enabled state.
The first real send appears once in history and reaches a client whose record genuinely met the trigger.
Follow along in Junocal
Open the exact product area, then keep this guide beside it.
Choose broadcast or automation
Use a broadcast for a timetable announcement, studio update or targeted one-off campaign.
Use an automation for repeatable moments such as welcome, reminder, failed-payment or win-back communication.
Use transactional booking messages for facts a client needs to complete or attend a purchase.
Avoid sending the same reminder from Junocal and another connected marketing tool.
Send a careful broadcast
- 1
Open Emails and choose a new message.
- 2
Select the intended segment and review the estimated recipient count.
- 3
Write a specific subject and a short message with one clear next action.
- 4
Send a test to yourself and check links, mobile layout, names and studio branding.
- 5
Review the audience again before sending the live message.
Configure an automation
Open Automations, choose the event or lifecycle moment and review the default message. Make the copy sound like the studio, confirm who is eligible and turn it on only after checking for overlap with existing tools.
Monitor the first real sends. If the message depends on a booking, membership or payment state, verify that the triggering record is the one you expect before changing the rule.
Troubleshooting
Start with the symptom that matches what you can see. Check the existing record before repeating a booking, payment or import.
The recipient count is zero or unexpectedly small
Check these first
Review every segment filter, consent requirement and whether the selected studio has matching clients.
Check for missing email addresses, opt-outs and date filters that exclude older records.
Next step: Correct the audience rule and preview the count again. Do not broaden consent or add unrelated clients merely to make the number larger.
An automation did not send
Check these first
Confirm it is enabled and the client record met the exact trigger and eligibility rule after activation.
Check send history, missing email, opt-out state and any waiting period before retriggering the event.
Next step: Fix the blocking configuration and test with a new eligible event. Avoid editing the client history to imitate a trigger.
A client received duplicate messages
Check these first
Compare Junocal broadcast, automation and transactional history for the same time.
Check connected email platforms for another flow triggered by the same booking or profile change.
Next step: Choose one system as owner of that message and disable the overlapping rule before the next eligible event.
Answers before you get stuck
What is the difference between an email blast and an automation?
A blast is a one-off message you deliberately send to a selected audience. An automation sends when a configured event or lifecycle condition occurs.
Why did a client receive two similar emails?
Check whether Junocal and a connected email platform both send for the same event. Keep one system responsible for each operational or marketing message.
Did this guide solve the problem?
Make the change, or ask with your account attached
Open the relevant Junocal screen now. If your question depends on a particular client, payment or class, Juno can send it to the support inbox with the page and studio context included.