jataíOne account. Thirty-five brands, if that is your case.
Jataí is multi-brand by design: each brand has its own sending domain, isolated reputation, and its own search profile, tone, knowledge base, approval limits, and destination CRM, and a spacing rule stops two brands with the same owner from writing to the same organization in the same window. Whoever runs the platform sees all of them; whoever runs a brand sees only theirs.
For groups, holdings, networks, and agencies: each brand sends as if it were the only one — and none of them runs over another.
Too many brands, too little tooling.
If you run five, twelve, thirty-five brands, you live in one of two scenarios. Either you keep one account per brand in tools built for a single company — and pay per seat thirty-five times, with no account knowing what the other did. Or you put everything in one account and it all blends together: one brand's domain burns the other's reputation, the school's tone shows up in the agency's email, and the same company gets two approaches from "different groups" that share the same CNPJ (Brazilian company ID). The person on the other side notices. And replies to neither.
What is separate per brand, and what is shared.
| What | Separate per brand | Shared |
|---|---|---|
| Sending domain and reputation | ✓ | |
| Pólen search profile | ✓ | |
| Tone of voice and knowledge base | ✓ | |
| Destination CRM | ✓ | |
| Operators and approval limits | ✓ | |
| Suppression and consent | ✓ | |
| AI cost, with a statement per brand | ✓ | |
| The question "did another brand talk to this organization?" | ✓ (yes or no only) | |
| The portfolio of whoever runs the platform | ✓ |
Each brand is an isolated space in the database: every table carries the brand identifier, and every query is filtered by it. One brand cannot see another brand's data, not even by mistake.
Two of your brands do not write to the same company in the same week.
Before every send, Jataí asks the database one question: "did another brand talk to this organization in the last N days?". N is set per brand, from 0 to 180 days. The answer is yes or no — it does not say which brand, nor when, nor what. The key is the organization's domain; never email, never a person's name.
If the answer is yes, the touch waits until the window opens. Nothing is discarded: the message is right, the week is not.
Rota "Schools — Feb/27 cohort" · touch 2 WAITING — another brand talked to exemplo.org.br in the last 90 days resumes when the window opens
Does not exist yet: priority between brands (deciding which one keeps the organization) and shared suppression. Today the window is the same for all of them, and whoever opts out of one brand leaves only that one.
You see the group. The operator sees their brand.
Whoever runs the platform sees the portfolio — every brand, side by side — and can enter a brand to operate it: the "support mode" banner stays visible the whole time, and every entry is recorded in that brand's audit log. A platform role does not grant automatic access to any brand: access is granted, never inherited. A brand's operator sees only their own.
What it looks like in practice.
A group with several brands (our own case).
We run Jataí on our own group's brands before opening the door. Brands from different fields on the same radar, each with its own domain, its own tone, and its own CRM; spacing stops two of them from writing to the same organization in the same window.
An agency with several clients.
Each client is a brand, with its own CRM, tone, search profile, and reputation. The agency runs all of them with the whole team, and no client sees another. Each brand's AI cost is tracked separately, with a statement and monthly close — so you can pass it on.
Three things we do not do with your group.
We do not share reputation.
One burned brand does not take the others down.
We do not mix tone or knowledge base.
One brand's Enxame (agents) does not read another brand's tone or knowledge base.
We do not "optimize" across brands without you.
Spacing is your rule, visible and configurable per brand.
Frequently asked questions
What counts as a brand?
An isolated space, with its own sending domain, search profile, tone, knowledge base, destination CRM, operators, and approval limits.
Can I have brands in different CRMs?
Yes. Each brand has its own CRM destination, and several can point to the same one.
How do I stop two brands from approaching the same company?
With spacing between brands: you set a window from 0 to 180 days per brand, and Jataí delays the send when another brand talked to the organization within it. Nothing is discarded.
Does a brand with a bad reputation affect the others?
No. Sending domain and reputation are per brand.
How many brands fit?
Jataí was designed for dozens of brands in the same account. Plugging in a new brand is configuration — profile, tone, CRM, domain — not a code change.
Does it work for an outbound agency?
Yes: each client is a brand, isolated from the others, with AI cost tracked separately.