#pulley871_best-practices
wicked sonnetBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- pulley871_best-practices, 2 days ago, 8 messages
urban hearthBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1243220799628902451
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
jaunty wagon
Might be best to consider limiting how often users can upgrade/change plan
willow tartan
Yea that is a consideration the company has. They wanted me to see if there were any other standards that you guys may recommend for this.
My initial thought was to not use tiered pricing since it was only for 3 items
jaunty wagon
yeah up to you on how you want to model price
But if you want to avoid customers from switching plans so frequently, might make sense to limit 1 plan change per billing cycle
willow tartan
is this something that stripe has plugged in? or something we need to build out?
willow tartan
own site
willow tartan
roger.
Thanks for the insight!