Vermilion

Last update August 13, 2025

AI hub

Vocalize - A new AI gamification tool to engage end users

Vocalize is an AI-powered voice gamification tool that is designed to make lead collection engaging and competitive. Instead of filling out forms with their information, end users are invited to play a game and compete for a high score.

To participate, end users must provide basic information such as their name and company. Save this information in People for lead generation.

To use Vocalize, create the Vocalize campaign, and then add it to your Answers chatbot.

For more information, refer to the Vocalize documentation.

Analyze

Dashboard usability and filtering enhancements

We have improved the Analyze Dashboard to help you work faster and extract insights more easily.

What's new

• Line charts are now the default for SMS and MMS delivery metrics (replacing bar charts).
• Tooltips show key values instantly, no need to click or hover precisely.
• Filters persist across most channels (for example, SMS to WhatsApp), streamlining multichannel analysis.
• Active filters are now visible on the main dashboard view for better context.
• Charts can be sorted by metrics like delivery rate, application, or entity.
• Country filter now only shows countries with actual traffic, so there are no more empty or irrelevant results.

These updates make it easier to detect trends at a glance, streamline cross-channel workflows, speed up access to key insights without the need to export data, and provide cleaner, more relevant filtering options tailored to your actual traffic.

To learn more, refer to our Analyze Dashboard documentation.

Apple Messages for Business

Delivery and Inbound message events now available in Subscriptions

You can now configure subscriptions for Apple Messages for Business (AMB) through both the Subscriptions API and the web interface.

Previously unavailable, AMB and its associated events, Delivery and Inbound message, are now exposed for use in Subscriptions. You can now subscribe to those events using the Subscriptions API or configure them directly through our web interface.

Key benefits

• Channel support: AMB is now available as a selectable channel when configuring Subscriptions.
• Expanded event tracking: You can subscribe to both DELIVERY and INBOUND_MESSAGE events for AMB.
• Improved integration flexibility: Configure subscriptions using the API or use our web interface, whichever suits your workflow.

Learn more

• How to configure subscriptions in our web interface
• Full list of supported events
• Subscriptions API reference (opens in a new tab)

Apps and Integrations

Enhancing "Broadcast Message" channel in Oracle Eloqua

Recently, Infobip introduced a universal "broadcast message" channel for Eloqua, powered by Infobip's Messages API, allowing companies to send communications via RCS, Viber, and MMS, in addition to the previously supported SMS and WhatsApp channels (which use separate messaging actions). This upcoming feature update will unify SMS into the "broadcast" channel and extend the broadcast channel’s feature set to include URL shortening and tracking, two-way messaging (including inbound message capture and opt-out handling), resulting in a more streamlined, powerful, and efficient messaging workflow.

New features

• Built-in URL shortening and click tracking for all messages sent through the universal broadcast channel (RCS, Viber, MMS, and SMS).
• Support for two-way messaging: inbound message capture for replies on all channels, and automated handling of opt-outs to comply with regulations.
• Integration of SMS capability into the broadcast channel, allowing for eventual removal of the standalone SMS action.
• Unified message tracking and reporting across all broadcast-supported channels.

Key benefits

• Marketers need to streamline and enhance their multichannel messaging workflows within Oracle Eloqua, including better analytics and conversation management features.

For more information, go to the Infobip Exchange listing (opens in a new tab).

To see the documentation, go to Oracle Eloqua messaging.

Multi-account support for Oracle Eloqua messaging

Infobip’s messaging integration for Eloqua currently limits users to connecting only a single Infobip account. For organizations requiring separate accounts for different teams, regions, business units, or to meet billing and compliance requirements, this presents a significant limitation. The Multi-Account Support feature will allow clients to connect and manage multiple Infobip accounts within their Eloqua app, unlocking greater operational flexibility and control.

