Private user: email helper

Email automation

A tactical email assistant for teams that cannot afford to lose context, time or control

Results

• Approximately 20 working hours recovered each day across a 15-person team

• Around 4,400 hours of annual capacity released

• Equivalent to approximately 2.4 full-time roles

• Estimated annual productivity value of £90,000-£100,000

• No new mail client, migration or central data platform

The challenge

A team of 15 operators, consultants and account leads was managing dozens of active client conversations every day.

Each substantive reply required the sender to:

• reread the complete thread

• reconstruct the commercial and operational context

• decide the appropriate tone and tactic

• draft a response from scratch

• check that no unauthorised commitment had been made

Slow replies created commercial risk. Rushed replies created a different risk: vague wording, inconsistent positions and promises the business had not approved.

Generic AI writing tools improved drafting speed but introduced additional concerns around data handling, context control and dependence on external platforms.

What was built

NexOps Operator is a browser-based email assistant that works alongside Gmail and Outlook 365.

It reads the open conversation, identifies the sender’s position and generates a complete recommended response. The user reviews the draft, makes any required changes and approves it.

The workflow is intentionally simple:

1. Open the email

2. Run Operator

3. Review the recommended response

4. Approve or edit

There are no complex menus, mandatory modes or separate workspaces.

Tactical response generation

Operator does more than rewrite text.

It evaluates the conversation and selects an appropriate response strategy based on the email, previous context and an optional one-line instruction from the user.

Alongside the draft, it provides a brief assessment of:

• what the sender is trying to achieve

• which pressure or negotiation tactic is being used

• how the recommended response addresses it

Alternative approaches remain available but stay hidden unless the user needs them.

Draft quality control

Every response passes through a separate review stage before it is presented to the user.

The system checks whether the draft:

• follows the selected tactic

• remains consistent with the company profile

• introduces an unauthorised promise

• contains unnecessary filler or unsupported claims

This creates a quality gate between automated drafting and the final human decision.

Commitment tracking

Operator records material commitments made within approved drafts.

Promises, deadlines and agreed actions are associated with the relevant contact, reducing the risk that obligations disappear inside long email threads or are forgotten during busy periods.

The user remains responsible for approving every response. The system provides visibility and consistency rather than autonomous sending.

Integration

Operator runs in a browser side panel and works directly with:

• Gmail on the web

• Outlook 365 on the web

• Chrome

• Microsoft Edge

• Brave

It detects the active mailbox and adapts to the existing interface.

There is no new inbox to adopt, no email migration and no separate system for staff to maintain. Deployment requires minimal configuration and allows the team to continue working in its existing environment.

Measured time saving

The working model assumed that a substantive email required approximately six minutes to read, contextualise and draft manually.

With Operator, analysis, review and approval took approximately 90 seconds.

Using a conservative saving of four minutes per reply, across 20 replies per person per day and 15 users, the system released approximately 20 working hours each day.

That equates to around 4,400 hours annually, or approximately 2.4 full-time roles based on 1,800 productive hours per person.

At an estimated loaded employment cost of £40,000 per role, the recovered capacity represents approximately £90,000-£100,000 in annual productivity value.

This calculation excludes the commercial benefit of faster replies, improved consistency and fewer unauthorised commitments.

Data and security model

Operator does not use a central NexOps platform to collect or store client email.

The API key is stored locally on the user’s machine. NexOps does not receive:

• mailbox content

• usage telemetry

• draft history

• client correspondence

• company profile data

The company controls the information used to ground each response.

Commercial API deployment

In the standard deployment, draft generation uses a commercial model API.

This means the relevant email content is transmitted to the model provider for inference. It does not remain entirely within the client’s network.

This deployment is suitable where the business permits controlled use of an external AI provider and accepts its contractual data-processing terms.

Fully private deployment

For organisations that require zero external data transmission, the same workflow can run on NexOps Private AI.

The model operates:

• inside the client’s network

• on client-controlled hardware

• without transmitting email content externally

• at a fixed infrastructure cost rather than a per-message charge

The user experience remains the same, but all inference and company data remain within the organisation’s own environment.

Why it worked

The system was designed around a single high-frequency task: producing a commercially sound reply without repeatedly rebuilding context.

It did not replace the inbox or remove human approval. It reduced the repetitive work surrounding each decision while adding controls around accuracy, commitments and company position.

The result was faster correspondence, more consistent responses and substantially more time available for client and revenue-generating work.