Changelog

The visual journey builder now splits waiting and talking into two dedicated blocks. Wait for reply pauses a journey until the customer responds, and Handle conversation is a first-class card your AI agent uses to hold a back and forth toward a goal. You can expand and edit a block in place and drag it to reorder, so building a multi-step flow is clearer and faster.

Creating an initiative is now a guided four-step wizard: set it up, configure the agent, choose what data to extract, and shape the journey. Each step keeps the choices in front of you, so you can launch a research or outreach initiative with confidence and step back to adjust anything before you go live.

A few smaller improvements from the last couple of days.

• Editable customer details: edit a customer's name right in the inbox, and your change overrides the synced data everywhere the agent uses it.
• Simpler WhatsApp templates: message templates are now managed with just your phone number, no technical account identifier needed.
• WhatsApp location shares now render as a shared location instead of a blank bubble, and your AI agent can read them too.
• Richer CSV uploads: every column in an uploaded CSV is captured as a customer attribute, and the upload wizard asks for an ID column so contacts match cleanly.
• Clearer journey conditions: boolean decision steps now use a simple True or False selector, and an unset condition is caught before you publish.
• The dashboard now follows your light or dark theme.

The journey builder now uses clearer building blocks so it is easier to see what each step does. The old Conversation step becomes Wait for reply, a new Handle conversation block lets you choose whether AI or a human takes over, and the confusing send-immediately toggle is replaced by an explicit send-window step. Building an outbound journey now reads the way it runs.

The Metrics dashboard has a refreshed layout with a new funnel overview, softer sentiment colors, and clearer labels, so your results are easier to read at a glance. Response rate and the conversation funnel now count real inbound replies, so the numbers reflect what actually happened.

The metrics view got a rework that makes results easier to read at a glance. A new funnel shows how contacts move through each stage, the response rate and funnel are now based on real inbound messages, and the layout, colors, and labels are cleaner so you can spot what is working faster.

A few smaller improvements from today.

• Contact uploads now capture every column in your file as a person attribute, so no data from your upload is left behind.
• The contact upload wizard now asks for an ID column, so records reconcile cleanly instead of creating duplicates.
• Journey decision conditions now use a clear True/False selector and can no longer be published while left unset.

You can now maintain a Do Not Contact list per organization from the new dashboard under People, so opted-out contacts are never messaged again by mistake. A contact is added automatically when they reply STOP, use the one-click unsubscribe link in an email, or is added manually, and every outreach campaign, journey message, and automated follow-up checks the list before sending. A team member can still send a message by hand when it is truly needed, with a clear warning and a permanent audit log, and the dashboard now supports search and pagination to keep long lists easy to manage.

A few smaller improvements from today.

• WhatsApp replies from your AI agent now arrive faster, thanks to a streamlined reply pipeline.
• The segments builder is denser and easier to scan, with a cleaner header and no more horizontal scrolling on smaller screens.
• Your AI agent can now see images customers send in a conversation, not just read the text, so it responds with the full picture in mind.

A few smaller improvements from today.

• Journeys can now branch on any event property, not just the reserved set, so decision and case steps react to the full detail of your custom events.
• Reports now hide cards that have no data (like reward eligibility when no reward is configured), so the view stays clean and shows only what is relevant.
• The journey builder node editor is now fully localized, so the controls read in your language throughout.
• Revenue figures are more accurate: discounts that are already used up no longer count against net amount.

You can now add a Case node in the journey builder to route people down many paths based on a single attribute value, instead of chaining several decision steps. Each branch has its own outcome and there is a required default, so everyone lands somewhere and no one silently falls through.

You can now configure your agent per channel from a new settings screen: pick a default agent, toggle AI on or off, and set the namespace for each channel independently, with a fallback to your organization defaults. WhatsApp and web chat can behave differently without extra setup.

