Your agents now classify each conversation as Sales, Service or Undefined when closed, and the funnel of stages is executed only on sales. Support inquiries, complaints and single questions stop adding to your funnel, so your conversion reports reflect the actual sale.

✍️ Two conditions in natural language: describe when a conversation is about sales and when it is about service. If it doesn't meet any, it's left as Undefined.

🏁 Closing evaluation: the type resolves on the entire conversation when it ends, either due to an end condition or due to inactivity. If it is a sales one, the appropriate stage is assigned.

💬 Data from each conversation: the type is saved in the conversation, not in the contact. The same customer can have a service conversation today and a sales conversation tomorrow.

🔍 Full traceability: see the type assigned in the conversation and, in the logs, the result of each condition, the closing mechanism and the assigned stage.

🧭

Go to Cortex → Global Configuration → Stages and complete the Conversation Type section with your sales and service conditions.

⚠️ if your flow already has stages, it will continue to work the same way until you republish it. As of that publication, both conditions are mandatory.

When a customer initiates a conversation on WhatsApp without a registered phone number, the agent can send a native card asking them to share their contact. This reduces writing friction and prevents errors in data capture.

Go to Cortex → Agents → Agent Configuration → Message Format → Activate the Contact Request option.

Your agents can now recover inactive conversations based on where each customer left off. You can create up to 5 recoveries with their own conditions, to insist on the one who was about to schedule and not to the one who just greeted. In addition, you can avoid messages after hours.

Conditions in natural language: define when each recovery applies, for example “only if the customer asked for prices”. The first one on the list to be fulfilled applies.

Own attempts and schedules: each recovery has up to 3 attempts with their times and their shipping days and slots. If an attempt falls after hours, it is postponed rather than lost.

Contact record: each recovery saves a value in a contact field, so you know which recovery was applied and you can segment.

Test in the simulator: force the next attempt and verify what recovery is applied, without waiting for real times.

Go to Cortex → Global Configuration Panel → Recovery → choose the Custom mode and create your recoveries.

Download the conversations from your Cortex evaluations

Now you can download all the conversations from a mass evaluation into a single file to analyze them together, cross-reference them with other data, or share them with your team.

Download during execution: download conversations that have already ended while the evaluation is still running. The file indicates what is partial and how many it includes.

All the details in a file: transcript, simulated fields, tools executed with their result, interactive messages and the result per criteria of each conversation.

Without losing the failures: Incomplete or failed conversations are also included, with the reason for the outage.

Without interruption: the file is generated in the background and the evaluation continues without pauses.

Open the results of a mass evaluation in Cortex and use the download action.

The Appointments component adds two new actions —reschedule and cancel—with automatic reflection in Google Calendar and Outlook. ✨

#

Now , without calling the front desk or writing to an advisor. We added two new actions to the Appointments component of the FlowBuilder — and — and, when you have Google Calendar or Outlook connected, those changes are reflected in your calendar on their own. Schedule, reschedule and cancel: the complete appointment cycle, automated on the same channel where you already talk to your customers. 🙌

#

You choose the action by placing the Quotes component in your flow, in the field. Each action behaves depending on how many future appointments the customer has (filtered by the and you configure):

If the client doesn't have any future appointments for that group and type of event, the flow continues down the branch without sending anything. And if the synchronization with the calendar fails, your appointment is rescheduled or canceled just like in Atom: nothing is blocked. 🛡️

#

You don't need to reconnect calendars or change anything you already have configured.

When you create their calendar, they receive an email to synchronize their Google or Outlook in one click - without you having to connect it for them. ✨

#

Now with the buttons to connect their own Google Calendar or Outlook. From then on, the appointments that are scheduled in Atom appear alone in the personal calendar that you already use on a daily basis. No more relying on an administrator to make the connection by hand: the external user synchronizes himself on his own from the email. 🙌

#

Everything starts when creating the external user's calendar and is resolved from their welcome email:

#

Creating the calendar and triggering the email takes less than a minute:

If your business operation doesn't always have a defined amount when you open a business—either because you define it later, because you work with quotation services, or because you're in the prospecting stage—there's nothing to stop you. You can create and edit Deals without filling out the Amount field, and as an administrator you can decide exactly how you want them to behave.

#

The behavior of the “Amount” field now depends on how you configure it from “Customize Forms”:

💡 Your Amount field will remain active and required so as not to interrupt your current operation. The difference is that you can now adjust it whenever you want from “Customize Forms”.

If you also use to automate the creation of Deals, your flows can now run the “Create Deal” node without an assigned amount, without errors and without interrupting the conversation.

#

Customizing how the Amount field behaves in your Deal forms takes less than a minute:

#

Does this improvement remove friction from your business operation? We would love to know. Escríbenos. Your feedback helps us to continue building Atom with you.

In the results of any evaluation you will see the ✨ Correct with AI button. When you click, the IA Wizard opens on the side of the builder with the results already loaded. There:

Analyze what failed and why. Review each conversation with some error criteria, the evaluator's reasoning and the configuration of your Cortex, and group the errors by cause.

It shows you what it is going to correct. You see the list of problems found and choose which ones to fix.

Apply the changes for you. You see them reflected in the canvas and you can test them in the simulator.

You monitor: nothing changes for your customers until you save and publish.

It's available for all accounts with Cortex, without having to activate it.

Create a campaign once and let it reach each customer that meets the conditions on your list on its own.

Previously, to automatically send to a dynamic list you had to assemble a flow with the “Dynamic List” trigger. Now you do it directly from Campaigns: when you create a or campaign, you can now choose a dynamic list. The campaign sends those who are already on the list and everyone who enters later, and stays Active until you stop it.

You choose when it is sent: as soon as the customer enters the list, or within a window of days and times. If you enter after hours, the shipment waits until the next window.

Go to , choose Template or Flow and select a list labeled . Each dynamic list can be in only one active campaign at a time; if you stop the campaign, the list is free to use in another one.

Learn more about dynamic lists aquí

Until now, information fields in Atom were filled in by typing. That works for some data, but for information that should always have a fixed value — the type of plan, the source of the lead, the customer segment — free text generates inconsistencies. Starting today, you can create fields with predefined options, using two new types: (choose one option) and (you can choose several).

When you create a selector field, you define a catalog of options. Each option has two parts:

Two important things before configuring:

Each field allows up to , with a maximum of per option.