Many enterprises use more than one Infobip account for a variety of reasons: regional operations, distinct business units, brand segmentation, or separate billing needs. Currently, the Eloqua Infobip messaging integration only supports connecting a single Infobip account, which limits campaign agility, regional compliance, and complicates reporting and resource management.

New features

• UI and management tooling in Eloqua to add, configure, and manage any number of Infobip accounts.
• Per-campaign or per-message action selection of the Infobip account to use, based on organizational needs (region, product line, business unit, etc.).
• Centralized reporting and message status dashboards that respect and support multi-account activity, improving clarity and governance.

Key benefits

• Enables seamless connection and management of multiple Infobip accounts within a single Eloqua instance.
• Provides flexibility for campaign managers to select the appropriate Infobip account for each campaign segment—supporting varied billing, regional sender IDs, compliance settings, and operational workflows.

For more information, go to the Infobip Exchange listing (opens in a new tab).

To see the documentation, go to Oracle Eloqua messaging.

Workflows based on additional entities in HubSpot messaging

Previously, Infobip’s HubSpot messaging integration has supported messaging actions triggered only by “contact”-based workflows. However, many business events relevant to sales, marketing, and operations originate from other key HubSpot objects. This new feature extends Infobip messaging capabilities, allowing workflows to be triggered not only by Contacts, but also by Companies, Deals, and Custom Objects—broadening the scope of automation and communications in HubSpot.

Workflows in HubSpot can be initiated by diverse entities—Contact, Company, Deal, or Custom Objects—but Infobip messaging actions have been limited to Contact-based triggers. This restriction prevents seamless alignment of automated communications with critical business events, such as notifying decision makers on Company records, sending updates based on Deal stage progression, or reaching out based on changes to unique business entities managed as Custom Objects.
Marketers, sales, and service teams need to automate personalized messages linked to the full context of the customer lifecycle, not just contact-related events.

New features

• Infobip messaging actions can now be placed in workflows triggered by any supported object type: Contact, Company, Deal, or Custom Object.
• For each entity, associated contact(s) can be dynamically identified and targeted, supporting targeted notifications, alerts, and campaign messages based on business context.
• Custom Object support brings messaging automation to any unique business process tracked in HubSpot—such as event registrations, property listings, support requests, or project workflows.

Key benefits

• Enables direct messaging actions in HubSpot workflows triggered by Company, Deal, or Custom Object records—empowering operational, transactional, and lifecycle communications at every business milestone.
• Improves the timeliness and relevance of messages, ensuring that outreach aligns with events such as deal closures, account updates, or custom process steps.
• Eliminates the need for complex workaround logic or manual handoffs to reach associated contacts for non-contact-centric workflows.

For more information, go to the Infobip Exchange listing (opens in a new tab).

To see the documentation, go to HubSpot messaging.

Two-way on HubSpot workflows - inbound messages as workflow triggers

This feature introduces the ability for inbound messages—such as SMS, WhatsApp, or other integrated channel replies—to act as triggers in HubSpot workflows, establishing a foundation for robust two-way messaging automation.

Until now, HubSpot workflows could not be directly triggered by inbound messages or replies from customers. This meant any automation or process (like lead qualification, follow-ups, acknowledgments, or personalization) could only be initiated from system-side activities, limiting true conversational automation and responsiveness.

New features

• Users can define workflow enrollment triggers based on the reception of inbound messages, specific keywords, or conversational criteria.
• Supports setting up conditional workflow branches and actions (e.g., send follow-up, assign to owner, tag record, escalate to human agent) based on customer replies or message content.
• Empowers chatbot and live chat flows to hand off relevant data to workflows for further automation, tracking, and reporting.

Key benefits

• Enables workflows to launch or branch based on specific inbound messages or keywords—unlocking use cases like auto-responses, sales routing, escalation, opt-in/out processing, and dynamic lead journeys.
• Facilitates full two-way messaging with customers, integrating inbound responses from SMS, WhatsApp, or other supported channels, for both support and marketing use cases.
• Reduces manual intervention and response time, creating a more automated, personalized, and conversational customer experience.

