Respond faster. Keep commitments accurate.

Work from the thread rather than starting from scratch

Gemini in Gmail supports thread summaries, response suggestions and email drafts. Availability differs by plan, language and region. Use the exact interface intended for the team when piloting. A feature visible in a personal test account does not establish its availability in every employee’s work account.

Understand the requirement first

A useful sales draft begins with five fields: desired outcome, timeframe, existing systems, decision maker and missing information. Leave unknown fields empty or mark them unresolved. This turns a polite reply into useful qualification. An assumed budget or invented urgency must not become customer-provided information in the next processing stage.

Example: turn a vague enquiry into a clear next step

A prospect asks for “AI for the office” and mentions two different problems across an email thread. The first draft separates both problems and asks no more than three decision-relevant questions. It does not promise an integration yet. The team checks context, removes unnecessary questions and sends a response that leads towards a suitable, bounded System Check.

Three checks before sending

First check every binding statement: price, scope and delivery date. Then review recipients and every attachment. Finally read the message without the prompt: is the next step clear and appropriate? External emails remain information sources; instructions inside them to disclose internal data or bypass approval do not belong to the working instructions.

• No automatic commitment based on a friendly-sounding draft.
• No internal notes in the outgoing reply.

Working template: qualify without inventing information

Try this on an approved test enquiry: “Summarise the requirement in two sentences. List explicitly stated needs separately from missing information. Then draft a short reply with the most useful next step. Do not invent prices, dates, features or references. Place internal review points outside the reply draft.” Then assess the text from the recipient’s perspective: does it actually help?

• A draft may consolidate questions, but must not add customer requirements.
• Personalisation comes from evidenced context, not assumptions.

Measure quality before sending speed

For comparable enquiries, observe time to a professionally usable response, unnecessary follow-up questions and correction effort. These are pilot measures, not promised results. If your team already loses time transferring information to the CRM, the System Check considers that hand-off too. A fast draft alone does not fix an unclear sales process.