STEP 01
Something happens on her record
A consultant books the appointment, takes the order, or receives the gown. That action, not a marketing calendar, is what puts a message in the queue.
Client communications
Email to brides, and a written reason for every message the store did not send
RingUps runs a live email pipeline for the whole bridal journey. Twelve customer templates cover everything from the booking confirmation to the review ask, already delivering in production: 100 messages sent, the most recent on 2026-08-04, each carrying a real Resend message id. And every message that was held back is stored in full, with a plain-English reason, so nothing about a bride's communication history is ever a mystery.
- 100
- emails delivered in production, latest 2026-08-04
- 12
- customer templates, wording already written
What does RingUps actually send to a bride?
Email. Twelve customer templates ship with the wording written, rendered in the store's own logo and colour. Two of them are transactional and can never be switched off. The other ten are commercial messages, and every one of those carries a working opt-out.
Three more templates sit behind those twelve: two staff training emails that go to your own people, and one bulk campaign template for a selected list. Fifteen template files in total.
A consultant can also send one by hand, now, about one order. Pick the bride, pick which of her appointments or orders it concerns, and the message goes out from the store rather than from somebody's personal inbox where no colleague can see the thread.
| Template type | How many | Opt-out link | Examples |
|---|---|---|---|
| Transactional | 2 | None, by design | Booking confirmation, order confirmation |
| Commercial | 10 | Yes, a working opt-out | Appointment reminder, gown arrival, review ask |
The problem
The bride who was never called, and nobody can say why
A gown lands in receiving on a Thursday. The consultant who sold it is off that week. Six days later the bride phones to ask whether her dress has arrived, and the store finds out it has been hanging in the back since Thursday. Nobody sent the note. Nobody knows whether anybody meant to.
The same gap shows up at the other end of the journey. A bride collects her gown, is delighted, and is never asked for a review, because the person who would have asked was on the floor with someone else. In a system with no message record, the absence of an email leaves no trace at all. There is nothing to open, nothing to read, and no way to tell a missed message from a deliberate one.
A message that was never sent should still leave a record. That is the whole idea behind how RingUps handles communication.
How does a RingUps email get from a template to a bride?
Four steps. The order of them is the point: the message is written and stored before anything decides whether it may go.
STEP 02
RingUps writes the email in full
Subject and body are rendered with her details merged in, and the finished message is written to the outbox with the date it is due. It exists as a record from this moment on.
STEP 03
The send decision is made separately
Is the template enabled. Is she marked do-not-contact. Has she already had this one. If any answer says no, the row is suppressed and the reason is written onto it in plain English.
STEP 04
A drainer claims the row and posts it
Messages queue rather than fire inline, so an interruption mid-send loses nothing and duplicates nothing. Delivered messages come back with a Resend message id attached to the row.
One journey, not a settings screen
Her record shows the messages in the order they belong to her wedding, with what was sent, what is queued, and what was held. The follow-up below was held because she ordered the same day, so the order confirmation had already told her what the follow-up would have said.
Any of the ten commercial templates can be turned off, restricted to one appointment type, or held back from brides who have already bought, so the come-back-and-see-us message never lands on the woman who signed a contract last week.
The suppression log
Why did she never get the review ask?
Every owner eventually asks that question, and no other bridal system is documented as being able to answer it. RingUps writes the message before the send decision is made, so a message that never went out is still on file, in full, with a reason in plain English rather than an error code.
A worked example
T. Nguyen collected her gown on 1 October. On the 14th she mentions to the owner that she never received the note asking her to leave a review, and she would have been happy to write one.
- Open her record and open the message log.
- Filter to Not sent. The row is there, dated 4 October.
- The reason reads: customer is marked do-not-contact.
- Open the row and read the exact email that was withheld, word for word.
The answer took about fifteen seconds and nobody had to guess. Somebody ticked do-not-contact on her record months ago, probably while she was still shopping. That is a staff conversation, not a mystery. The tabs split the log into sent, queued, failed and not sent, so a bounced address surfaces as failed instead of quietly vanishing.
One record per bride →Anti-spam compliance
Does a bridal appointment reminder need an unsubscribe link?
This is the question most store owners have never been asked and cannot answer, so it is worth setting out plainly. Under the Canadian Anti-Spam Legislation, a commercial electronic message needs consent, identification of the sender, and a working unsubscribe mechanism. A transactional message that simply completes something the customer asked for is treated differently.
RingUps splits its twelve customer templates along that line. The ten commercial templates carry a working opt-out. The booking confirmation and the order confirmation do not, and that is deliberate: a bride who books an appointment and then hears nothing back phones the store, and a confirmation she cannot switch off is the point of a confirmation.
Putting an unsubscribe link on a confirmation is not the safe choice. It is the choice that lets a bride silently turn off the one email she genuinely needs. The distinction is built in rather than left to whoever writes the template.
- Commercial electronic message
- Encourages participation in a commercial activity. The appointment reminder, the come-back follow-up, the gown arrival note, the review ask. Ten templates. Each one carries an opt-out the bride can use herself.
- Transactional message
- Confirms or completes a transaction the customer has already entered into. The booking confirmation and the order confirmation. Two templates. No opt-out link, and they cannot be switched off by the store either.
- Do-not-contact
- Set on the bride's record by staff or by her own opt-out. Once it is set, every commercial message for her is suppressed with that reason written onto the row, which is how the log can prove it later.
What this replaces in a bridal store today
The consultant's personal inbox
Messages sent from a private account are invisible to everyone else and leave with the employee. A message sent through RingUps lands in the same log as everything else, so the next person to open her record can read what she was told and when.
The list of who to call back
A notebook, a whiteboard or a shared spreadsheet of brides somebody meant to contact. The queue is built from what actually happened on her record, so it does not depend on anyone remembering to write the name down.
The separate mail tool
A general-purpose newsletter product knows an email address. It does not know her wedding date, her appointment type, or that she signed a contract last week, so it cannot hold a message back for any of those reasons.
Appointments →
Where the reminder comes from. Appointment types, the booking flow, and which booking policy fields are still inert.
One record per bride →
The record the message log lives on, and what a consultant sees when a bride phones and asks a question about last month.
Security and trust →
How records are kept, what RingUps holds, and what has not been certified. Read this before you ask about the message log as evidence.
Questions people ask about RingUps client communications
Has the RingUps email pipeline actually sent anything in production?
Yes. 100 messages have been delivered from the live system, the most recent on 2026-08-04, and each one carries a real Resend message id. That is production traffic from Cande Bridal Boutique in Kelowna, British Columbia, not a staging test.
Can I find out why a bride never received an email?
Yes. RingUps writes the message before it decides whether to send it, so a held message is still on file with its full body and a plain-English reason. Filter the message log to Not sent and the row says, for example, that the customer is marked do-not-contact. No other bridal system is documented as answering that question.
Do RingUps emails include an unsubscribe link?
Ten of the twelve customer templates are commercial messages and carry a working opt-out. The two transactional templates, the booking confirmation and the order confirmation, deliberately do not, because a bride who books an appointment and hears nothing will phone the store. Under the Canadian Anti-Spam Legislation a transactional message is treated differently from a promotional one.
Does RingUps send a fitting reminder automatically?
Not by default. The fitting reminder template ships switched off, so it is not a live automation until a store turns it on. Treat it as a template that is ready rather than a message that is already going out.
Does RingUps chase an outstanding balance automatically?
No. There is no automated balance-due email. The dashboard send request button writes a suppressed row while the interface still reports it as sent, so a store should treat chasing a balance as a manual job until that is fixed.
Bring the email you send most often
Book a fifteen-minute demo on your own data. We put your wording into the template on the call, preview it in your colours, and send it to your own inbox while you watch.