One clean list, not five
The agency finally works from a single, de-duplicated view of each client's contacts, rather than reconciling spreadsheets, old exports and manual entries every time a campaign needs building.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business has one clean, de-duplicated list of contacts with accurate status (subscribed, unsubscribed, bounced) instead of scattered spreadsheets or stale exports.
Works with
What it does
Patri lets the owner import contacts from a CSV or connected tool, merges duplicate entries by email address, and tags or groups contacts for easier targeting later. Every contact record shows its current subscription status and consent history at a glance.
A marketing agency managing five retail clients has each client's contact history scattered across old spreadsheets, a few CSV exports from a previous tool, and whatever got manually typed in over the years — with the same customer showing up three times under slightly different spellings of their email address, and no reliable way to tell which version is actually current.
Contact and list management brings that into one place. Contacts get imported from a CSV or a connected tool, duplicate entries are merged by matching email address, and every contact can be tagged or grouped for easier targeting later. Each contact record shows its current subscription status and full consent history at a glance, so the agency, or any business, is finally working from one clean picture instead of five scattered ones.
Patri runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Upload a CSV or pull contacts from a connected CRM or e-commerce platform, with each import tracked as its own job showing exactly how many rows were processed and what happened to each one in turn.
Records matching by email address are identified and merged into a single contact, with a periodic scan also catching near-duplicate entries that slipped in through slightly different spellings or formatting choices made much earlier on.
Apply tags or group contacts into lists based on whatever distinction actually matters to the business — client, product interest, region — making later segmentation faster to build against as the list grows larger over time still.
Open any single contact's record and see their current subscription status and full consent history at a glance, rather than having to cross-reference several separate systems just to answer that one simple question correctly each time.
Why it matters
The agency finally works from a single, de-duplicated view of each client's contacts, rather than reconciling spreadsheets, old exports and manual entries every time a campaign needs building.
Merging by email address collapses three slightly different versions of the same person into one accurate record, instead of counting and possibly emailing the same customer three separate times.
Subscription status and consent history sit on the contact record itself, so answering a question about any one person takes a glance, not a cross-check across several old files.
The detail
Every import is the single most common way a previously unsubscribed or bounced address gets accidentally re-added to a mailable list, which is why an import does not become a shortcut around suppression — each row passes through the same suppression preflight check as any send path before insertion, and the uploader confirms the consent basis for that batch first. An old spreadsheet with no clear consent basis is not safe to import for marketing purposes just because it is already sitting on someone's laptop.
Storing names, emails, phone numbers and purchase history makes this a data store genuinely covered by India's DPDP Act 2023, not merely a convenient database — contacts have to be erasable on request, and the business needs a documented reason for how long it keeps contact data, rather than storing everything indefinitely by default. An agency holding five clients' contact histories in one workspace carries this obligation five times over, once per client, not once for the workspace overall.
Merging duplicates by email address is reliable for the exact-match case, but will not catch every real duplicate — a customer who signed up once with a work email and once with a personal one looks like two different people to an email-based match, and no automated merge can safely guess they are the same person without a stronger signal than a similar name. Periodic near-duplicate scans catch formatting variations, but a genuinely separate address for the same real person is, correctly, left as two distinct records unless the business has independent reason to merge them by hand.
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
No — every row in an import runs through the same suppression preflight check as any other send path, so a previously unsubscribed or bounced address is excluded from becoming mailable again even if it appears in the uploaded file. The import itself still requires attesting to the consent basis for that batch, since suppression checking and consent validity are two separate, both-necessary safeguards to satisfy.
Exact email-address matches merge automatically, and a periodic scan also catches near-duplicates from formatting or spelling variation, but two genuinely different email addresses belonging to the same real person — a work address and a personal one, say — will not be merged automatically. There is not enough reliable signal to safely guess that two different addresses are the same person without risking a wrongful merge, so that specific case needs a deliberate manual decision instead.
Yes — storing personal data like names, emails and purchase history makes this a data store covered by the DPDP Act 2023, which means a genuine deletion request has to be honoured properly and promptly, and the business needs a documented reason for its retention practices generally, rather than indefinite storage by default with no rationale behind it whatsoever, ever, at all.
Yes — contacts, tags and lists can be organised per client within a shared workspace, keeping each client's data and consent history distinct rather than pooled into one undifferentiated mass. This matters for more than convenience, since each client's contact data carries its own separate DPDP obligations that an agency has to honour individually, not collectively as if it were all one dataset.
The rest of your stack
No rip-and-replace — keep subscriber data organized works alongside the systems already running your business.
Coming soon