For more information, go to the Infobip Exchange listing (opens in a new tab).

To see the documentation, go to HubSpot messaging.

Improving visibility and management of workflow messages in HubSpot Inbox

This feature focuses on enhancing message transparency and tracking within HubSpot by bridging the gap between automated workflow messages and ongoing Inbox conversations. Currently, workflow-generated outbound messages (such as those sent from automations in sales, marketing, or service) appear in the appropriate Inbox conversation threads only if the end customer has replied to the initial workflow message.

Workflow messages often fail to appear in the relevant HubSpot Inbox conversations unless a customer replies, resulting in incomplete conversation histories and inconsistent context for agents. Agents and teams lack a holistic view of all customer communications—including automated workflow actions—within a single conversation thread. Outbound messages can start unnecessary new conversations, fragmenting customer history across threads unless carefully managed. Message status updates (delivered/read) are not always reflected in real time, making it harder for teams to track engagement. In workflow actions, the associated account name is not easily visible, reducing operational clarity.

New features

• Automated logic for appending workflow messages to the correct ongoing conversation, based on recipient and context, or starting a new thread according to a configurable toggle in app settings.
• Real-time Inbox message status updates reflecting when messages are delivered or read.
• Workflow action UI updates to show and select account names clearly.

Key benefits

• Ensures (if user selected this option in config) workflow-originated outbound messages are always added to existing Inbox conversations if they exist, making all customer communication accessible in a unified thread regardless of customer replies.
• Centralizes both automated and agent-driven communication, improving collaboration, team awareness, and response efficiency.
• Adds configuration options for admins to decide whether each outbound workflow message should create a new conversation or be appended—even to new recipients—empowering organizations to control message organization as suits their processes.
• Improves the accuracy of message status indicators in the Inbox, with real-time updates for delivered and read events.
• Adds account name visibility directly in workflow actions, giving teams more context and reducing operational ambiguity.

For more information, go to the Infobip Exchange listing (opens in a new tab).

To see the documentation, go to HubSpot messaging.

Salesforce Marketing Cloud: register and manage WhatsApp templates

Currently, SFMC users leveraging Infobip’s WhatsApp channel integration can only send messages using pre-registered WhatsApp templates. All template management (creation, registration, editing) is handled outside of SFMC via the Infobip portal, creating friction for marketers who must switch platforms for every new campaign or template variation. This feature introduces in-SFMC template management, empowering users to create WhatsApp templates directly within the SFMC environment.

Marketers need campaign agility—frequently creating, updating, and registering WhatsApp templates for new campaigns, variants, and localization. Current workflow requires users to leave SFMC and log into the Infobip portal for template management.

New features

• Native WhatsApp template editor within SFMC, supporting the creation and preview of message templates with all required elements (variables, media, languages, categories, etc.).
• Direct registration and submission of templates for WhatsApp’s approval workflow from within SFMC, complete with validation and status feedback.
• (Future phase) Interface for managing template edits, versioning, and overview of approved, pending, or rejected templates—keeping users in a single, familiar marketing environment.

Key benefits

• Allows WhatsApp template registration directly within the SFMC interface—no more context-switching or redundant logins.
• Accelerates campaign launch times by removing platform barriers, letting teams quickly design, localize, and register templates for approval and use.

For more information, go to the Infobip Exchange listing (opens in a new tab).

To see the documentation, go to Salesforce Marketing Cloud messaging.

India regional deployment of Responsys

For finance institutions operating in India, strict data residency regulations require that all sensitive data—and often the entirety of application data flows—remain within country borders. As a result, SaaS solutions such as Oracle Responsys including all integrations must provide in-country (India) deployment, ensuring frontend, backend, and database components all run within an Azure Cloud region physically located in India. This theme addresses the architectural, operational, and migration requirements for creating, managing, and scaling a regionally compliant, multi-location deployment of the Responsys application.

