How client communication works in Celebrant Central

This film follows one wedding, still eight months out, through every email and message already on its ceremony record in the real app. It shows which ones the celebrant sent herself and which ones the system sent automatically, then turns to the couple's own portal view of the same wedding, and shows one of their messages landing straight back on the ceremony instead of in an inbox.

Step by step

1. On Nina and Sam's ceremony hub, still 258 days from the wedding day, the Email panel already carries eight emails about it, before the couple and their celebrant, Sarah, have even met in person.

   

2. Sarah sent one of them herself: the quote. Everything else in the panel went out because something happened on the ceremony, not because she remembered to write it: the couple's acceptance, told both ways, the service agreement, and the booking confirmation.

3. This is what Sarah actually saw the morning Nina and Sam accepted the quote: a congratulations pop-up confirming the booking, with nothing left for her to chase.

   

4. Sarah gave each partner their own portal access, and the system sent the invitations that let them in.

5. This is Nina's view of the same wedding: the same date, the same venue, the same countdown, and the Notice of Intended Marriage paperwork she still has to lodge, waiting for her in her own portal.

   

6. When Nina has a question, she doesn't start an email. She writes it in her portal, and it lands straight on the ceremony record, in the Messages panel, next to everything else about the wedding.

   

7. Sarah answers once in the shared thread, and both partners get it. When something is meant for only one of them, a private thread keeps it that way, so a question about the vows, or a surprise for the other partner, never becomes a group email.

Chapters

• 0:00Eight emails
• 0:21What the system sent
• 0:32The booking she did not chase
• 0:44The couple's side
• 0:57A message that lands on the ceremony
• 1:26Sign-off

Full transcript

This is one wedding, still eight months out. Nobody has met yet. And there are already eight emails about it. Sarah sent one of them. The system sent the rest, and it sent them because something happened, not because she remembered. Nina accepted the quote. So it told Nina. It told Sarah. It raised the service agreement, and it confirmed the booking. And this is what Sarah actually saw that morning. A booking she did not have to chase. Sarah gave each of them their own portal access, and the system sent the invitations. This is Nina’s view of the same wedding. The same date, the same venue, the same countdown. And the paperwork she has to lodge, waiting for her. When Nina has a question, she does not start an email. She writes it here, and it lands on the ceremony, next to everything else. Sarah answers once. Both of them get it. And when it is intended for only one of them, only they get it. A question about the vows. A surprise the other one should not see yet. One wedding. One page. Every conversation on it, in both directions. Built for and by Australian marriage celebrants.