The public REST API and MCP server can now create and manage your research Initiatives, not just read them: create a draft, update it, cancel or archive it, and link a WhatsApp outreach template to an initiative. You can also create, list, and check the approval status of WhatsApp templates, so you can run campaigns end to end from your own systems.

The in-app assistant can now draft a complete email template from a simple chat prompt, filling in the copy and the right customer variables for you. Describe the email you want and start from a working draft instead of a blank canvas.

A few smaller improvements from today.

• Email templates now show variable chips consistently everywhere, and a bug that sent a raw token instead of the value is fixed.
• You can now publish or unpublish an email template, and the send-test button shows a loading state so it no longer looks stuck.
• New themed starter templates give you image-forward, styled emails to begin from, with variables available in the subject line.
• The engagement detail view has a new Data tab, so you can see a person's context and workflow state at a glance.
• Funnel and coverage numbers in reports now use honest denominators and rounded, attributed cards, so the figures you show match reality.

You can now author on-brand email templates in a rich editor: write your copy, drop in customer variables from a slash menu, and start from a gallery of ready-made templates (welcome, onboarding, reactivation, and more). Send a test to yourself, then send for real from your own verified domain, so email becomes a fully operated channel alongside WhatsApp.

In the visual Journey Builder, WhatsApp message steps can now pull fields from your custom events as variables. When a journey is triggered by an event, pick its properties (like plan_tier or order_total) from a dropdown and drop them straight into your message, so each send is personalized with the data that started the flow.

The public REST API and MCP server now read your research Initiatives and the data they collect: list and get initiatives, participants, and their extracted variables, plus a per-initiative summary of engagement and results. Personal and internal fields stay hidden, so your own systems and agents can pull insights safely.

A few smaller improvements from this week.

• You can now reference context files inside an initiative's context block with an @ mention, and they render as inline chips so it's clear which files the agent is using.
• The initiative detail view now shows attached assets as chips, so you can see what's linked at a glance.
• The initiative tester can now impersonate pre-launch enrollment requests, so you can preview exactly how an enrollment will behave before you go live.
• The initiative tester opener no longer invents a placeholder name, so test conversations start with a clean, realistic first message.
• The agent no longer shows internal tool preamble in its replies, keeping customer-facing messages clean.

A few smaller improvements from this week.

• Archived templates are now viewable: a new "Show archived" toggle on the templates list lets you find and review templates you previously removed.
• WhatsApp templates now submit for approval automatically when you create them, so you no longer need a separate manual step.
• The initiative tester now opens with a preview of the journey's real WhatsApp template instead of a generated message, so what you test matches what customers receive.
• The journey builder no longer discards unsaved changes when you switch browser tabs and come back, protecting work in progress on the canvas.
• Survey re-extraction is unblocked: initiatives without a fixed schema can be re-analyzed, so you can refresh survey results after making changes.

You can now enroll people into a journey by picking them manually from your CDP or by taking a snapshot of an entire segment, with no CSV upload required. Each source can be added as pending or start the journey right away.

Journeys are now available to every organization, no longer behind a preview flag. Build automated, multi-step flows over WhatsApp in the visual builder: branch on customer data with decision nodes, wait, send messages, run a conversation, and dispatch events, with each path ending in its own outcome. Access is role-based: admins have full control, and other roles get read-only access.

Message templates that attach a PDF now show the first page of the document in the WhatsApp media preview, instead of a generic file icon. You can confirm you attached the right document before sending.

A new public REST API lets you create and preview segments and read your CDP catalog (relationships, custom object types, and relationship types) from your own systems. The same data is available through an MCP server, so your own agents can query Boom directly.

A handful of smaller improvements across segments, journeys, and templates:

• Personalize messages with computed values: calculated segment values, such as a summed subscription amount, can now be used as variables in journey messages.
• Import people by CSV: add people to the CDP People tab through a CSV upload or one by one.
• Cleaner template management: Boom now creates fewer duplicate template variations per round, and follow-ups reuse approved copy.
• Smoother CSV enrollment: the add-contacts wizard handles column mapping and large files more reliably.
• Accurate relative times: recently created records no longer show timestamps in the future.
• Tidier initiative assets: the assets inherited from your organization now start collapsed.

