Aurora
Last update January 14, 2026
| What's new | Learn more |
|---|---|
| AI agents | New AI agents product is available in Early access |
| Broadcast | KakaoTalk Broadcast: Chingu API migration to Brand Messages |
| Conversations | Consult call |
| Passive email storage (archives) | |
| RCS | Launch RCS senders from the portal with a guided UI flow AT&T test device setup is now fully automated in the US Rejection reasons are now included in sender launch webhooks |
| New onboarding option: Connect a number from your WhatsApp Business app |
AI agents
New AI agents product is now available
The AI Agents product enables you to build intelligent, autonomous agents that can execute tasks, orchestrate workflows, and improve end user interactions across Infobip solutions.
AI agents are AI‑driven systems that operate independently towards defined goals. They use large language models, tools, external systems, and structured instructions to understand requests and deliver accurate, contextual responses.
Unlike traditional chatbots that follow scripted responses, AI agents can do the following:
- Set sub‑goals and plan multi‑step workflows to complete complex tasks.
- Use tools and external systems, including APIs, databases, browsers, and third‑party services.
- Perform actions autonomously, such as sending API calls, updating records, or retrieving information.
- Identify user intent to determine the appropriate next step.
- Adapt behavior based on context and previous interactions for more natural, dynamic automation.
For in‑depth guidance and configuration details, refer to the AI Agents documentation.
Broadcast
KakaoTalk Broadcast: Chingu API migration to Brand Messages
Kakao has deprecated the Chingu API as of January 1. To ensure continuity, broadcast traffic is being migrated to Kakao Brand Messages.
As an interim solution, the Chingu API implementation has been updated to use the Brand Message API (opens in a new tab), minimizing disruption during migration.
Key features:
- Chingu API has been replaced internally with the Brand Message API (opens in a new tab) endpoint.
- Broadcast supports free-form Brand Messages only (templates are not supported at this stage).
- Targeting is limited to channel or sender friends, matching previous Chingu behavior.
- Message types such as buttons and layouts remain mostly unchanged.
- Some changes apply to:
- Image aspect ratios
- Image widths
- Maximum character counts
- Gradual customer migration is planned throughout January.
For more information, refer to the Kakao Brand Message documentation.
Conversations
Consult call
EARLY ACCESS
This feature is released as Early Access.
This release introduces Consult call functionality. It enables agents to add another internal participant to an ongoing call for a private conversation that is not audible to the customer. Agents can use consult calls to request assistance, confirm information, or align on next steps while keeping the customer on the line.
Consult calls support real-time collaboration during active interactions and help agents handle complex inquiries more efficiently.
For more information, refer to the Consult call documentation.
Passive email storage (archives)
EARLY ACCESS
This feature is released as Early Access.
This release delivers the first phase of Email storage and retrieval.
Passive email storage enables long-term archiving of email content. Archived emails are stored securely and can be retrieved when needed.
The solution supports retention of full email content (HTML, placeholders, and attachments) for up to six years. It is available for all sending methods (web and API). Pricing depends on traffic volume, email size, retention period, and storage location (cloud or on-prem).
Passive storage is intended for scenarios where historical email data needs to be accessed occasionally, such as:
- Legal requests
- Compliance and regulatory retention
- Audit activities
Learn more about Passive storage.
To enable passive email storage, contact Support or your account manager. Additional configuration options, retrieval methods, and API documentation will be added in upcoming releases.
RCS
RCS sender management: Launch requests through the UI
Clients who are not integrated with the RCS sender management API can now request sender launches directly from the web interface (opens in a new tab).
Previously, launch requests were handled through email and Excel forms with account managers. With this release, launch submission is fully supported through the user interface.
Key features
- Request sender launch directly from the web interface (opens in a new tab) using a guided form, removing the manual email-based process.
- No more Excel forms—information is entered directly in RCS sender management.
- Dynamic, country-specific form that shows only the questions required for the selected country.
- Automatic validation of submitted data (format and completeness) for faster processing.
- Requests can be updated and resubmitted if rejected.
- Overview of all launch requests submitted through UI and API.
- Faster sender onboarding for UI-based customers.
- Enables quick corrections and resubmission of launch requests.
For more information, refer to the RCS documentation.
AT&T (USA): Automated test device setup
Adding test devices for AT&T in the United States is now fully automated.
Previously, this process required manual work by CPaaS registration engineers due to AT&T's custom implementation.
Key features
- Test devices for AT&T can now be added automatically with no manual intervention from the client, account managers, or operational teams.
- No manual intervention from account managers or CPaaS registration.
- Faster setup of test devices.
- Fewer delays and dependencies on internal teams.
- Consistent experience across all networks.
Rejection reason in RCS sender launch webhook
The sender launch update webhook now includes rejection reasons.
Key features
- If a carrier rejects a sender, the webhook now includes a descriptive rejection reason.
- Clients understand exactly why a sender was rejected.
- Faster fixes and resubmissions.
- Less back-and-forth with support teams.
For more information, refer to the RCS sender launch documentation.
Connect a number from your WhatsApp Business app
A new onboarding option is now available that allows users to connect an existing WhatsApp Business app phone number to Infobip while continuing to use the app.
This enables co-existence between the WhatsApp Business app and the WhatsApp Cloud API on the same phone number, allowing businesses to combine manual messaging in the app with automation and integrations through Infobip.
What is supported
- Continue using the WhatsApp Business app on the same phone number.
- Use Infobip and the Cloud API for automated messaging, integrations, and programmatic use cases.
- Messages sent and received after onboarding are delivered to Infobip as events through webhooks.
Important limitations
- Chat syncing is not supported. During registration, users must select Don't share chats.
- Chat history from the WhatsApp Business app is not transferred during onboarding.
- Contact data from the WhatsApp Business app is not synchronized to Infobip in this onboarding flow.
- Some WhatsApp Business app features remain available only in the app and are not supported through the Cloud API.
- Selecting chat sharing during registration may cause the onboarding process to fail.
This onboarding option is currently available only for selected accounts and can be enabled by contacting Support.
For more details on this onboarding option, see Connect a number from your WhatsApp Business app