Reviewing subscription requests

Plan requirement

Subscription Any plan
Access Admin, Owner

For account owners: what arrives, what to ask before approving, and why a stale queue is worse than no queue.

Review them

  1. In Admin Center, click Account and select Billing > Subscription.
  2. Open the Requests tab and read the request summary, which lists the changes asked for and what the additions cost.
  3. Click Update subscription to approve it, or Reject to turn it down.
  4. Tell the requester either way. Nothing in the flow does it for you.

The account owner and any billing admin can do this. If there is no Requests tab, your account does not use this route; contact pluscloud support for a subscription change.

Three questions before approving

  1. Is there an unused seat? Check last sign-in dates first; the answer is often yes.
  2. Does this person need a full agent seat or a lighter role?
  3. Is this permanent or for a project? Seats are easy to add and hard to remove before renewal.

Answer quickly, even when the answer is no

A request sitting for two weeks blocks somebody's work, and they will solve it another way: sharing a login, working from a personal account, or doing the job outside Zendesk.

Each of those is worse than the seat would have been.

Say why when you decline

Approving or rejecting does not tell the requester anything, so the reason only reaches them if you send it. "We have two unused seats, deactivate one of those" is actionable. Silence gets read as a no with no route forward, and it recurs next month.

Watch the pattern, not the request

Repeated requests from one team usually mean the team grew or the process changed. Raise that with the team rather than approving another individual request.

Review the queue on a rhythm

Weekly is enough. Requests do not notify loudly, and an owner who checks only at renewal will find requests from three months ago.

See also

Was this article helpful?

0

Still stuck?

Our support team will take a look with you.

Comments

0 comments

Article is closed for comments.