Support email is not transactional

Solo US lash, brow, and wax artists already live in email. The consent chase does too.

The mistake is treating every message as the same kind of mail. A question from a client is not the invite. A human reply is not the reminder. The signed copy is not a support thread.

Two jobs

Support email is where a person answers. What does this line on the form mean? I am running late — does that change anything? The artist writes back in ordinary language. So do I, when the question is about ConsentBloom itself.

Transactional consent email is the chase. The invite carries the signing link. The reminder knocks again when the signature is still missing. The signed copy goes out when the record is done. That mail carries status. It is not a conversation.

Those are different jobs. They need different mail.

What mixing does

Put both jobs in one mailbox and three things go wrong.

The signature gets buried. The signed copy lands between a question about parking and a reply about a late arrival. Months later the artist hunts a record that was never missing. It was sitting in inbox noise.

Clients learn the wrong habit. They reply to the invite. They reply to the reminder. The question lands where the product was trying to send a link and a status, not host a conversation. The chase thread becomes a help desk by accident.

Reputation gets muddy. Inbox providers watch what a sending address does. A stream of signing links and reminders is one kind of mail. A back-and-forth with clients is another. Mix them and you train both the client and the inbox on the wrong job.

Same product, named at the mailbox

This is the same shape I have been writing down, just at the mail boundary.

• Email-first. The chase rides email. SMS is a different product, and it waits.
• Chasing is the product. A reminder is another knock on the same signing link, not a new conversation.
• The signing link is the surface. Transactional mail carries that link and the status of the chase.
• ConsentBloom is the notary of the consent record. Metaphor, not a license. The signed copy belongs with the record, not lost in a support thread.

Support mail does not replace any of that. Humans answer questions. Transactional mail moves the signature.

What this decision is not

I am not naming a help desk, a ticket queue, or a second product. I am not claiming a finished mail setup or a deliverability badge.

The artist can keep answering clients from the address she already uses for human help. The invite, the chase, and the signed-copy delivery do not share that support mailbox.

Appointments can stay manual. The calendar stays in Square or Booksy. ConsentBloom sits beside booking, not instead of it.

Honesty about the shape

This is a product-decision note, not a launch. I am not claiming the chase is finished, or that support and transactional mail are already two polished products.

I am naming the boundary. Support email is for humans. Transactional email carries the signing link and the status of the chase. They stay separate so the signature is not buried, the reply goes to a person, and the sending reputation stays about the job it was given.

The short answer

If someone asks why the help address and the consent mail are not the same inbox, the short answer is that support email is not transactional. Questions need a human. The invite, the reminder, and the signed copy need mail that only does the chase.

The blog will have more of this. There's RSS if you want it in a reader.