When you create an initiative, Boom now builds the first draft of its journey and outreach messages automatically in the background, including a message for each follow-up round, reusing your approved templates when they fit. Starting a new campaign goes from a blank canvas to a ready-to-review draft.

You can now set how far the agent digs in on each guiding question, from no follow-up to a deep, multi-turn probe. Use lighter follow-ups for quick survey-style questions and deeper ones where you want richer, more detailed answers. This gives you finer control over the length and depth of every interview.

The Wait step in journeys can now hold a contact until a specific date and time, or until the next weekday you choose (for example, the next Monday at 9 AM) in your organization timezone. Before, a wait could only pause for a relative amount of time. Now you can align messages with launches, deadlines, or business hours.

A few smaller upgrades:

• A zoomable image viewer in conversations, WhatsApp style, with pinch, scroll, and double-click zoom plus thumbnails.
• Click to copy any value in the conversation context panel.
• Starting a New message is no longer blocked when the contact already has a conversation.
• Connect a database through an SSH bastion (jump host), for data behind a private network.

You can now build a segment from a library of common templates (for Shopify, Skio, and connected databases) instead of starting from a blank filter. Pick a template, adjust it, and your audience is ready. Segments are also now reachable over the public API.

Creating an initiative is now just an objective and a bit of context, and you are done. The long multi-field setup form is gone, so you can launch a research or outreach initiative in a fraction of the time.

A handful of smaller fixes across the inbox and engagement views:

• The engagement timeline now shows which branch a decision took and how long a delay lasted, in English, Spanish, and Portuguese.
• The conversation list filter can now include archived initiatives.
• Runs lists show a contact's email instead of a raw internal id.
• You can only reply to a conversation that is assigned to you, so replies no longer get lost in the unassigned view.
• A cleaner events table with corrected relative timestamps.

The Shared Inbox is now on for every team on your plan, with no setup required. Anyone with inbox access can see and reply to conversations across WhatsApp and your other channels from one place.

WhatsApp template buttons can now carry personalized link variables, so each recipient gets their own URL (a unique reward link, a tailored checkout) resolved at send time. Template header images are also saved now, so they appear in the shared inbox instead of showing as text only.

The inbox got a round of polish: resolved conversations now look visually distinct, the All view shows only open conversations with a count badge, actions update the list instantly, and the context panel surfaces a contact's channel and identity even when there is no match in your data yet.

Journey messages can now pull in variables from your data and from the events that triggered them, so each customer gets a message written for their context. Picking the event that starts a journey is clearer too, with a branded event picker.

A new People directory lets you browse everyone in your customer base in one paginated table, then open any profile to see their attributes, events, and conversations across tabs. Find the right person and understand them at a glance.

Segments can now use computed attributes like number of orders or total spent, calculated for you from each person's history, plus match on list and tag values. Build audiences around behavior, not just static fields.

You can now connect your Skio subscriptions to Boom from the Integrations page, using a self-serve API key. Bring your subscription data in so your segments and journeys can act on it.

Journeys got three new controls: a frequency cap so a customer never gets too many messages, a node that fires an event into the CDP as the journey runs, and the ability to remove a customer from a journey the moment a chosen event happens.

Boom now supports more than one WhatsApp business account at once. Choose which number sends each step of a journey, and templates stay scoped to the account they belong to across journeys and the inbox, so the right sender and the right templates always line up.

Segments can now filter across related records and reach into nested attributes. Build a segment that follows the link from a customer to their orders, or matches on a value buried inside a JSON field, all from the same builder.

Describe the audience you want in plain language and the agent builds the segment for you, turning your request into the right conditions, including links to related records and nested fields. No manual filter setup required.

