Prerequisites
- Create a Booking Schedule — A bookable schedule to test with
Make Sure Invitations Actually Send
The setup the booker's invitation depends on, and how to prove it works before you need it to.
Before You Begin
- An understanding of which message goes out from where
- A bookable calendar to test with
- Access to your organisation's email sending settings, or someone who has it
Messages Zyntro sends on your behalf go out from your own domain, because an invitation that appears to come from a generic address is worth much less — it is likelier to be ignored and likelier to be filtered.
The cost of that is a dependency: your domain has to be verified for sending before Zyntro will send as you. Until it is, invitations to the people booking you are skipped.
Nothing in the booking screens warns you about this, and your own briefing keeps arriving, so the only reliable way to know is to test.
Steps
Check whether a sending domain is set up
Look at your organisation's email sending settings for a verified domain.
If one is there and verified, invitations will be sent as you and there is nothing more to do. If there is none, or it is unverified, then everything addressed to the person booking you is currently being skipped.
Set the domain up if it is missing
Verifying a sending domain means adding some records to your domain's DNS so that receiving mail systems can confirm Zyntro is allowed to send on your behalf.
It usually needs whoever manages your domain, and it is not instant — DNS changes take time to propagate. It is worth starting before you need it rather than on the morning you publish a booking link.
This is the same setup that email from Zyntro generally depends on, so if you are already sending email as your business, it is probably already done.
Test with a real booking
This is the only test that proves anything. Open your booking page in a private window and book a slot using an email address you can actually check — a personal address is ideal, because it also shows you how the message looks to someone outside your business.
Then check both mailboxes:
- Did you get the briefing? That one almost always arrives and tells you little.
- Did the booker's address get an invitation from your domain?
It is the second one that matters. If it is missing, the sending domain is the first thing to look at.
Check what the invitation looks like
While you have it in front of you, read it as a stranger would:
- Does the From name look like you or your business?
- Is the event title meaningful to someone who booked a week ago? It comes from the schedule's event title, not the customer-facing one.
- Does the calendar attachment add correctly to your calendar?
- Do the reschedule and cancel links work?
Those links are the booker's only self-service route, so they are worth clicking once.
Cancel your test and keep the habit
Cancel the test booking using the link in the invitation — which also tests the cancellation path and frees your slot.
Repeat this test whenever something changes around sending: a new domain, a change of email provider, or a new calendar going out to a different audience.
Result
You know, rather than assume, that the people booking you receive an invitation from your own domain with everything they need to attend or change the meeting.
And you have seen it as they see it, which is a different thing from seeing a copy of it yourself.
Before you publish a booking link to the public
- A verified sending domain exists for the organisation
- A real test booking was made with an outside email address
- The invitation arrived, and the From name reads as your business
- The calendar attachment added correctly to the test calendar
- The reschedule and cancel links in the invitation both work
- The test booking has been cancelled and the slot released
Important: Everything sent to the person who booked depends on a verified sending domain. The booker's invitation goes out from your own domain, using your own email sending setup — so until that is configured, those messages are skipped. The meeting is still created, and you are still emailed, which is exactly why this goes unnoticed. If you take bookings from the public, set your sending domain up before you share a booking link.
