Table of contents
One morning staff cannot sign in. The Admin console says suspended. Mail stops, Drive files are unreachable, and Google’s reply is a template. This is one of the most asked questions in the Workspace community, and one of the least usefully answered.
First: what exactly is suspended?
The word covers three completely different situations, and the fix differs for each:
- A single user account. Suspended by your own admin or an automated policy. Solvable in minutes in the Admin console: Users, select the account, Reactivate.
- The whole organisation. Google suspended the subscription. The most common cause by far is a failed payment: an expired card, a bounced invoice. Fix the payment method in Billing and service returns, usually within the hour.
- An account managed by a reseller. The subscription is controlled by a third party who has not paid Google or has stopped responding. You cannot fix this in your console, because it is not your billing.
Mixing these up is why people write to the wrong support channel for weeks.
If it is a payment problem
- Admin console, Billing, check the payment method and any overdue invoice.
- Pay by card even if you normally pay by invoice. Restore service first, argue accounting later.
- Data is not deleted during suspension. There is a grace window, but do not test its length.
If it is a policy or abuse suspension
Spam sent from a compromised mailbox is the classic trigger. You appeal from the Admin console, and the appeal that works is specific: what happened, what you fixed, which passwords were reset, which filters or forwards were removed. Vague appeals get template rejections.
If you are stuck at a reseller
A subscription can be transferred away from an unresponsive reseller to direct billing or to another partner. It requires your domain ownership and a transfer token, and it is exactly the kind of thing we do for companies as a Google Cloud Partner: we take over the conversation with Google and get service back without experiments in production.
Related: if the person who had admin rights is gone, read how to reach real support first, and lock down a second super admin once you are back in.