Financial sector clients in India are subject to RBI and other regulations mandating strict data localization for sensitive, personal, and transactional data. Hosting a single instance of Responsys in a non-Indian cloud region is non-compliant and risks penalties, operational disruption, or inability to serve the regulated market. There is a need for a robust architecture that not only supports an India-only instance but also enables future expansion to other regions or markets as regulations or business opportunities dictate.

New features

• Design and implementation of region-specific app mirrors: full stack duplication (frontend, backend, DB) deployed in Azure India.
• Strict data residency controls: network, storage, and backup configurations guaranteeing no sensitive data leaves the Azure IN region after migration.
• Parallel, synchronized deployment and updates across all selected regions, guaranteeing feature parity and operational consistency.
• At installation or onboarding, logic to present and route clients to their designated regional instance.

Key benefits

• Guarantees ongoing compliance with Indian data residency requirements by hosting all application components within the IN region in Azure Cloud.
• Modular, multi-location architecture allows rapid deployment of replicas in other cloud regions as regulations or global expansion require.
• Enables customer choice/flexibility at deployment and app installation, while supporting seamless, risk-managed data migration and service continuity.

For more information, go to the Infobip Exchange listing for SMS (opens in a new tab) and Infobip Exchange listing for WhatsApp and Viber (opens in a new tab).

To see the documentation, go to Oracle Responsys messaging.

Broadcast

Improved editing for RCS rich card and carousel messages in Broadcast

The Broadcast content editor now allows you to create RCS rich card and carousel messages without uploading media, in full alignment with Infobip's API and Google's RCS specifications.

Previously, the editor incorrectly enforced media upload for all RCS messages, even when it was optional. This caused validation errors in cases where only text and suggestions were needed. For example, users can now create a rich card with a title, description, and reply button, without needing to upload an image or video.

With this update:

• Media upload is no longer required when the creating a rich card or a carousel message.
• Validation behavior in the editor matches Infobip's RCS API logic.
• Users can now create valid RCS messages without being blocked by incorrect constraints.

Key benefits

• Aligned with official specifications: Editor validation now follows Google's RCS guidelines and Infobip's API structure.
• Improved usability: Enables faster, smoother message creation without unnecessary validation blocks.
• Fewer support issues:Eliminates discrepancies between the editor and API, reducing user confusion.

To learn more, refer to our Broadcast documentation.

Conversations

Audit logs improvements

This release brings improvements to Conversations audit logs, with extended tracking for key configuration changes.

You can now see detailed logs for actions related to different events, such as queues, tags, account capacity, and more.

Additionally, you can track the time spent on key pages, including Conversation logs and Audit logs, to help improve usability insights.

See the Logs page to learn more.

Queue-level waiting strategies

You can now configure waiting strategies at the queue level in the contact center platform. Previously limited to the phone number level, this enhancement gives you more flexibility to manage customer interactions per queue.

With queue-level configuration, you can:

• Set unique wait times per queue

• Offer custom callback options

• Define escalation paths specific to each queue

For more information, refer to the Waiting strategy section in Calls, and the Waiting strategy for messaging channels.

Redesigned call modal for enhanced usability

This release introduces a redesigned call modal to provide a more modern, intuitive experience for agents.

The updated interface includes:

• New call control icons for easier navigation

• Minimize/maximize functionality to support multitasking

• Clear visual indicators for active calls

This enhancement simplifies call handling and improves overall agent efficiency.

New dark mode color palette is available

In this release, we’re introducing our dark mode color palette to enhance contrast, meet accessibility standards, and create a more comfortable, eye-friendly experience—now available in the More work and All work sections in Conversations.

To switch between light and dark modes, select the sun icon.

Email

Late bounce events over webhook

