jataíRotas. The third email goes out. On the right day.
Rotas (sequences) are Jataí's contact sequences. Each Rota is a versioned recipe: touches, waits, and stop conditions. It cancels itself when the person replies, when a human takes over the conversation, or when the person asks to opt out — and the text of each touch is written for them, not copied from a template.
Multi-touch sequences that follow up on the agreed schedule and cancel themselves when the person replies, a human takes over, or they ask to opt out.
42% of replies arrive after the first email.
In Instantly’s Cold Email Benchmark Report 2026, 42% of all replies came from the touches after the first, and the best-performing sequences had between 4 and 7 touches. Most teams stop at the second — not by decision, but because the second depends on someone remembering.
A Rota doesn’t remember. It executes. And, unlike a blast, it knows how to stop.
Touches, waits, stops.
Touches.
Each touch is written by Enxame (agents) for that person, starting from the organization’s angle — it isn’t a template with {{nome}}. Each mold has a word limit and a list of prohibitions: no "hope you’re doing well", no manufactured urgency, no number that isn’t in the context. The default cold sequence has three touches: opening, proof, and close.
Waits.
Waits are brand parameters, counted in hours and calendar days. By default: one hour before the opening, four days until the proof, seven until the close. If a wait lands outside the brand’s sending window (business days, business hours, in the brand’s time zone), the touch is pushed to the next opening. Each brand adjusts its own; the recipe is versioned data, and the one already running doesn’t change midway.
Stops (the ones that matter).
- Replied → cancels before the next send; the reply goes to Enxame.
- A human took over the conversation (your salesperson replied, or the CRM reported human activity) → cancels.
- Asked to opt out → cancels, and the contact goes into suppression for that brand.
- Bounce or complaint → the contact goes into suppression.
- Fit below the minimum → the Rota doesn’t even start: it’s a comparison, made before any model cost.
- No reply by the end → it closes. Recycling can come back later (default: 180 days, a brand parameter).
"Not now" isn’t "no".
When Enxame classifies the reply as "not now", the Rota stops. Recycling — a clock-driven recipe that runs on business days at 9 a.m. — schedules the return (default: 90 days, a brand parameter) with a touch that builds on what happened before: without pretending it’s the first contact and without chasing the old reply. That touch starts with a zero approval limit — it goes to the manager’s queue before it goes out.
If the person gave a date, the date rules. "Reach out in March" and "on the 22nd" become a date at triage, and recycling comes back on it — before or after the brand’s default. A vague marker ("after Carnival", "when the budget closes") doesn’t become a date: then the brand’s default applies.
A three-touch Rota, as it goes out.
| Touch | When | Goal | Length |
|---|---|---|---|
| 1 · opening | 1 hour after entry | Context and a question, anchored in the organization’s angle | up to 90 words |
| 2 · proof | +4 days | A concrete proof point and a request for a short conversation | up to 80 |
| 3 · close | +7 days | Close while leaving the door open, with no pressure | up to 45 |
The molds forbid repeating the opening, promising results, offering unauthorized discounts, "last chance", and asking why the person didn’t reply.
Each brand, its own Rota, its own domain.
Each brand sends from its own domain, with isolated reputation and its own daily quota. A Rota never crosses brands, and suppression is per brand. Before each send, Jataí checks whether another of your brands talked to the same organization within the spacing window you set — if it did, the touch waits, it doesn’t disappear. See Multi-brand and Deliverability.
Three things Rotas don’t do.
They don’t send the same text to everyone.
Each touch is written for the person; what repeats is the structure, not the sentence.
They don’t keep going after a reply.
Not even "just one more". Replied, stopped.
They don’t send outside the brand’s window.
With the sending window on — business days and business hours, in the brand’s time zone —, a touch that would land on a Saturday night waits for Monday morning. And no touch goes out without passing suppression, consent, frequency, quota, and approval limit.
Frequently asked questions
How many touches should a Rota have?
The default cold sequence has three (opening, proof, and close; the close can be turned off). The 2026 benchmarks point to 4 to 7 touches as the best-response range; a longer recipe is versioned data the platform publishes, with no code change.
Does the Rota stop if the person replies "no"?
It stops. Enxame classifies the reply (not now, not interested, unsubscribe…), and an unsubscribe suppresses the contact immediately, without going through a human. Recycling only comes back for those who said "not now" or never replied.
What happens if my salesperson replies directly to the lead, outside Jataí?
The Rota cancels: when a human takes over the conversation, Jataí steps aside. And when your CRM reports that the lead became a customer, was lost, or was a duplicate, it stops too.
Can I use my own sequences?
The recipe parameters belong to the brand: waits, minimum fit, close on or off. Enxame writes the text of each touch for the person, and the operator approves it according to their approval limit.
Do Rotas work over WhatsApp or LinkedIn?
Today, email. WhatsApp exists as a channel, but there’s no Rota for it yet. LinkedIn isn’t on the plan.
How do Rotas handle deliverability?
A sending domain of its own per brand, a daily quota, an unsubscribe link on every touch, and suppression checked before each send. Details in Deliverability.