➡️ Exact delivery dates may vary, so some features may not be immediately available on the publication date. For your specific access dates, please contact your LivePerson account team.
🚨The timing and scope of all changes remain at the sole discretion of LivePerson and are subject to change.
Authorize agent access using IPv6
To support modern IPv6-only network environments, LivePerson has expanded IP Restriction configuration within the Account Access Control page in the Management Console.
Administrators can now authorize agent access using IPv6 address ranges and CIDR blocks, in addition to the existing IPv4 controls — all managed from the same interface.
Key enhancements
IP Restriction section
The IP Restriction section is now organized into two clearly labeled subsections:
- IPv4 — existing IP range and CIDR configuration
- IPv6 — new IP range and CIDR configuration
IPv6 configuration
- Dedicated input fields for IPv6 ranges and CIDR blocks
- Real-time validation ensures entries follow correct IPv6 notation
- Configuration is saved directly to the account's access control settings
Protocol safety warning
To prevent accidental lockouts, saving a configuration where either the IPv4 or IPv6 access list is left empty (while the other is populated) triggers a warning:
Warning: You have authorized IPv6 ranges, but your IPv4 access list is currently empty (or vice versa). Because our security policy requires strict protocol validation, saving this configuration will block all login attempts via an IPv4 connection. Are you sure you wish to continue?
Administrators must explicitly choose to either add a range for the missing protocol or confirm and save the configuration as is.
Android Mobile Messaging SDK now supports Android 17
The Android Mobile Messaging SDK version 5.28.0 release includes support for Android 17, a new customization capability, and bug fixes.
Environment requirements
The Android Mobile Messaging SDK version 5.28.0 uses:
- Minimum API version 21
- Compile API version 37
- Target API version 37
- Maps SDK "com.google.android.gms:play-services-maps:18.1.0"
- Structured Content Library “com.liveperson.android:lp_structured_content:2.8.0"
- Date Picker Library “com.liveperson.android:lp-date-picker:2.3.0"
- Appointment List Library "com.liveperson.android:lp-appointment-scheduler:2.1.0"
New features
- Added support for Android 17.
- Added a character counter for text input fields in the conversation screen. As users type, the counter updates to show the number of remaining characters, improving accessibility compliance. New branding attributes allow customization of the counter's default style.
Bugs fixed
- Fixed a crash caused by a null pointer exception in certain conversation flows.
- Resolved a file naming conflict that could occur when integrating with certain third-party SDKs.
- Fixed an issue where the time-to-respond popup incorrectly appeared when automatic messages were enabled.
- Fixed an issue where encryption could fail for the first message sent while in offline mode.
Generative AI - An update on our initiative to migrate to Google Gemini
This is another update on LivePerson's initiative to migrate to Google Gemini models for our Conversational Cloud products using Generative AI.
Recall that your primary source of information is this article in our Community Center.
Here's what's new:
North America brands: Reminder of upcoming cutover of prompts for Automated Conversation Summaries
As first announced in our June 24, 2026 release notes, this is a reminder about the upcoming cutover to Gemini for custom prompts for Automated Conversation Summaries. This cutover will be performed on July 26, 2026.
See our info on the general migration process, and learn more about cutover of custom prompts.
➡️ Call to action: We encourage you to perform a review of all of your custom prompts and manually migrate them to Gemini before this cutover.
North America brands: Upcoming cutover of prompts for KnowledgeAI
Please be advised of the upcoming cutover to Gemini of custom prompts for KnowledgeAI on August 2, 2026. This impacts the following products:
See our info on the general migration process, and learn more about cutover of custom prompts.
➡️ Call to action: We encourage you to perform a review of all of your custom prompts and manually migrate them to Gemini before this cutover.
EMEA brands: Upcoming cutovers for aiStudio flows
If you're using aiStudio in the EMEA region, be advised that cutover of all custom flows will happen as follows:
1 - July 29, 2026 8 p.m. British Standard Time: A 48-hour "freeze" on brand activity starts. LivePerson asks that all brands refrain from making changes to existing flows and from creating new ones. LivePerson retrieves necessary data on existing flows.
2 - July 30: LivePerson migrates all existing flows to Gemini. LivePerson prepends "[Gemini]" to the name of the Gemini flows that are active once the cutover is completed.
➡️ Flows that already point to a Gemini model are unaffected.
3 - July 31, 2026 8 p.m. British Standard Time: The 48-hour freeze period ends.
➡️ Call to action: Starting July 29, 2026, refrain from:
- Making changes to existing flows
- Adding new flows
The freeze period will last for 48 hours, so the cutover can be performed.
Once the cutover is completed:
- Verify that the active Gemini flows perform as you expect.
- For the sake of keeping things tidy and organized, we also recommend that you delete old prompts and flows that are no longer in use.
FAQs
How can I know if I am impacted by the cutover?
If you created a new aiStudio flow after February 4, 2026, you are likely excluded from the cutover. (This was the date on which we retrieved data on existing flows.) In this case, contact your LivePerson representative to request a Gemini-optimized flow. Once you receive it, you can migrate the flow to Gemini yourself. Contact your LivePerson representative if you need assistance.
If you are unsure about whether you are impacted by the cutover, contact your LivePerson representative.
What is the impact if I make additions or edits to prompts and flows during the freeze period?
If you make changes during the freeze period, those changes may be overwritten as a part of the cutover. Please refrain from making changes during this time.