This feature introduces late bounce notifications over a webhook. Previously, late bounce events were processed and retrieved only using the default return path. When configuring a custom return path, Infobip could not receive or accurately interpret late bounce feedback, leading to incomplete or missing delivery status information.

This limits clients’ visibility into the final status of their messages, impacting delivery monitoring and troubleshooting.

New features

• Subscribe to opt-in to late bounce event notifications independently of the return path.
• Processing of late bounces through the default return path for clients who do not define a custom one.
• Dual approach to guarantee that late bounce events are captured and accessible under all client configurations.

Key benefits

• Ensures Infobip always receives late bounce feedback regardless of clients’ return path configuration.
• Enables clients to explicitly subscribe to late bounce events, improving access to delivery failure information.
• Provides more reliable and flexible delivery reporting, helping clients optimize their messaging strategies and improve recipient engagement.

A client using a custom return path can keep their setup while still reliably receiving late bounce notifications through event subscription, avoiding any disruption in their message tracking.

For more information, see Receive user events webhook (opens in a new tab) and Late bounces.

Envelope domain

Previously, if you registered a domain and used the same root domain for both the header-from and envelope-from addresses when sending emails, this causes the root domain’s reputation to be directly impacted by bounces, complaints, or other sending issues. Negative reputation events on the sending side can harm brand reputation and deliverability.

New features

• Automatic creation of a unique envelope domain (a subdomain like ib38450.example.com) when registering a root domain.
• Outgoing emails use the root domain in the header-from address but send using the envelope-from subdomain to isolate reputation.
• Infobip will process late bounces and abuse/complaints for envelope domains, reporting back final delivery status.
• Relaxed DKIM alignment to maintain authentication passing despite the different envelope domain.

Key benefits

• Sending reputation is isolated between the root domain and a newly created envelope domain. This prevents reputation problems from affecting the main domain.
• Bounce handling and complaint feedback are managed by Infobip, improving delivery insights and abuse management.
• DKIM alignment is relaxed to allow authentication to pass smoothly despite the use of a different envelope domain.
• Better deliverability without extra domain management or complex reputation work.

For more information, see Envelop domain.

IP Pool selection over HTTP API

Previously, if you use the same sending domain across multiple departments but you could not separate sending IPs per department. This could lead to shared IP reputation and increased risk of reputation damage if one department’s email practices negatively impact the IP pool.

This feature introduces the ability to select IP pools on a per-department basis when using the same sending domain.

New features

• HTTP API supports specifying the IP pool to be used for each email send request, allowing you to programmatically associate sending traffic with the correct department’s IP pool.
• API parameters or headers that designate the IP pool to use for that particular request.
• Management user interface and/or API endpoints for clients to manage IP pools and associate departments with pools.
• Detailed logging and reporting that reflects the IP pool used for the email, enabling monitoring at granular levels.

Key benefits

• Isolate sending reputations on a per-department basis while using the same sending domain, preserving overall domain reputation.
• Improves deliverability by allowing departments with distinct sending behaviors to use dedicated IP pools, reducing the chance of cross-contamination of reputation issues.
• Provides greater control and flexibility over API to dynamically select IP pools as part of sending workflow, enabling automation and integration with internal systems.
• Simplifies management by allowing centralized domain usage and decentralizing IP management per department.
• Enables detailed reporting and analytics per IP pool/department to monitor performance and identify issues faster.

For more information, see the Email with IP pool ID example in Send Email message (opens in a new tab).

New endpoint for sending in MIME format over HTTP API

This new feature introduces support for accepting incoming data in MIME format over the HTTP API.

Previously, users who want to send MIME formatted messages over the HTTP API could not do so, limiting the flexibility of message formatting.

New features

• HTTP API will now accept incoming messages in MIME format.
• Submit MIME formatted messages via HTTP requests.
• Aligns HTTP API capabilities with the existing SMTP API MIME support.

Key benefits

