Skip to content

Subscriptions

Subscriptions is for customers who are on a plan rather than buying once. It holds the plans, the customers attached to them, and the payment decisions somebody has to make when one does not go through.

Try it in the democustomer_subscription · 3 tasks

Before you start

  • The plans themselves, and what each costs.
  • Somebody named who decides payment reviews — an unowned review queue stops being read within a month.

What Subscriptions does

Customers on a plan rather than a one-off sale.

01

Set up plans and what they cost

A plan is the product; a subscription is a customer on it. Defining plans first means a price change is one edit rather than a bulk update across every customer.

02

View and manage a customer subscription

The customer record shows what they are on and what has happened to it. This is the record support is answering from, so changes made outside it are invisible to the person taking the call.

03

Decide a payment review

Payments that need a judgement are routed to a person rather than retried silently. Someone is accountable for the decision, and the decision is kept.

What it claims to do

The capability list this guide is written against, unabridged. Nothing above adds to it.

Subscriptions on the Sales page
  • Subscription plans and what they cost
  • Customer subscriptions, viewed and managed
  • Payment reviews decided by someone accountable

Where it connects

The modules Subscriptions hands work to, or takes it from. Most problems that look like one module are a handover between two.