What counts as transactional
Charchy Send is for email a person's own action triggers. What that includes, what it doesn't, and how we check.
Transactional email is triggered by the recipient's own action or account — they signed up, asked for a code, bought or booked something, or something happened to their account. They expect it and would miss it.
Yes
- Sign-in, verification and one-time codes
- Password resets and security alerts
- Receipts, invoices and payment confirmations
- Order, shipping and delivery updates
- Booking confirmations and reminders
- Account notices: a plan renewing, a storage limit reached, a teammate's invite, a reply to their support ticket
No — use Charchy Campaigns
- Newsletters and product announcements
- Offers, discounts and sales
- "We miss you" and re-engagement emails
- Anything sent to a list rather than to one person about their own action
Mixing the two in one stream lets a promotion's spam complaints drag down your password resets. Sending emails has examples for the grey area.
Why we hold the line
Every sender on our delivery infrastructure shares its reputation with mail providers. Keeping the stream transactional keeps your password resets in the inbox, at this price. You agree to this rule in the Charchy Send terms before your first live key.
How we check
We watch for the shapes of marketing mail:
- The same email to many people. A receipt or a code always differs (an order number, a code, a name); a promotion is identical for everyone.
- Many emails with
List-Unsubscribe. The header is allowed — right for product notices people can switch off — but when most of a workspace's emails carry it, they're usually a mailing list. - Sudden blasts. Thousands of emails in a few minutes, far above your usual pattern.
- Many
bccrecipients on one email — a faked mailing list. - Spam complaints. People complain about mail they didn't expect.
What happens
- If your mail looks like marketing, a person at Charchy reviews it and emails you what we saw and how to move it to Campaigns.
- If it happens again within 30 days, or the review confirms it, API sending
is paused (
sending_paused) until we sort it out with you.
Not sure about an email? Ask support@charchy.krd before you send it.