Subscriptions and cycles
5 articles
- Creating a New Subscription in "Subscriptions"When a new customer agrees to a subscription, its details end up in scattered messages and sheets: when it starts, how many users, at what discount, and whether it renews when the term ends. So the first invoice is late, or goes out at a price other than the one agreed, or the renewal date is forgotten.
- Setting Up Subscription and Line Fields in "Subscriptions"When a subscription is linked to another system, such as a sign-up or deployment system, every subscription must carry its reference, and no two subscriptions can share it. And if any employee can change a line's price or discount, a subscription goes out at a price nobody approved, and it only shows on the invoice.
- Viewing Subscriptions, Cycles, and Their Statuses in "Subscriptions"When a customer asks about their subscription, or a manager asks what renews this month, it has to be known at once: is the subscription active, when does it renew, what is its monthly value, and what has changed on it since it began. If the trail of changes is lost, nobody knows what the customer was paying in an earlier period.
- Approving Cycles with Workflows in "Subscriptions"When a customer renews, someone has to review the deal before the invoice: did they stay on the same plan, did the number of users change, and is the discount they got approved. If any employee can invoice the cycle or change its figures after it's been reviewed, an invoice goes out that nobody reviewed.
- Invoicing Cycles in "Subscriptions"An annual subscription at 49 a month has the customer pay for 12 months at once. But an invoice only has a quantity and a price, with no room for the term, so if the monthly price is written on it the customer can't tell why they pay more than that. And a cycle can pass its end date without being invoiced, so it doesn't renew, or a draft cycle is forgotten while the customer is actually using the service.