Automations

Bug fix for Account Cancellation / Subscription Status Trigger
For this feature https://ideas.gohighlevel.com/changelog/subscription-and-refund-trigger-live-in-automations there is a missing subscription status and a mis-labeled status. What is called "cancelled" is actually the "expired" date. And there seems to be no actual cancel date. Let me explain...if I'm a client on a monthly SaaS subscription and my monthly renewal date is the 15th, and say I "cancel" my subscription on the 1st, there is no way for that event to be a trigger for any workflow (we want to know so we can immediately go to work to try to save that account). If I go into the Billing Section, I will see a note "scheduled for cancellation". I can click on "modify your subscription" and then will see the screen below with my options and the actual date when my account "will be cancelled on ______________". In reality, the cancellation has already happened. What GHL is calling cancellation is the "expiration". Since the account is actually in an "active" status between the cancellation date and the expiration date (in my example, 15 days), no notifications go out and this is precious lost time and opportunity to try to re-engage the client and change his mind. If, "expired" means something else (for example does it mean the end of a trial period?), then perhaps that need clarification to agencies. If you want to keep "cancelled" as the status/label for the actual date the account is frozen (client locked out until they pay again), then we DO need an additional status to represent that actual date the client requests the cancellation...maybe "Cancel Order" etc. We know there is a data point for the date the account will be frozen/expired. We also need access to this date via a dynamic field so we can time emails, etc. off of that critical end date.
2
Load More