A new synchronization rule gives you the power to define when HubSpot contacts are created in Atom. ✨

#

Now . We added a new synchronization rule that gives you control over when a contact created in HubSpot is replicated in Atom: instantly, or only when the interaction actually begins. You define behavior based on your operation. 🙌

#

Everything is managed from a single option: . Depending on how you leave it, it completely changes the way Atom brings your contacts:

#

Activating or deactivating it takes seconds, directly from your platform:

At Atom, we anticipate and enable the possibility of generating a username for your channels within Atom.

With this update, administrators can claim and view the @username of each WhatsApp channel connected from Atom available in Settings → Channels.

The phone number will still be visible in the WhatsApp profile for your customers. @marca complements your identity; it doesn't replace it.

Additional resources:

#

Through stickers and voice notes, connect in a more authentic way, allowing you to transmit immediate trust through pre-recorded audios and create much more enjoyable and visual experiences at every stage of your customer's journey.

#

Implementing these new formats is super fast and intuitive directly from your platform.

The Smartons now supports all four of WhatsApp's interactive formats. This means that your bot can show your customer a product carousel, ask them to confirm data with yes/no buttons, present a menu of options as a list, or accompany an answer with an image.

The configuration lives in the Smarton inspector: you activate the types you want to use and you describe in natural language in which situations you should use them.

Flowbuilder → Smarton node → Inspector → “Interactive Messages” section.

Available for all types of smartphones

We launched the component, a new node that you drag to the FlowBuilder canvas to divide your contacts' traffic between different variants of your flow.

Do you want to know if “Schedule demo” works better than “Talk to an advisor”? Insert the component after your welcome message, define the traffic percentage for each variant and connect them. Done: your contacts are automatically distributed and you compare results by variant.

Until today, setting up an experiment required combining HTTP and conditional components with a random number API — something that only the Atom team could configure. Now you do it, in less than 2 minutes.

Open any flow in FlowBuilder, search for the “Experiment” component in the component palette and drag it onto the canvas. Start optimizing your conversations today!

If you have doubts see the entire detalle aquí 👈

Now you can duplicate a WhatsApp template to one or more channels from a single action, without having to manually recreate it for each number.

💬 Do you have feedback or questions? Leave us a comment in the feedback section.

Introducing Component Blocks: a way to save any sequence of FlowBuilder nodes as a reusable block and make it available for all your future flows, with one click.

From the same canvas where you build your flows, select the nodes you want to save, give them a name and a description, and voila — they appear in your Block Library to insert when you need them. The nodes are inserted already connected to each other, ready for you to only glue the ends to the rest of the flow.

In addition, Atom 🧡 includes a catalog of curated blocks available to you.

In the FlowBuilder canvas, select the nodes you want to save and click in the floating bar. To insert existing blocks, use the button in from the component side panel.

Until now, in outbound flows (Webhook, Dynamic List, Typing), the trigger was connected directly to the Template, with no possibility of inserting logic into the medium. With this update, you can place any component of the FlowBuilder before the Template - just as it already worked in inbound flows (bots).

This enables the most requested use case: . Add the Waiting Time component in “Time Window” mode before your Template and define what days and times the flow can run. If a contact comes in outside of those hours, the flow automatically waits until the next valid period. The time zone is taken from your company settings.

In addition to schedules, this opens up other useful cases: customizing the message according to product segment with a Conditional, A/B testing between two templates, or enriching contact details before sending with the Format component.

In the FlowBuilder, open any flow with a Webhook, Dynamic List, or Typing trigger. When you drag from the trigger, you'll see all the available components. For the time window, add a Waiting Time component and select “Time Window” before adding your template.

Performance metrics are available at two key moments: before sending (health of your templates) and after sending (performance of your campaigns). Everything from Templates, Campaigns and FlowBuilder.

, we added five new columns: Sent, Delivered, Read, Answered, and Failed. Compare performance at a glance and click on any metric to open a side panel with the breakdown in quantity and percentage, plus four optimization recommendations.

, when you select a template, a health traffic light appears above the preview. Click on it to see the full metrics. If the template has a high error rate, you'll see a red alert before submitting.

, the health indicator appears in the side panel when you select a template node — so you can identify problems without changing screens.

. From the Campaigns, Webhooks, Typifications and Dynamic Flows tables, open the actions menu (...) and choose “Campaign Metrics”. A side panel shows you actual shipping performance with six indicators: Customers, Sent, Read, Answered, Failed and Not Delivered — each with its number and percentage.

You can now configure interactive carousel-type messages directly from the “Message” component in the Flowbuilder, both in Inbound and Outbound flows.

Each carousel can have between 2 and 10 cards. Each card includes an image or video, its own description and up to 2 action buttons. Everything is saved inside the node — no additional template is created.

💬 Do you have feedback or questions? Leave us a comment in the feedback section ☝️