Google Workspace support in London

In volume terms, the work is account lifecycle and permissions: new starters, leavers, shared drive access, group membership, delegated mailboxes, calendar resources and mobile device enrolment. Underneath that sits a steadier flow of mail delivery investigations, spam and phishing triage, and the occasional genuine incident.

The strategic work sits alongside it: quarterly security posture review, licence position review before renewal, and a standing recommendation list that we work through with your internal owner. Support agreements that only handle tickets leave the tenant slowly degrading between projects.

Workspace itself does not care where support sits. Your staff do. A mail delivery problem at 09:15 needs somebody who is awake, who understands that your finance team is mid-month-end, and who can call the person concerned rather than exchanging emails across a nine-hour offset.

The other reason is escalation. Google's own support paths are effective when driven correctly, and driving them correctly means having someone who can hold a case open during the same working day rather than losing a full cycle to time zones.

Per-seat monthly pricing has one important property: nobody hesitates to raise a ticket because it costs money. Time-and-materials support produces the opposite behaviour, where small problems go unreported until they are large problems, and the security ones are exactly the ones people sit on.

Standard support costs £10 per user per month, subject to the £450 monthly minimum. The initial term is three months; after that, it runs monthly with thirty days' notice. There is no annual lock-in, because a support relationship that needs a contract to survive is not one worth keeping.

The first two weeks are discovery, not tickets. We document the tenant as it is, produce a findings list, agree the runbook for routine tasks, and establish who inside your organisation can authorise access changes. That authorisation matrix prevents the most common failure of outsourced support, which is an engineer making a change because somebody asked confidently.

From week three the desk runs normally, with a review at thirty days to correct anything about response routing or authorisation that is not working in practice.

Ask whether the response clock runs in GMT, local UK time or another specified zone, and how public holidays and out-of-hours requests are handled. A portal acknowledgement is not an engineer response; severity and escalation need clear definitions.

Provide your recurring access, authentication and mail-flow problems, along with user count and internal approvers. If a short consultancy engagement addresses the root cause, compare that with a retainer. Confirm the published £450 monthly floor and any on-site work separately.