Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenCustomers get instant, reliable order confirmations, booking receipts, password resets and similar one-to-one messages that are separate from marketing blasts.
Works with
What it does
Patri exposes a simple way to trigger a single, personalized email in response to a specific customer action, using its own sending identity distinct from marketing campaigns. These messages go out even to contacts who have unsubscribed from marketing, since they are service communications, not promotions.
A booking platform for weekend getaways sends its promotional newsletter and its actual booking confirmations from the exact same sending setup, and when a festive-sale broadcast draws an unusually high complaint rate one month, booking confirmations for that same period start arriving late or bouncing too — a customer who just paid for a trip is left wondering, reasonably, whether their booking actually went through, entirely because of a promotional email they were not even part of.
Transactional email delivery exists specifically to prevent that. It exposes a simple way to trigger a single, personalised email in response to a specific action — a booking, an order, a password reset — using its own sending identity kept separate from marketing campaigns. These messages reach the customer even if they have unsubscribed from marketing altogether, because a booking confirmation is a service communication the customer is owed, not a promotion they can decline.
Patri runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
A specific action — a completed booking, a placed order, a requested password reset — fires a near-real-time send built from a transactional template matched to that event type, bypassing campaign batching entirely and immediately every time.
Transactional mail goes out through its own subdomain or dedicated stream, kept distinct from the identity marketing campaigns use, so the two never share the same reputation pool with one another at all, ever, under any circumstance.
A customer who opted out of the newsletter still receives their booking confirmation or receipt, because transactional sends check only the narrower, service-specific suppression scope, not the broader marketing opt-out at all, ever, under any condition.
Every transactional send is recorded with its event type, recipient and delivery status, giving a clear, searchable log for confirming whether a specific confirmation actually reached a specific customer, checked on request at any time.
Why it matters
If a marketing broadcast draws complaints or bounces heavily one month, booking confirmations and password resets keep flowing normally on their own separate sending identity, unaffected by the marketing side's trouble.
Someone who unsubscribed from the newsletter still gets their order confirmation, because that is a service message they are owed, checked against a narrower suppression scope than marketing mail.
A searchable delivery log per transactional message means a support query about a missing booking confirmation can be answered by checking the actual record, not by guessing.
The detail
Separating sending identities is not a cosmetic choice — it is the entire point of this capability, and skipping it undoes the protection almost completely. If marketing and transactional mail share the same domain or IP reputation, a complaint spike from one bad promotional send degrades deliverability for both at once, meaning the scenario this feature exists to prevent — a confirmation delayed by an unrelated newsletter's problems — happens anyway despite the feature being present. A dedicated subdomain, kept genuinely separate in how mailbox providers see it, actually delivers isolation, not merely labelling a message 'transactional' internally while it shares infrastructure with campaigns.
Suppression scope here is deliberately narrower than marketing suppression, and getting the distinction right matters in both directions. A customer who unsubscribed from promotional mail specifically has not withdrawn consent to receive a receipt for a booking they just made — that receipt is a service communication tied to a transaction they initiated, not a promotion they can decline like the newsletter. But a hard bounce or full account-closure request still has to suppress transactional sends too, since an invalid address or closed account should not keep receiving any mail, transactional or otherwise.
Because these sends are triggered by a specific action and bypass the batching pipeline entirely, they need to be near-instant and reliable in a way a scheduled broadcast does not — a confirmation arriving late reads as a system that might have failed, even once it arrives. This makes transactional delivery a different job, prioritising speed and per-message reliability over the batching a large broadcast depends on.
Industry use cases
13 industries where Patri applies this directly.
A dealership's website inquiry form feeds new leads into a segmented list; Patri sends a short nurture sequence over the following two weeks and a service-due reminder automation runs quietly in the background for existing customers.
See the automotive playbookA software reseller captures demo requests through a signup form; Patri enrolls each lead in a welcome-and-nurture automation while the sales manager reviews and approves the first broadcast to a larger prospect list before it sends.
See the b2b sales playbookA regional NBFC branch collects customer email consent at account opening; Patri stores that consent record and later sends a fixed-deposit rate update only to customers whose consent record is on file, routed through a manager approval step first.
See the banking and finance playbookA D2C skincare brand connects its online store; when a shopper adds a serum to cart but leaves, Patri's recovery automation sends a reminder a few hours later without any manual action from the brand's small team.
See the beauty and cosmetics playbookAn online exam-prep platform enrolls every new trial signup into a welcome series that introduces study resources over the first week, while a separate automation checks in on students who have not logged in for two weeks.
See the education playbookAn independent designer adds a signup form to their portfolio page; Patri captures each new subscriber's consent and sends a two-email welcome sequence introducing recent work.
See the freelancers and consultants playbookA physiotherapy clinic uses a welcome sequence for new patient inquiries and a quarterly newsletter reviewed by the clinic owner before sending, since Patri flags AI-drafted health claims for manual approval.
See the health and wellness playbookA modular-furniture retailer connects its catalogue site; a visitor who views a wardrobe configuration but does not request a quote receives a follow-up email a day later through Patri's recovery automation.
See the home decor and furnishing playbookAn agency managing five retail clients keeps each client's contact list and consent records separate in Patri, with every draft campaign routed through the account manager's approval before it reaches that client's subscribers.
See the marketing agencies playbookA brokerage captures site-visit inquiries through a signup form; Patri enrolls each inquiry in a nurture sequence that shares similar listings over the following weeks, while a broadcast to the full buyer list still needs the principal broker's sign-off.
See the real estate playbookA restaurant collects email addresses through a QR-code signup form at checkout; Patri sends a monthly offer email to that list and automatically suppresses anyone who unsubscribes from future sends.
See the restaurants and food playbookA salon connects its booking system; clients with no visit in the last two months are automatically enrolled in Patri's re-engagement sequence, which pauses immediately if the client books a new appointment.
See the spas and salons playbookA travel agency's package-inquiry form feeds into Patri, which sends a short sequence of destination highlights over the following days and a follow-up if the traveler started but did not finish a booking request.
See the travel and tourism playbookMore from Patri
The business gets a professional-looking email out to its list without hiring a designer or writing code.
Learn moreThe business sends fewer, more relevant emails and avoids annoying subscribers who do not care about a given message.
Learn moreThe business nurtures leads and customers on autopilot — a welcome series, a re-engagement sequence — without anyone remembering to hit send each day.
Learn moreNew subscribers and customers get an immediate, on-brand introduction instead of silence after they sign up.
Learn moreThe business wins back revenue and engagement from people who started something (a cart, a booking, an inquiry) and did not finish.
Learn moreThe business finds out which subject line or message performs better before committing the whole list to one version.
Learn moreQuestions
It should not, provided transactional mail is genuinely sent through a separate sending identity — a distinct subdomain or dedicated stream — from marketing campaigns. This separation is the entire point of the capability; sharing the same sending domain or IP reputation between the two would let a marketing problem degrade transactional delivery anyway, which defeats the purpose of having the distinction at all in the first place.
Yes — a marketing unsubscribe is scoped to promotional mail specifically, and it does not suppress transactional sends like receipts or booking confirmations, since those are service communications tied to a transaction the customer actually initiated, not a promotion they chose to decline. They would only stop receiving transactional mail too if their address hard-bounced or their account was closed entirely afterward.
Near-instantly — transactional sends bypass the campaign batching and pacing pipeline entirely, since a booking confirmation or password reset needs to feel immediate to be trustworthy, unlike a scheduled broadcast where a delay of minutes or hours is normal and expected. A noticeable delay on a transactional message tends to read as something having gone wrong, even when it eventually arrives correctly.
Yes — every transactional send is logged individually with its event type, recipient and delivery status, so a support query about a missing confirmation can be answered by checking that specific message's actual record rather than guessing, or asking the customer to check their spam folder blindly first without knowing whether it was even sent to begin with in the first place.
The rest of your stack
No rip-and-replace — send order confirmations and account notices works alongside the systems already running your business.
Coming soon