A new analytics dashboard shows how your conversations are going, with volume over time, response times, an hourly activity heatmap, and an operator leaderboard. Filter by the dimensions that matter and see where to focus.

Boom is now available end-to-end in Portuguese (pt-BR), both the operator dashboard and the agent itself. Set Portuguese as your workspace's default language and run conversations natively in Brazil.

The shared inbox got a rework. Every conversation row now shows which channel and number it came from, a new filter bar lets you slice by channel, and search was rebuilt to scan across all sessions of a conversation, returning results in milliseconds instead of seconds.

You can now configure exactly what your operators see next to each conversation: customer attributes, related records like orders or loans, and deep links into your own systems. Set it up once and every agent gets the context they need to resolve faster.

Save your team's most common responses and drop them into any conversation with a / shortcut or a button. Edit before sending, and search across all of them. Quick replies are separate from WhatsApp templates, so they're yours to manage.

The new segments builder lets you combine conditions with AND/OR in a simple three-step flow. Schedule a segment to refresh daily at the hour you choose, and export the full membership to CSV.

Boom can now read your customer data straight from your own database, with no CSVs and no middle layer. Model real-world relationships like one buyer across many merchants, push behavioral events such as a completed payment, and segment on what your customers actually do. A documented public API keeps everything in sync with your systems.

A journey can now enroll a customer the instant something happens, like a completed order or a churn-risk signal, straight from a CDP event. There's no CSV and no waiting for the next segment refresh. The right message goes out in the moment.

You can now chat with your agent right inside the initiative. It's a live test that runs the real pipeline and streams responses as they generate, so you can try multi-turn flows and edge cases before any customer sees them.

Connect your Shopify store in a few clicks and Boom keeps customers, orders, and your full product catalog continuously in sync. The agent can reference real products in the conversation, with their images and descriptions.

Leave internal notes in a conversation thread to pass context to a teammate, drop a reminder, or note a handoff detail. Notes stay private to your team and never reach the customer.

Upload your documents, like product sheets, policies, and FAQs, and the agent searches them to answer customer questions. It pulls the right passage from the right file, so replies stay grounded in your own content.

Boom now runs on WhatsApp, Instagram, Facebook, web chat, and email (beta), with support for multiple WhatsApp numbers per workspace. Every channel lands in one shared inbox, and the agent answers with the same customer context no matter where the conversation starts.

Beyond downloading a single conversation, you can now export the transcripts of many conversations at once, as a single consolidated .txt you can hand off or analyze in bulk.

Your agent can now send images, PDFs, and video in WhatsApp conversations, not only text. It shares receipts, product sheets, or onboarding docs right inside the chat, picking the right file for the moment.

Contacts is now a dedicated section in the initiative sidebar, easier to reach, with a unified view of engagement status, filters, and bulk actions to start journeys.

You can now download the full transcript of any conversation, as plain text (.txt) for quick sharing, or as JSON (.json) to feed into your own analysis.

We deployed a new version of Boom Voice. It sounds dramatically more natural, perfect for Research campaigns running over voice.

You can now run Boom Surveys: shorter, focused conversations to ask your customers a specific question and get fast answers.

Use Surveys when a full Research interview is more than the moment calls for: a quick pulse after a release, a single follow-up question, or a targeted check-in with a segment.

We built an agent at Boom that controls the entire platform.

It can create research initiatives. Change settings. Add context about your company. All through a conversation.

Read more →

Define your research objective. Add the guiding questions you want answered. Boom does the rest.

Boom Research runs personalized, context-aware customer interviews at scale over WhatsApp, email, and voice, turning what used to take weeks of recruiting and scheduling into a 2-day workflow. Each conversation feels human, follows the thread your customer opens up, and stays focused on the questions that matter to you.

When the conversations are done, Boom synthesizes every transcript into an actionable insight report, so you go from "let's talk to users" to "here's what we learned" in days, not quarters.