Zenvia: connecting WhatsApp conversations, customer data and support
An insurance customer needs more than a quick reply after an accident. They may need to request assistance, send a missing document and learn which repair shop will handle the vehicle. Zenvia’s work with MAPFRE illustrates the practical problem behind its Customer Cloud platform: keeping those steps connected as a conversation moves between automation, business systems and staff.
The Brazilian technology company began with corporate SMS services in 2003. Today its product range includes campaign tools, sales conversations, support tickets, customer data and AI-assisted service. Its 2026 direction also includes a retreat from the costs of a US stock-market listing.
From a message to a service workflow
Customer Cloud brings several parts of customer communication into one environment. Marketing teams can segment contacts and run campaigns. Sales teams get a shared inbox and automated routing. After a purchase, support teams can organise chat and email tickets, set triggers and maintain a knowledge base.
Zenvia also offers a customer data platform, or CDP, intended to bring information together for more relevant interactions. Connections to CRM and enterprise systems matter because the message is only one part of the task: an answer about an order or account depends on the information behind it.
Its AI offering covers several jobs. Zenvia describes tools for creating campaign text, suggesting responses from a knowledge base, analysing interactions and operating customer-facing chatbots. The product also supports configuration without writing code. These capabilities need to be set up around the organisation’s own information and service processes; the presence of an AI agent does not establish that every response will be correct.
What MAPFRE’s example actually shows
In Zenvia’s MAPFRE case study, digital service extended beyond answering initial questions. Automated WhatsApp communications could provide updates on car-insurance claims, request missing documents and direct customers to a repair shop.
The figures in that case relate to the first half of 2023. Zenvia reports that opening an assistance request through the digital channel took 55% less time than by phone, and that WhatsApp accounted for 88% of bot accesses. The case also reports a 28% reduction in transfers from bots to human support.
Those results belong to the insurer’s implementation, rather than being a guaranteed improvement for every Customer Cloud customer. The account describes extensive curation and training of the solution, with staff remaining available for more complex situations. That operational work is part of the story behind the headline numbers.
When automation should hand over to a person
The useful measure of a service bot is not how long it can keep a customer in a chat. It is whether it can complete a simple task and recognise when the next step needs a person. In an insurance claim, a customer may be able to submit details and documents through a guided WhatsApp flow. A disputed claim, a missing record or a request that falls outside the defined process needs a clear route into a human support queue.
That is where the different parts of Customer Cloud meet. A campaign tool starts a planned communication; a shared inbox and routing rules decide who sees an incoming conversation; a ticket preserves the service request; and a knowledge base can give both the bot and staff a consistent answer. A customer-data layer is useful only if it brings the right account and interaction information into that workflow at the moment it is needed.
The MAPFRE case makes this division visible. The insurer used automated messages for repeatable service steps, while Zenvia’s account of the project notes that staff remained available for complex situations. The reported reduction in bot-to-agent transfers is therefore not a claim that human support disappeared. It shows that the digital flow was able to resolve more of the requests it had been designed to handle.
Messaging channels are not interchangeable
SMS, WhatsApp and RCS can all carry a customer communication, but they do not offer the same experience. SMS is useful for concise alerts and broad reach. WhatsApp supports a more conversational exchange where a customer can provide information over several messages. Zenvia describes RCS in Brazil as a richer channel for images and interactive buttons. A business needs to choose the channel around the customer’s task, permission and local availability—not simply send the same message everywhere.
How acquisitions widened the product range
Zenvia was founded in Porto Alegre by Cassio Bobsin, with business messaging through SMS as its starting point. Its later acquisitions added capabilities that now help explain the breadth of its software.
Sirena, acquired in 2020, expanded its WhatsApp sales and service tools. The 2021 purchases of D1 and SenseData added marketing automation and customer-success capabilities. Movidesk followed in 2022, strengthening ticketing and service-desk functions. The company’s current timeline identifies 2026 with a greater focus on applying AI through Customer Cloud.
Messaging infrastructure remains part of the offering. Zenvia’s channels business advertises SMS and RCS services alongside APIs for integration. Its RCS description specifically refers to sending in Brazil, with richer content such as images and interactive buttons. Channel coverage and a customer-service application are related parts of the portfolio, but they serve different implementation needs.
The Nasdaq chapter changed in 2026
Zenvia went public on Nasdaq in 2021. On 25 February 2026, however, it announced its decision to voluntarily delist and seek deregistration with the US Securities and Exchange Commission. The board cited reporting and listing costs, limited trading activity and uncertainty about maintaining Nasdaq compliance.
A subsequent filing confirmed that Zenvia submitted Form 25 on 9 March to remove its shares from Nasdaq listing. Its February announcement had scheduled the delisting to become effective on 19 March and warned that an over-the-counter market was not guaranteed. The listing decision concerns its shares and reporting obligations; the company continues to market Customer Cloud and its communications services.
For the product itself, the central task is still recognisable from the MAPFRE example: connect a customer’s question with the next useful action. Campaigns, conversations, tickets and customer records become more valuable when the person asking for help can move through that process without starting again at each step.
