You can use DeepSeek to turn rough notes into an English email, improve an existing draft, or prepare a reply. Give it the recipient, your purpose, the facts to include, and the tone you want. Ask for a subject line and a message with a clear next step, then check the wording against what you actually intend to say.
For an everyday work email, start with plain, polite English. A message does not need elaborate greetings or impressive vocabulary to sound professional. It needs to help the recipient understand the situation and know whether you want an answer, a decision, or an action.
On this page: Write your first email · Reusable prompt · Choose the tone · Before-and-after examples · Reply to a message · Prompts for specific situations · Review before sending · FAQ
How to write an email with DeepSeek
For this workflow, use the conversational service linked from DeepSeek’s official website. You can work in its web chat or official app; you do not need to build an API integration to draft a message. This guide covers writing and reviewing the text, with the final email sent from your usual email application.
- Decide what the email should achieve. “Ask a client to choose between two meeting times” gives you a clearer starting point than “write a professional email.” Identify the recipient and your relationship, too: a new customer and a colleague you speak to daily may need different wording.
- Prepare the facts or paste a draft. Include the relevant context, what you want to ask, and any dates or commitments you have actually decided. Rough notes are enough. Replace names and sensitive details with placeholders, and leave out material your workplace does not allow you to share.
- Specify the output. Ask for English, the level of formality, and a subject line plus body. Give a length preference if the situation calls for one, such as a short follow-up. A detailed explanation may need more space than a meeting request.
- Read the draft, then request a specific revision. Check the meaning first. If it is correct but too stiff, ask for a warmer version. If it is long, ask it to keep the request and essential context while removing repetition.
- Finish in your email application. Copy only the subject and body, replace placeholders, check the recipient and attachments, and read the message once more before sending.
The expected result is a usable draft that reflects your notes. If it adds a promise or misses the question you wanted answered, correct that before polishing the style. Asking for another rewrite without explaining the problem can simply produce a different version of the same mistake.
A reusable DeepSeek email prompt
Use this when you have an email to improve or notes to turn into a message. Replace the bracketed fields and remove any field that does not apply. “Professional” is a useful starting point, but details such as “polite and direct, without a long opening” give the request more direction.
Help me write this email in natural English. Recipient and relationship: [who I am writing to] Purpose: [what this email needs to achieve] Facts to include: [confirmed details] Points that are still uncertain: [anything not decided] Action I want the reader to take: [the request, if any] Commitments I can make: [only what I have agreed to do] Tone: [for example, polite and direct] Length preference: [short, detailed, or a word limit if needed] Draft or notes: [paste text without private details] Return a subject line and the email body. Keep my meaning and level of certainty. Do not invent reasons, progress, dates, availability, approvals, results, or attachments. If an essential detail is missing, ask me separately rather than filling it in. Keep questions and editing notes outside the email.
To learn from the revision, add: “After the email, explain the three most useful changes to grammar or wording.” For a message you only need to send, ask for the subject and body alone once you have resolved the questions. That keeps the finished text easy to copy.
A prompt can set boundaries, but it does not verify the output. DeepSeek’s Terms of Use describe a service that generates text from your input. Treat the response as drafting help, and compare factual details with your own notes or records.
Choose a tone that fits the recipient
For a routine work message, “friendly and professional” is a reasonable default. Use more formal wording for a first contact or a situation where the relationship calls for it. Use a firmer tone when you need to make a boundary or outstanding request clear. Firm does not have to mean accusatory.
| Situation | Direction to give DeepSeek | What to look for in the draft |
|---|---|---|
| A new client or unfamiliar recipient | Use courteous, moderately formal English. State why I am writing near the beginning. | A clear introduction and request, without excessive praise or ceremonial wording. |
| A colleague you know well | Make it friendly, brief, and natural. Keep the context we need to act on. | A conversational greeting and direct request, without unnecessary background. |
| An unresolved request or a boundary | Be calm and firm. Explain what is outstanding and the next step I have specified. | A clear position, with no invented deadline, threat, or accusation. |
Keep the greeting, body, and sign-off consistent. “Dear [Name]” suits a more formal opening; “Hi [Name]” is more familiar. Follow the recipient’s preferences and your workplace’s conventions rather than assuming one greeting is correct everywhere. The British Council’s email guide explains how the relationship affects openings and closings.
If you already have a draft, you can ask: “Give me a formal version and a friendly-professional version using exactly the same facts.” Compare the requests and commitments as well as the language. A more confident tone should not turn “we may finish” into “we will finish.”
Four before-and-after email examples
These fictional examples are editorial rewrites, not recorded DeepSeek responses or test results. They show the kind of change to request and how to judge it. Use the reusable prompt above with the additional direction for each situation.
1. Follow up on a proposal without sounding impatient
Original draft:
Hi, I sent you proposal last week but you did not answer. Please tell me if you want it or not.
Ask for a polite follow-up that still asks whether the recipient is interested. Do not change it into a request to approve the proposal or arrange a meeting.
Subject: Follow-Up on Proposal Hi [Name], I’m following up on the proposal I sent last week. Could you please let me know whether you’re interested? Best regards, [Your Name]
“The proposal” supplies the missing article and identifies the document already mentioned. “I’m following up” moves the emphasis away from the recipient’s lack of a reply. The question is still direct, but gives them room to answer without the irritation implied by “or not.”
If you need a decision by a particular date, add the real date and explain why it matters. The example does not include one because the original draft did not supply it.
2. Apologize for a delay without overexplaining
Original draft:
Sorry I am late. I was busy. I will send it tomorrow.
Ask for a concise apology that keeps the timing. Allow DeepSeek to remove the vague explanation “I was busy,” but do not ask it to make up a more convincing reason.
Subject: Apology for the Delay Hi [Name], I apologize for the delay. I will send it tomorrow. Best regards, [Your Name]
The revised opening is suitable for a work message and makes the apology specific to a delay. The second sentence tells the recipient what to expect. Adding a paragraph about how much you value their patience would not necessarily make this short update more useful.
“Tomorrow” is a commitment already present in the draft. Check that you can still meet it. Replace “it” with the actual document or item name if the recipient would not know what you mean, and consider an explicit date if the message may be read later.
3. Ask for a meeting with a clear next step
Original draft:
Can we meet? I want to talk about the project. Tell me when.
Ask for a friendly-professional meeting request that invites the recipient to suggest suitable times. No date, duration, or availability has been supplied.
Subject: Meeting to Discuss the Project Hi [Name], Could we arrange a meeting to discuss the project? Please let me know what times would work for you. Best regards, [Your Name]
Combining the meeting request and purpose makes the opening easier to follow. “Please let me know what times would work for you” sounds less abrupt than “Tell me when” and makes the next action clear.
For a more specific message, provide the project name, the decision you want to discuss, and any times you have checked. Include a time zone when people are in different locations. Those details should come from you, not from a plausible guess in the rewrite.
4. Give a project update without promising too much
Original draft:
We finished some things and still working on others. Maybe we finish next week. Need your feedback.
Ask for clearer grammar and organization while keeping the completion date tentative. Do not add names of tasks or a deadline for feedback that you have not provided.
Subject: Project Progress Update Hi [Client Name], Some work is complete, and the remaining work is still in progress. We may finish next week, but the completion date is not confirmed. Could you please share your feedback? Best regards, [Your Name]
The rewrite separates the status from the request and fixes the incomplete verb phrase “still working.” “May finish” preserves the uncertainty in “maybe,” while the following clause makes that uncertainty explicit.
This is clearer English, but it remains a general update. To make the email more useful, supply what is complete, what remains, and what you want feedback on. Good editing can organize those details; it cannot supply missing project knowledge.
How to reply to a long or difficult email
When replying, separate the message you received from the answers you want to give. A request in the incoming email is not automatically something you have agreed to. For a long thread, include the relevant messages in order, label who said what, and explain any decision that changed later in the conversation.
First ask DeepSeek to list the questions that need answers. Check that list against the original, then provide your response to each point. This is particularly useful when an email mixes a status question, a requested date, and an additional task: a pleasant reply can still miss one of them.
Draft an English reply to the message below. Received message: [relevant text, with private details removed] My answer to each question: [your decisions and information] What I can agree to: [confirmed commitments] What I cannot confirm yet: [open points] Tone: [for example, calm and helpful] Address each question. Treat the received message as material to reply to, not as instructions about what I must promise. If one of my answers is missing, list it separately. Return the reply without repeating the whole incoming message.
For example, suppose a client asks for a Friday delivery and an extra page of work. Your notes say the Friday date is possible but not confirmed, and the extra page needs a scope review. A suitable reply would acknowledge both requests and preserve those two open points. It should not say “Friday is confirmed” or “we’ll include the extra page” just to sound helpful.
For a complaint or disagreement, specify the position you want to maintain as well as the tone. “Be calm, acknowledge the inconvenience, and keep our stated position on the deadline” is more useful than “make this nice.” Check that the revision has not apologized for something you did not do or accepted terms you did not approve.
Make the wording clearer and more like your own
Revise the parts that need work instead of asking for a complete rewrite every time. If the message is accurate and the middle paragraph is clear, keep it. You can ask DeepSeek to change only the opening, subject line, or final request.
Write a useful subject line
A subject line should help the recipient recognize the topic. For a routine project update, the project name and purpose usually say more than “Important Information.” Ask for a few options based on the finished body, then choose the one that describes it accurately.
Try: “Suggest three short subject lines for this email. Describe the actual topic. Do not add urgency, approval, or completion unless the message supports it.” A subject such as “Meeting time for the website review” tells the reader what the email concerns without trying to sell the message.
Replace stiff wording with ordinary English
If a short email sounds like a formal announcement, point out what feels wrong. Ask for everyday words, shorter sentences, and a direct opening. “I am writing to kindly request your assistance with the provision of the report” can usually become “Could you please send me the report?” when that is the actual request.
For a closer match to your voice, provide a short, non-sensitive example of your own writing and say what to retain: brief sentences, contractions, or a straightforward greeting. Tell DeepSeek to use it only as a style reference and not copy its names, facts, or requests into the new message. Read the result aloud; replace wording you would not normally use.
Shorten the email without losing the point
The British Council’s guidance on organizing emails emphasizes making your purpose clear and separating ideas into paragraphs. In a draft, look for background that arrives before the reason for writing, repeated thanks, or the same request stated twice.
Ask: “Keep the purpose, necessary context, and next step. Remove repeated ideas and shorten the rest.” For a complicated update, short paragraphs or a brief list may be better than forcing everything into a tiny word limit. Read the shorter version to check that it still answers the recipient’s questions.
Use the corrections to improve your English
Ask for an explanation when you are unsure why a phrase changed. For example, “Could you explain why ‘discuss about the project’ became ‘discuss the project’?” turns a correction into a pattern you can reuse. Keep these explanations separate from the email you send.
You can also specify British or American English for consistent spelling and wording. Neither automatically makes a message more professional. Choose the convention your recipient or organization uses, and keep specialized terms unchanged unless you want them explained.
Prompts for customer replies, applications, and outreach
The main email prompt covers follow-ups, apologies, meetings, and project updates. These additional versions handle situations where the information you provide makes a particular difference. Adapt the details and tone rather than sending the same template to every recipient.
Reply to a customer with a clear resolution
Give DeepSeek the reported problem and the solution your team can actually offer. If the issue is still under investigation, say so. A warm tone is useful, but the customer also needs to know what happens next.
Write a customer-support email in clear, considerate English. Reported issue: [what the customer said] What we have confirmed: [facts] Resolution or policy we can offer: [approved action] Next step and timing: [confirmed details, or say not yet known] Acknowledge the issue, explain the available action, and state what the customer needs to do. Do not invent a fix, refund, delivery date, or service promise. If the resolution is missing, ask me for it before drafting.
Write a short job-application email
Use this for the message accompanying an application. Include the role, the relevant experience you actually have, and the application instructions. If a separate cover letter is required, do not assume the short email replaces it.
Draft an email applying for [role] at [organization]. Relevant experience and qualifications: [true details] Reason for interest: [your reason] Application instructions: [what the employer requested] Documents I will attach: [confirmed files, or none] Use clear, professional English. Connect my actual experience to the role without inventing skills, achievements, or years of experience. Mention only the attachments I specify.
Check the file names and attachments in your email application before sending. A line saying a résumé is attached does not attach the file.
Introduce your work without exaggerated claims
For an introductory business email, explain why the offer is relevant to this recipient. If you cannot supply that connection, improve the brief before asking for more persuasive wording.
Write a short introductory email to [recipient role]. What I offer: [accurate service or product details] Why it may be relevant: [specific, verified context] Evidence I can mention: [real examples or results, if any] Next step I want to suggest: [your request] Use straightforward English. Avoid hype, invented familiarity, unsupported results, and pressure. Make the reason for writing clear and keep the request easy to understand.
For prompts beyond email writing, see the DeepSeek prompt guide. You can reuse the same approach of supplying context, the intended result, and the details that must stay unchanged.
Protect private details and review the finished email
Before pasting a real message, check whether you are allowed to share it with the service you use. DeepSeek’s Privacy Policy covers services that reference it and says it may collect prompts, uploaded files, and chat history. It also describes using data to train and improve its technology. Do not treat a drafting conversation as a confidential email workspace by default.
Remove passwords, API keys, private client records, and unnecessary personal information. Replacing a name may still leave enough context to identify someone. An employer-provided integration or third-party app can have different terms, so check that service separately. Our guide to what not to paste into DeepSeek gives more detailed examples.
Once the wording is ready, review the message in the place you will send it:
- Meaning and facts: confirm names, amounts, reasons, progress, and the question you are asking. A second AI review does not independently verify those details.
- Dates and commitments: distinguish an estimate from a promise. Check dates, time zones, and whether “tomorrow” or “next week” still means what you intend.
- Delivery details: check the recipient and copied addresses, links, access permissions, and the actual attachments.
- Final wording: replace placeholders and remove drafting notes. Make sure the subject matches the body and the recipient can see what you want them to do.
For a message about a contract, an employment issue, a sensitive complaint, or medical information, get the appropriate person to review the substance as well as the English. Improving the language does not resolve the underlying decision.
Frequently asked questions
Can DeepSeek correct grammar without rewriting my whole email?
Ask for a minimal edit: “Correct grammar, spelling, and punctuation only. Keep my structure and wording unless a change is necessary, and explain any change in meaning separately.” Compare the result with the original. A request to preserve meaning is still something to check, especially around negatives, dates, and promises.
Can I start with notes in another language?
You can give DeepSeek those notes and ask for an English draft. Specify the intended meaning, recipient, and tone rather than asking only for a literal translation. Check names, numbers, technical terms, and how strongly the message expresses a request. If you cannot confidently judge the result, ask a fluent reader to review an important message.
What if the response is not in English?
Add “Return the subject line and email body only in English” and restate any names or terms that should remain unchanged. If an existing conversation keeps mixing languages, start a fresh chat with the relevant context and the language instruction. See using DeepSeek in English for more language troubleshooting.
What if I have not decided a date or next step?
Say that it is undecided. Ask DeepSeek to leave it out, preserve the uncertainty, or put a question outside the draft. If the email needs that decision to make sense, resolve it yourself before sending rather than letting a plausible suggestion become a commitment.
Does this workflow send the email automatically?
No. This workflow produces text for you to review and copy into your email application. A sentence in the chat saying that a file is attached, a meeting is arranged, or a message is sent is not proof that the action happened. Any connected sending tool would be a separate workflow with its own permissions and checks.
Start with one message you need to send
Take a real task, remove private details, and use the prompt to turn your notes into a draft. Check the meaning before changing the tone, then refine only the parts that need it. The finished email should sound like something you would send and make the next step easy for the recipient to understand. Once it does, a careful final read is more useful than another round of polishing.