Skip to content

Guides

Support for a product with per-seat pricing

Per-seat pricing is simple until the first change mid-month. Most billing tickets are about adding or removing people and what the next invoice will show.

Last reviewed

Explain what counts as a seat

Define a seat in one sentence and show where customers can see who holds one. Disputes start when people disagree on who is counted.

Make seat changes self-serve

Let admins add and remove seats without writing in. Every change they make themselves is a ticket you do not have to answer.

Show proration before they confirm

Display the charge or credit for a mid-cycle change on the confirmation screen. Surprises on the invoice are what cause complaints.

Prepare replies for true-ups

If you bill extra for seats used above the plan, write a clear reply that lists the users and the dates, with a link to adjust before the next cycle.

Handle removed users cleanly

Explain when a removed seat stops costing money and what happens to that person's data. Be explicit about the next invoice.

Watch for seat-count pain points

Tag billing tickets by cause. Many tickets about the same step mean the page or the invoice needs a fix, not another reply.

Questions

Should we refund unused seats?

Follow a written rule. Many teams credit the unused time on removal and refuse refunds for time already used.

How do we reduce seat billing tickets?

Show live seat counts, preview charges before changes and send a notice before each renewal.

What if a customer disputes the seat count?

Share the list of users with the dates they were added and agree on any corrections together.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.