🐛 Describe the Bug
When a Marketplace app adds new Conversation Providers in a subsequent app version, existing installations do not receive those providers after updating the app from the Marketplace.
We recently released a new version of our Marketplace app that introduces additional Conversation Providers (e.g., separate WhatsApp and iMessage providers) instead of replacing SMS.
However, customers who already have the app installed do not receive the newly added providers, even after updating the app through the Marketplace.
The only workaround we have found is:
- Uninstall the Marketplace app.
- Reinstall the Marketplace app.
Unfortunately, uninstalling the app removes the provider configuration across all sub-accounts and resets locations back to the default SMS provider.
For agencies with dozens or hundreds of sub-accounts, this creates a major service interruption and makes Marketplace upgrades effectively impossible.
This prevents Marketplace developers from safely evolving their apps and introducing new providers to existing customers.
📍 API Endpoint
Marketplace App Installation / Update Flow
✅ Expected Behavior
When an existing customer updates a Marketplace app, any newly added Conversation Providers should be installed and registered automatically, similar to how newly added features or permissions become available after an app update.
The update process should preserve existing provider assignments and location configurations.
Expected outcome:
- Existing installations receive newly added providers.
- No uninstall/reinstall required.
- Existing location-level provider settings remain unchanged.
- Marketplace developers can safely release new providers to existing customers.
💻 Screenshots or Code Samples
Reproduction Steps
- Install a Marketplace app that provides a Conversation Provider.
- Configure locations to use that provider by replaces SMS in location settings.
- Release a new Marketplace app version containing an additional Conversation Provider.
- Open Marketplace and update the app.
- Observe that the new provider is not installed or available.
- Uninstall and reinstall the app.
- Observe that the provider appears.
- Observe that existing location configurations are reset.
Product Area
ad-publishing
📋 Use Case
Our Marketplace app currently powers WhatsApp messaging for over 1200+ agencies.
Historically, we replaced the SMS provider with our WhatsApp provider because that was the only viable implementation path.
We are now trying to evolve our integration to support multiple messaging channels simultaneously (e.g., SMS, WhatsApp, iMessage, and future providers) so customers can continue using LC Phone/SMS while also using additional messaging channels.
This approach benefits both customers and HighLevel by increasing adoption of Conversation Providers and reducing the need to replace existing communication channels.
However, because newly added providers are not installed during Marketplace app updates, we are unable to roll out these improvements to our existing customer base.
🚨 Why Should This Be Prioritized?
This issue is currently blocking production rollout of a major Marketplace upgrade.
Impact:
Over 1,000 agencies are affected.
Many agencies manage 100+ sub-accounts.
Uninstalling and reinstalling the app resets provider configuration across locations.
Large agencies would need to manually reconfigure hundreds of locations.
This creates a significant risk of messaging disruption and downtime.
Marketplace developers cannot safely introduce new Conversation Providers after initial installation.
The issue discourages adoption of HighLevel's Conversation Provider ecosystem because upgrades become operationally risky.
From our perspective, this is not merely a feature request, it is a platform limitation that prevents Marketplace apps from evolving after deployment.
Without a migration/update path for Conversation Providers, Marketplace developers are effectively forced to decide all providers at initial install time, which is unrealistic for long-term product development.
🧠 Additional Context
No response
🐛 Describe the Bug
When a Marketplace app adds new Conversation Providers in a subsequent app version, existing installations do not receive those providers after updating the app from the Marketplace.
We recently released a new version of our Marketplace app that introduces additional Conversation Providers (e.g., separate WhatsApp and iMessage providers) instead of replacing SMS.
However, customers who already have the app installed do not receive the newly added providers, even after updating the app through the Marketplace.
The only workaround we have found is:
Unfortunately, uninstalling the app removes the provider configuration across all sub-accounts and resets locations back to the default SMS provider.
For agencies with dozens or hundreds of sub-accounts, this creates a major service interruption and makes Marketplace upgrades effectively impossible.
This prevents Marketplace developers from safely evolving their apps and introducing new providers to existing customers.
📍 API Endpoint
Marketplace App Installation / Update Flow
✅ Expected Behavior
When an existing customer updates a Marketplace app, any newly added Conversation Providers should be installed and registered automatically, similar to how newly added features or permissions become available after an app update.
The update process should preserve existing provider assignments and location configurations.
Expected outcome:
💻 Screenshots or Code Samples
Reproduction Steps
Product Area
ad-publishing
📋 Use Case
Our Marketplace app currently powers WhatsApp messaging for over 1200+ agencies.
Historically, we replaced the SMS provider with our WhatsApp provider because that was the only viable implementation path.
We are now trying to evolve our integration to support multiple messaging channels simultaneously (e.g., SMS, WhatsApp, iMessage, and future providers) so customers can continue using LC Phone/SMS while also using additional messaging channels.
This approach benefits both customers and HighLevel by increasing adoption of Conversation Providers and reducing the need to replace existing communication channels.
However, because newly added providers are not installed during Marketplace app updates, we are unable to roll out these improvements to our existing customer base.
🚨 Why Should This Be Prioritized?
This issue is currently blocking production rollout of a major Marketplace upgrade.
Impact:
Over 1,000 agencies are affected.
Many agencies manage 100+ sub-accounts.
Uninstalling and reinstalling the app resets provider configuration across locations.
Large agencies would need to manually reconfigure hundreds of locations.
This creates a significant risk of messaging disruption and downtime.
Marketplace developers cannot safely introduce new Conversation Providers after initial installation.
The issue discourages adoption of HighLevel's Conversation Provider ecosystem because upgrades become operationally risky.
From our perspective, this is not merely a feature request, it is a platform limitation that prevents Marketplace apps from evolving after deployment.
Without a migration/update path for Conversation Providers, Marketplace developers are effectively forced to decide all providers at initial install time, which is unrealistic for long-term product development.
🧠 Additional Context
No response