jataíEntrega. Only once it is a conversation. With the history attached.
Entrega is Jataí's handoff to your CRM. The lead only goes in once it has become a conversation: first into a board of stages inside Jataí itself, the pre-CRM, and into your CRM when it reaches the last stage, with the full history, activity and temperature — never the pipeline stage. When the CRM reports the outcome, the lead's Rotas cancel themselves.
The lead lands in your CRM at the right moment, with everything that happened before — and your pipeline stays yours.
A pipeline with 4,000 leads and 40 conversations is not a pipeline.
Every prospecting tool "integrates with your CRM". What that usually means: it dumps the whole list in as leads, and the rep starts ignoring the column. Entrega (handoff) does the opposite. The lead is only born in the CRM when someone replied and Enxame (agents) classified it as a conversation. Whatever did not become a conversation stays in Jataí — visible, but out of the pipeline.
We write activity and temperature. Never the stage.
| CRM field | Does Entrega write it? | Why |
|---|---|---|
| Lead, contact, and company | Yes (creates it or links to the existing one) | that is the handoff |
| Activity (conversation history) | Yes — every touch, every reply | the rep reads the whole conversation |
Temperature (dedicated field jatai_temperatura) | Yes — a number from 0 to 100 | a signal, not a decision |
| Why it arrived and where it came from | Yes — the reason and the angle, with the contact source | LGPD and traceability |
| Pipeline stage | Never | two systems fighting over the same field destroy trust in the CRM |
| Lead owner | No — it follows your CRM rule | your process assigns the rep |
Before your CRM, a board inside Jataí itself.
Whoever replied goes first into the pre-CRM: a board of stages for the brand, inside Jataí. By default there are five — New, In conversation, Meeting scheduled, Proposal and Send to CRM —, and the brand changes the names and the number. Your team moves the card; reaching the last stage releases the handoff to the CRM, once, with the history attached.
The pre-CRM stages belong to Jataí, not to your CRM: there, it still does not write stages. The brand can turn the board off and hand off straight to the CRM.
Your CRM reports back. Rotas obey.
Jataí does not keep reading your CRM. Your CRM is the one that reports: a return webhook says the lead became a customer, was lost, was a duplicate, or received human activity — and each of these outcomes cancels or pauses that lead's Rotas (sequences). Human activity pauses every automated Rota for that lead: if your rep is already talking to the person, Jataí steps aside. There is also a reconciliation query, to check what the CRM knows.
That is why "replies or buys" on the home page is literal: the purchase happens in your CRM, and Jataí finds out.
Where we deliver.
The path is the handoff Contract: your CRM implements four HTTP routes, authenticated by token, and runs the conformance suite until it is green. That is how a new brand plugs in without becoming an integration project.
For a legacy system that will not implement any route, there is the generic adapter: it maps fields through configuration, with no new code (POST, PUT, or PATCH, with the token in the header, in the query string, or basic auth). HubSpot, Pipedrive, and RD Station CRM come in through one of these two paths — there is no native connector yet.
{
"versao": "v1",
"externalId": "lead-8f3a2c",
"gatilho": "resposta_positiva",
"organizacao": {
"nome": "Instituto Horizonte de Formação",
"cidade": "Goiânia", "pais": "BR",
"identificadores": { "cnpj": "••.•••.•••/••••-••" }
},
"pessoa": {
"nome": "Helena Prado", "cargo": "Academic coordination",
"contatos": [{ "tipo": "email", "confianca": 0.9 }]
},
"jataiTemperatura": 82,
"porQue": "Replied asking for pricing; the committee meets on the 22nd.",
"historico": [
{ "de": "nos", "canal": "email", "em": "2026-09-15T09:00:00-03:00" },
{ "de": "eles", "canal": "email", "em": "2026-09-18T09:12:00-03:00" }
]
}Each brand, its own CRM. Or the same CRM, without mixing.
One brand can deliver to one CRM, another to a different one, several to the same one. Each has its own connection and its own token. See Multi-brand.
Three things Entrega does not do.
It does not dump lists.
If they did not reply, they do not become a lead.
It does not touch the stage.
Not even with permission. The option does not exist.
It does not delete anything.
Entrega only adds; if you turn Jataí off, the history stays in your CRM.
Before Entrega.
Entrega is the end of the journey. It starts at Pólen (discovery).
Frequently asked questions
Is Jataí a CRM?
No, and it will not be. We deliver into yours.
Does Entrega create duplicates?
No. Each lead carries an idempotency key: the same key never creates two leads, and a redelivery is treated as a redelivery, not as an error. Your CRM can still answer that the lead already existed.
Can I allow Jataí to change the stage?
No. It is the only thing that is not configurable. We explained why above.
How does the integration work?
Through the handoff Contract: your CRM implements four HTTP routes, authenticated by token, and runs the public conformance suite. For a legacy system, the generic adapter maps fields through configuration. Details in handoff Contract.
What is "temperature"?
A signal from 0 to 100 written to a dedicated field (jatai_temperatura), so your rep can prioritize — it does not replace the stage or the rep's own qualification.