• Send MIME formatted messages over the HTTP API for greater flexibility in message formatting and facilitating richer content capabilities.
• Improves consistency between HTTP and SMTP APIs, simplifying the development experience and increasing integration options for clients who rely on MIME content.

For more information, see Send MIME email (opens in a new tab).

Essentials

Changes to accessing or upgrading customer engagement solutions

Affected solutions

• Answers
• Conversations
• Moments

Changes

The following changes are now applicable:

• Customers can now book a demo for these solutions with an Infobip product expert. For more information, refer to Book a demo.
• To purchase these solutions, customers must contact their Infobip account manager.
• To upgrade the plans for these solutions, customers must contact their Infobip account manager.

Live chat

Advanced customization improvements

This release introduces expanded advanced customization options for the Live Chat widget, giving you full control over its appearance across both web and native mobile platforms.

You can now personalize the widget’s design to align with your brand guidelines, adjusting colors, logos, fonts, icons, and more for a seamless, consistent customer experience.

Key benefits

• Full brand alignment - Match the widget to your brand identity with customizable fonts, colors, logos, icons, and other visual elements.

• Cross-platform consistency - Ensure a unified look and feel across both web and native mobile apps.

Check the updates here.

Messages API

Control delivery order of RCS messages

We have introduced message ordering controls for RCS messages sent using the Messages API.

This feature gives you fine-grained control over the sequence and behavior of bulk message delivery, improving the conversational experience when multiple messages are sent to a single recipient.

What's new

You can now:

• Preserve the order of up to 10 RCS messages to a single destination.
• Use stop-on-failure logic to control whether the sequence continues if a message fails.
• Combine MMS/SMS failover with up to 2 ordered RCS messages for fallback logic.

Common use cases

• Send a file followed by a caption in the correct order.
• Structure multi-step onboarding or surveys using multiple RCS messages.
• Use fallback logic for media-rich content (for example: RCS to MMS if delivery fails).

How it works

Add the messageOrdering object to your request:

{
    "messageOrdering": {
        "respectOrder": true,
        "stopOnFailure": true
    }
}

• respectOrder: Enforces the message order defined in the request body.
• stopOnFailure: If set to true, the sequence will stop if any message fails to deliver. Can only be used when respectOrder is true.

To learn how to configure this action, see the See the Send a Messages API (opens in a new tab) page for details.

For an overview of the Messages API capabilities, see our product documentation.

Moments

Transfer IVR calls to your custom Calls API application

You can now transfer IVR calls from a flow to your custom Calls API application. This enables you to manage calls within your application.

Use the new Transfer call to voice application element to transfer the call.

Numbers and Compliance

Resource Request Service - alphanumeric sender request

This release includes a new functionality update to the Resource Request Service for managing alphanumeric sender requests more effectively. API users benefit from automatic validation of requirements, which includes checking if all requirements have been provided or if any information is missing.

In addition, API users can update their number purchase requests to include all required information, and the option to cancel the request if they decide not to complete the purchase.

This new feature makes it easier to validate, update, and cancel number purchase requests through both the API and web interface.

Key benefits

• More control over updates to number purchase requests.
• Automatic validation of number purchase requests.

For more information, see Resource requests.

Update to Toll-Free Number registration

In this release, Toll-Free Number (TFN) registration is now available using the US Sender Registration app. This new process removes the requirement to complete and submit Word documents and improves the overall experience.

Key benefits

• Single solution for registering US senders for TFN and 10DLC and short code
• Realtime tracking on registration and rejection/appeal functionality

For more information, see Toll-Free Number verification.

People

Automatic profile creation for Conversations sessions

Profiles are now automatically created in People when a Conversations session starts.

The following happens:

• If a profile already exists for the end user, Conversations product events, such as the start or end of a session, are added to the profile.
• If a profile does not exist, a new profile of type Customer is automatically created in People. The product events are added to this profile.

