Know why open rates fell
Instead of a silent, unexplained drop in engagement, the spa chain gets a clear flag that authentication is missing, pointing at the actual cause rather than leaving the owner guessing what changed.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business's emails actually land in the inbox instead of silently disappearing into spam, protecting the value of every other feature in the product.
Works with
What it does
Patri checks that the sending domain has proper authentication set up, tracks bounce and complaint rates over time, and warns the owner when a metric crosses a level that puts future sends at risk. It surfaces plain-language guidance rather than raw technical logs.
A spa chain switches from personal Gmail accounts to a dedicated sending domain for its newsletter, sends the first campaign, and watches open numbers come back far lower than the list size suggests — because nobody set up the domain's SPF, DKIM or DMARC records first, and mailbox providers quietly routed the mail to spam or rejected it before a single client saw it land in their inbox.
Deliverability monitoring exists because this happens constantly and almost never gets explained to the business it happens to. Patri checks whether the sending domain's authentication is actually set up correctly, tracks bounce and complaint rates over time, and warns the owner in plain language — not a wall of DNS jargon — the moment a metric crosses a level that puts future sends at risk. It cannot fix a domain's authentication for the owner; it can only tell them clearly when something needs fixing.
Patri runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
The system periodically re-verifies that the sending domain's SPF, DKIM and DMARC records actually resolve correctly at the DNS level, catching a record that was set up wrong or has since broken, rather than checking once and assuming it stays correct forever unmonitored.
Every bounce and spam complaint reported back from the sending provider is aggregated into a daily metric, building a clear trend over time, instead of a scattering of individual events nobody is tracking together at all.
When complaint rate or bounce rate crosses a conservative safe threshold, the owner is notified with a plain-language explanation of what happened and why it matters, well before the metric reaches a level that seriously damages sending ability.
Every warning explains the actual problem — an unauthenticated domain, a rising complaint rate — in terms an owner without a technical background can act on, rather than a raw DNS error code with no context attached to it.
Why it matters
Instead of a silent, unexplained drop in engagement, the spa chain gets a clear flag that authentication is missing, pointing at the actual cause rather than leaving the owner guessing what changed.
A rising complaint or bounce rate is flagged while it is still a fixable problem, rather than discovered only after it has already affected the domain's ability to reach anyone's inbox at all.
An owner with no DNS background gets an explanation they can actually act on or hand to whoever manages their domain, instead of a raw authentication error with no plain-English translation.
The detail
Authentication is the single highest-leverage factor in whether email arrives anywhere at all, and it is also the one part of this product Patri genuinely cannot do for the sender. SPF, DKIM and DMARC records must be added to the DNS settings of the sending domain itself, wherever the business manages that domain, entirely outside this product. Patri checks whether those records exist and resolve correctly, treating an unauthenticated domain as a real gate — but adding the records is work only the domain's owner, or whoever manages their DNS, can do.
This is where the 2024 bulk-sender rules Gmail and Yahoo now enforce become unavoidable. Both expect proper SPF and DKIM authentication, a DMARC record, a working one-click unsubscribe, and a spam-complaint rate low enough not to trigger filtering — providers treat a rate above roughly 0.1% as a reputation event serious enough to affect delivery for every future send, not just the one that triggered it. None of this is optional at real volume, nor can it be quietly handled without the domain set up correctly.
Reputation itself is earned, not granted. It belongs to the sending domain and builds up, or erodes, through how mailbox providers observe that domain behaving over time: engagement, complaint rate, bounce rate, consistency. No tool can hand a damaged domain a good reputation; it can only report accurately on where reputation stands and warn early enough for the business to protect it, before a threshold is crossed and sends start failing quietly, the way that spa chain's campaign did.
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
The most common cause is missing or incorrectly configured SPF, DKIM or DMARC authentication on the sending domain, which causes major mailbox providers to route mail to spam or reject it outright before a recipient ever has the chance to open it. Deliverability monitoring checks authentication status specifically so this gets flagged as the likely cause rather than left as an unexplained drop in numbers.
Patri checks whether those records exist and resolve correctly, and explains in plain language what is missing, but it cannot add DNS records to a domain it does not own or control — that step happens in whatever platform the business manages its domain's DNS settings through, done by the business or whoever manages their domain on their behalf. This is genuinely the one part of the whole product that depends entirely on the sender's own action.
The owner gets notified with a plain-language explanation of what happened and why it puts future sends at risk, since major mailbox providers treat a complaint rate above roughly 0.1% as a reputation event that can affect delivery for every subsequent send, not only the campaign that triggered the alert. Acting quickly on that warning — reviewing list quality and recent sending practices — matters more than waiting to see if the number settles on its own.
No — authentication is a necessary foundation, not a guarantee. Inbox placement is ultimately decided by each mailbox provider based on the sending domain's ongoing reputation, recipient engagement and a wide range of other signals no sender or platform fully controls. Proper authentication removes one major, common cause of failed delivery; it does not override every other factor a mailbox provider weighs.
The rest of your stack
No rip-and-replace — keep emails out of the spam folder works alongside the systems already running your business.
Coming soon