LivePerson is planning the process of deprecation for a number of products. See table below for more information. LivePerson's process of deprecation has 3 stages:
- Notice of deprecation: LivePerson inform customers of a feature that should no longer be used (but still works) and we will provide a date when it will stop working (normally 6 months post initial notice)
- Deprecation period: The period between the notice of deprecation and the end of life. In this period, will still support the feature but make no advancements and discourage use.
- End of Life: Feature no longer works.
Feature | Type | Date | Replaced by | Link for more info |
|---|
Predefined Content Custom Report | End of life | End of Q4 2024 | A similar report, the Predefined Content Messages Summary in Data Transporter | Coming soon |
Intent Analyzer (Analyze area only) | End of life | Q1 2025 | Report Center | Report Center Overview |
Bot Analytics | End of life | End of Q4 2024 | Report Center | Coming soon |
Legacy login: -Human login -Unified login (SSO) | End of life | Q3 2024 | Advanced login | Link to article |
WhatsApp On-Premise API | End of support | September 2024 | WhatsApp Cloud API | Meta announcement |
MCS Toolkit | End of life | TBC | Report Center | Report Center Overview |
Realtime Dashboard | End of life | TBC | Manager Workspace | Manager Workspace |
Completed Deprecations include:
Feature | Type | Date | Replaced by | Link |
|---|
Legacy Custom Reports: Agent Login & Agent Survey | End of life | Q1 2024 (still available for a few exceptions) | Reports can now be found in Data Transporter | Data Transporter |
Node Agent SDK | End of support | Q2 2024 | Messaging platform SDK | Link |
Old Versions of Mobile SDK | Only last 8 versions supported | April 1 2024 | Latest SDK versions | FAQs |
Realtime Dashboard | End of life | Q2 2024 | Manager Workspace | Manager Workspace |
LivePerson Insights | End of life | June 30 2024 | LivePerson Analytics Studio | Link |
MCS Toolkit | End of life | July 30 2024 | Report Center | Report Center Overview |
Push Notifications in the Android Mobile SDK | Google are ending support for Legacy APIs | June 2024 | Google use FCM v1 APIs for Push Notifications. Only Push Notifications using the new APIs will be delivered. | Link |
Google Business Messages
(Google Business Profile will not be impacted by the GBM deprecation) | End of support | July 30 2024 | Possible to link your social media profiles to your Google Business Profile to inform users of alternative channels. | Link |
Update:
- LivePerson will be continuing our partnership with X (formally Twitter). If you have any questions regarding X integrations, please reach out to your account team.
- LivePerson will be continuing with Email Connect Channel
FAQ
➡️ Why does LivePerson deprecate features and functionality?
At times, LivePerson undergoes a process of technological evolution and expansion to ensure continuous improvement. This evolution may necessitate the deprecation of existing features and functionality in favor of newer advancements. Maintaining multiple versions of the same functionality can impact LivePerson's ability to deliver the highest value to its customers.
➡️ How does LivePerson evaluate the impact of a feature deprecation?
LivePerson's evaluation process for feature deprecation involves a meticulous assessment by its product management leadership. The impact on customers is a focal point, with LivePerson considering factors such as the feature's current customer base, historical feedback, and the timeframe needed for customers to transition. Each feature candidate for deprecation undergoes a comprehensive evaluation to gauge its active user count, ensuring a seamless transition for LivePerson's customers without any negative impact when the deprecation takes effect.
➡️ What happens when LivePerson announces a deprecation?
Upon announcing a feature deprecation, LivePerson discontinues any further enhancements or advancements to the affected feature. LivePerson's provides timely communication about the change and offer assistance in case the deprecation has an impact on your operations. Typically LivePerson announces a deprecation 6 months in advance.
➡️ What communication does LivePerson provide for deprecation?
LivePerson has various communication channels to inform you about deprecations and potential replacement functionalities. These channels include the Knowledge Center Announcement section and email notifications targeted at affected account owners and administrators. LivePerson recognizes that transitioning to a new process can involve ongoing efforts. Customers who are supported by a Customer Support Manager might receive tailored communication from their account team.
➡️ Can I retain the legacy feature or functionality with LivePerson after the End of Life date?
No, once the End of Life date arrives, LivePerson discontinues the legacy feature from the platform. During the deprecation period; LivePerson discontinues any further enhancements or advancements to the affected feature but will still support the feature until the final end of life date.
➡️ What is the difference between End of Support and End of Life?
End of Support mean that LivePerson will no longer be providing ongoing assistance, updates, or maintenance for the product but brands can still use the Product.
End of Life refers to the point in time when a feature, functionality, or product is no longer supported or maintained by LivePerson. Users need to stop using the deprecated feature and migrate to alternative solutions.
➡️ How much notice does LivePerson provide for end of life of a product or feature?
LivePerson strives to offer ample advance notice for feature deprecations to ensure customers have sufficient time to prepare, as needed. Typically, LivePerson announces a deprecation around 6 months prior to the feature's planned deprecation date. However, the announcement period duration may vary based on factors such as business impact and customer considerations.