The feature is enabled by default for all new Conversations customers.

Existing customers must manually enable tracking of the following Conversations session events in the People events configuration page. Customers must also acknowledge profile auto-provisioning.

• Conversation Created
• Conversation Closed

RCS

WebView now supported in RCS templates and Freeform messages

Vodafone Idea has confirmed that RCS templates and FreeForm messages support WebView, and we have implemented this across:

• Templates UI

• Templates API

• FreeForm messages via VIL gateways

Brands can include rich WebView experiences, such as product pages, checkouts, or forms—directly in RCS messages delivered over Vodafone Idea, creating smoother, app-like journeys within the native messaging experience.

Message sequencing for RCS through Messages API

You can now use message sequencing when sending RCS messages in bulk through the Messages API.

This functionality allows you to control the order of multiple RCS messages sent to a single destination and apply optional stop-on-failure logic, improving how structured content is delivered to end users.

Key benefits

• Preserve message order for up to 10 RCS messages per recipient.

• Stop on failure to halt delivery if a message in the sequence fails.

• Combine with SMS or MMS failover for fallback options when delivery issues occur.

WhatsApp

MM Lite API: Local storage support now available

As of July 23, 2025, Meta's local storage feature is supported for MM Lite API in the same countries as the Cloud API.

Local storage introduces a time-to-live (TTL) policy, which defines how long message content may remain temporarily accessible outside the selected region:

• MM Lite API: up to 90 minutes
• Cloud API: up to 60 minutes

After the TTL expires, message content is deleted from Meta's data centers outside the selected region and retained only in the designated local storage region.

If local storage is already enabled for a Cloud API sender, the same setting now automatically applies to MM Lite API.

For more details, refer to our Local storage for data at rest section.

AI Agent for WhatsApp Flows

Infobip brings you the first-ever AI-powered flow JSON builder in the industry, helping you reduce development costs, speed up delivery, and scale your WhatsApp use cases faster.

The AI Agent for WhatsApp Flows enables both business users and developers to generate Meta-compliant WhatsApp Flow JSON using a simple natural language prompt. You can access the AI Agent via the Infobip web interface (no-code interface for static flows) or API (supporting both static and dynamic flows).

Key benefits

• Faster time to market: Generate flows in minutes instead of days or weeks
• Reduced manual effort: Let AI handle the JSON generation and structure
• Full Meta compliance: All flows follow WhatsApp's official flow component standards
• Web interface and API support: Choose the integration model that fits your workflow

For details on how to get started, see our Use AI Agent to build WhatsApp Flows section.

New experience for buying pre-verified numbers

You can now buy pre-verified WhatsApp numbers directly through the Infobip web interface, significantly reducing setup time and improving sender registration reliability.

Previously, WhatsApp number verification was handled during the sender registration process. With this update, a business looking to onboard a new WhatsApp sender can now purchase a number that has already passed verification checks, complete the sender registration process, and start messaging customers, all in one seamless flow.

Key benefits

• Faster onboarding: Pre-verified numbers eliminate the need for manual authentication steps.
• Improved control: Infobip can ensure number integrity and prevent external registration attempts on owned numbers.
• Streamlined experience: Users can select, purchase, and register WhatsApp numbers in a single guided flow.

How it works

• When registering a WhatsApp sender, select Buy a new number (Recommended).
• You will be shown only pre-verified numbers available for your selected country.
• Once purchased, the number can be used immediately in the registration flow, no code entry or manual verification needed.

To see the full step-by-step process, visit the WhatsApp sender registration guide.

UX enhancements

Infobip web interface is now available in Ukrainian

You can now use the Infobip web interface in Ukrainian.

Ukrainian has been added to our list of supported languages, along with Albanian, Arabic, Bosnian, Chinese (Simplified and Traditional), French, German, Greek, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Slovenian, Swedish, and Turkish.

To change the language, go to the Login page or go to Settings > User profile.