Skip to content

Docs: Subscription and billing management #9520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
agjohnson opened this issue Aug 18, 2022 · 4 comments · Fixed by #9963
Closed

Docs: Subscription and billing management #9520

agjohnson opened this issue Aug 18, 2022 · 4 comments · Fixed by #9963
Assignees
Labels
Accepted Accepted issue on our roadmap Needed: design decision A core team decision is required

Comments

@agjohnson
Copy link
Contributor

I don't believe we have any appreciable amount of documentation covering our billing process, subscriptions, and payment questions. This might also be an addition for our website instead, but either way, some of the information we aren't communicating to users might look something like:

  • Payment options
    • Monthly vs annual payments
    • We support credit card recurring subscriptions for monthly/annual subscriptions
    • We should define our support for invoicing, which so far is: you really should be using recurring credit card payments. We can support invoicing, but I'm not sure we really want to raise it as a possibility even, as that would almost certainly lend to more invoice payable subscriptions.
  • How to manage a subscription
    • You need to be an organization owner
    • How to add a CC to invoices
    • How to add your companies information and VAT/etc
    • We don't need to explain too much about the UI, it's pretty straight forward. There are some hidden pieces though
@agjohnson agjohnson added Needed: design decision A core team decision is required Accepted Accepted issue on our roadmap labels Aug 18, 2022
@agjohnson agjohnson moved this to Planned in 📍Roadmap Aug 18, 2022
@agjohnson
Copy link
Contributor Author

Re invoice by email, what I tend to do is:

If a user wants a PO first, I create a Stripe quote. Not sure if we want to document this though?

If approved, I give them the link to their existing subscription's invoice, payable by CC recurring. If they insist on an invoice, I'll edit/regenerate the invoice for email invoicing.

If they send me set up instructions for their vendor system, I tell the that we don't support this for our self-service plans. We'll only do for high tier plans, even then it's a pain.

@ericholscher
Copy link
Member

@agjohnson What is the quote doing in this case? Why not just link them to the invoice up front?

@agjohnson
Copy link
Contributor Author

It's a nicer workflow, and avoids the invoice going to unpaid/noncollectable, and doesn't count towards our revenue. This is specific to users asking for a quote or PO for approval.

@ericholscher ericholscher self-assigned this Nov 8, 2022
@benjaoming benjaoming changed the title Add docs on subscription and billing management Docs: Subscription and billing management Nov 23, 2022
@benjaoming
Copy link
Contributor

I think this is best placed as part of #9748 or #9749, i.e. once the new structure has landed and we are iterating over content refinements and additions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Needed: design decision A core team decision is required
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants