Tier Based Subscription Billing Automation Overview
After reviewing your feedback, Spiffy is proud to introduce a new layer of billing automation for subscriptions!
Previously, you have had the option to set up global billing automation, but now, you can set up more specific automation for tiers on your subscription products.
This is useful for businesses that have customers on multiple subscriptions. You will now be able to set up specific integration actions for billing automations on your individual subscription tiers and are not limited to global automation.
In this overview, we will go over how to start setting up tier based billing automation, as well as give insight into when certain events would run when configured.
- If you are new to creating subscription products, tiers and plans in Spiffy, be sure to review our article on managing subscriptions in Spiffy. Click Here
- If you have older subscription plans that were created prior to the introduction of Subscription Tiers in Spiffy, you can move your existing plans into a tier. For more info Click Here
- If you have set up global billing automation for subscriptions, you may want to review your existing configuration before setting up tier based subscription billing automation. You can review your global billing automation here: https://app.spiffy.co/settings/automation
From the Spiffy Dashboard, go to Products and select the subscription plan that you want to set up tier based billing automation for.
From the subscription dashboard, scroll down to the Tiers & Plans section and click the settings gear icon for the tier you want to configure.
Select Automations from the settings gear to open the automation view for your tier.
From the automation view, select Add Action
Select an event to configure an integration action for.
Next, select your integrated system from the list (Infusionsoft/Keap, Active Campaign, Hubspot, Zapier etc)
Select an available action for your integrated systems (ex: Apply Tags, Remove Tags, etc).
Configure your integration action and Finish.
You will now be able to add additional actions as needed by following the steps above.
Once you have configured your actions, they will appear in the automation view for your subscription tier.
You will be able to click on a specific action to modify or remove it.
Events and When They Will Run
Payment Failed: This event will run when a subscription payment failed. This is often used to apply a tag that can notify your customer and/or your team that a subscription payment failed.
Subscription Started: This event will run when a customer starts a subscription plan in the configured tier. This can occur when your customer purchases via a checkout, a manual order for the subscription is placed or you change a customer's subscription plan to a plan in the configured tier via the customer's record in Spiffy.
Subscription Unpaid: This event will trigger when a customer's scheduled subscription payment fails and all auto-reattempts have failed.
Subscription Cancelling: This event will trigger if you set a customer's subscription to cancel at the end of their current billing cycle, or if the customer selects to cancel via the Spiffy Customer Portal.
Subscription Resumed: This event will trigger if a customer's subscription was in a cancelling status, and is resumed via the customer's record in Spiffy.
Subscription Cancelled: This event will trigger when the customer's subscription is cancelled (at the end of their current billing cycle, or if you choose to cancel the active subscription immediately via the customer's record in Spiffy).
Subscription Swapped: If you are using multiple tiers, this event would fire if you change the customer's subscription plan to a plan in a different tier via the customer's record in Spiffy. You would set this automation event up on the plan they are switching FROM. Commonly used to add/remove tags in connected systems.
Upcoming Subscription End of Trial: This event will trigger 7 days prior to the end of a subscription that is on 'Trial Days' If you offer a trial that is 7 days or less, this would not be applicable.
Subscription Payment: This event will trigger when a customer's scheduled subscription payment is successful.
Upcoming Subscription Payment: This event will trigger 3 days prior to a customer's scheduled subscription payment.
Got a question? Send us an email over at email@example.com