These 24 prompts turn Mistral Le Chat into a capable work assistant. They lean on Work mode — which routes to Medium 3.5 with extended reasoning for multi-step tasks — plus connectors for Gmail and Calendar and Le Chat's document analysis for long reports and contracts.

Each prompt is written out in full. The pattern is always the same: a clear role, your real context, hard constraints, and a named output format. Swap the [BRACKETS] and go. For the wider library see the best Mistral prompts, and for polished copy the Mistral writing prompts.

Advertisement

Email & communication

Give Le Chat the situation, the outcome you want, and a word cap. Connect Gmail so it can work from the real thread.

1. Draft a hard email

Help me write a difficult email. Situation: [WHAT HAPPENED]. Recipient: [WHO, and our relationship]. Outcome I want: [GOAL]. Keep it under 120 words, professional and calm, own my part without over-apologizing, and end with a clear next step. Give me two versions — one warmer, one firmer — and a subject line for each.

Why it works: Two calibrated versions let you pick the tone the moment calls for instead of editing one draft twice.

2. Say no without burning the bridge

Write a polite but firm reply declining this request: [PASTE REQUEST]. I want to say no clearly, keep the relationship warm, and offer one small alternative if reasonable. Under 90 words, no groveling, no false promises to "revisit later" unless I mean it. Give me the email plus a one-line version for chat.

Best for: Protecting your time without the guilt spiral that produces a soft, ambiguous no.

3. Turn a thread into a decision

Read this email thread and cut through it: [PASTE THREAD]. Tell me what is actually being decided, where people agree and disagree, what is blocking a decision, and the single question I need to answer to move it forward. Then draft a short reply that names the decision and proposes a next step. Do not add positions no one took.

Why it works: A long thread hides the real decision; this surfaces it and drafts the reply that ends the loop.

4. Status update from bullets

Turn these rough bullets into a clean status update for [AUDIENCE, e.g. my manager / the team]: [PASTE BULLETS]. Structure: what shipped, what is in progress, what is blocked (and what I need), and what is next. Keep it skimmable, lead with the headline, and flag risks honestly without burying them. Under 200 words.

Best for: A weekly update that reads clearly and does not hide the blockers.

5. Calm an unhappy customer

A customer sent this complaint: [PASTE MESSAGE]. Draft a reply that acknowledges the specific problem, takes appropriate responsibility, states exactly what we will do and by when, and offers [what you can offer]. Empathetic but not sycophantic, under 130 words. Then give me a one-line internal note on what we should fix so this stops recurring.

Why it works: A concrete "what and by when" de-escalates far better than a wall of apology.

Meetings & planning

Le Chat is strong at structure. Give it the raw material and let it impose order — decisions, owners, dates, and next steps.

6. Meeting notes to actions

Turn this meeting transcript into structured notes: [PASTE TRANSCRIPT]. Output three sections: Decisions made, Action items (a table with Owner, Task, Due date), and Open questions. Do not invent details, and flag anything left unresolved. Then draft a two-line recap email I can send to attendees.

Best for: Making a meeting stick with a shareable recap and an owner on every action.

7. Agenda that respects the clock

Build an agenda for a [30]-minute meeting about [TOPIC] with [WHO]. Desired outcome: [OUTCOME]. Allocate minutes per item, mark each as decide / discuss / inform, put the decision items first, and add a "if we have time" section at the end. Include one line on what attendees should prepare beforehand.

Why it works: Timeboxing and decide/discuss/inform labels keep the meeting from drifting into status theater.

8. Prioritized weekly plan

Here is everything on my plate this week: [PASTE LIST]. Act as a sharp chief of staff. Sort by impact and urgency, name the three things that actually move the needle, say what to delegate or drop, and lay it out as a day-by-day plan. Call out anything that looks like busywork or a meeting that could be an email.

Best for: Turning an overwhelming to-do dump into a focused, honest week.

9. Project kickoff brief

You are a delivery lead. Turn this into a one-page project brief: [DESCRIBE PROJECT]. Cover the goal in one sentence, scope (in and out), milestones with rough dates, dependencies, the main risks, and the people who need to be involved. Use Work mode to reason it through. Output clean sections ready to paste into a doc.

Why it works: "Scope in and out" plus explicit dependencies is what stops projects from quietly expanding.

10. Prep for a tough conversation

I need to have a difficult conversation with [WHO] about [ISSUE]. Help me prepare: the outcome I want, my opening line, the two or three points to make, the likely objections and a calm response to each, and where I can compromise versus where I cannot. Keep it as a one-page prep sheet, not a script.

Best for: Walking in clear-headed with responses ready, without sounding rehearsed.

Strategy & analysis

Turn on Work mode and, where you need facts, web search. Ask Mistral to be blunt about weaknesses so you get analysis, not a pep talk.

11. One-page strategy brief

You are a pragmatic strategy advisor for a [COMPANY TYPE / STAGE]. We are deciding whether to [DECISION]. Context: [KEY FACTS AND CONSTRAINTS]. Use Work mode to reason it through, then lay out the options, the main trade-offs, the biggest risk, and what you would do and why. Be blunt about weaknesses. Output a one-page brief: recommendation, rationale, risks, next step.

Why it works: The "be blunt" instruction and a fixed structure produce a decision doc, not a hedge.

12. Competitive SWOT

Build a SWOT analysis for [MY BUSINESS] competing against [COMPETITOR]. Use web search for the opportunities and threats and cite each external claim with a link and date. Keep every point specific — no generic filler — and end with the single move I should make first and why. Output a four-quadrant table plus the closing recommendation.

Best for: A SWOT grounded in current facts rather than last year's assumptions.

13. Pricing options analysis

Help me think through pricing for [PRODUCT / SERVICE]. Current price: [X]. Costs and margin: [DETAILS]. Propose three pricing options (e.g. hold, raise, restructure into tiers), and for each give the rationale, the likely effect on revenue and churn, and the main risk. Assume [KEY CONSTRAINT]. Output a comparison table, then your recommendation.

Why it works: Three costed options with risks beats a single confident number you cannot pressure-test.

14. Pre-mortem on a plan

Run a pre-mortem on this plan: [PASTE PLAN]. Imagine it is [SIX MONTHS] later and it failed. List the most likely reasons it failed, ranked by probability, then for each give one concrete thing I could do now to prevent or reduce it. Be specific and a little pessimistic — I want the failure modes, not reassurance.

Best for: Surfacing the risks you are too close to the plan to see.

15. Summarize a market report

Read the attached market report and give me: the headline takeaways in 5 bullets, the numbers that matter with the page references, what it means for [MY BUSINESS], and any claim I should double-check independently. Note where the report is opinion versus evidence. Keep it to one page.

Why it works: Separating opinion from evidence keeps a vendor report from setting your strategy on marketing spin.

Advertisement

Ops & hiring

Ops work is structure work — SOPs, JDs, rubrics, onboarding. Give Mistral the specifics and it handles the scaffolding.

16. Write an SOP

Write a standard operating procedure for [PROCESS]. Audience: [WHO WILL FOLLOW IT]. Include: purpose, when to use it, prerequisites, numbered steps with the exact action per step, common mistakes to avoid, and who to escalate to. Write it so a new hire could follow it without asking questions. Output in clean Markdown with a short checklist at the end.

Best for: Documenting a process once so it stops living only in your head.

17. Draft a job description

Write a job description for a [ROLE] at [COMPANY / STAGE]. Include a two-line pitch for why the role matters, core responsibilities, must-have versus nice-to-have skills, and what success looks like at 90 days. Keep the tone human, not corporate, and avoid buzzwords. End with a one-line inclusive note. Under 400 words.

Why it works: A 90-day success line forces clarity on what the role is actually for.

18. Interview questions and rubric

Create an interview guide for a [ROLE]. Give me 6 questions that test the real skills (mix behavioral and practical), what a strong versus weak answer looks like for each, and a five-point scoring rubric so different interviewers rate consistently. Avoid trivia and gotchas. Output the questions, the answer signals, and the rubric as a table.

Best for: Making hiring more consistent and less gut-feel across a panel.

19. Onboarding plan

Design a 30-60-90 day onboarding plan for a new [ROLE] on my [TEAM]. For each phase give the goals, who they should meet, what they should learn, and one small win they should aim for. Keep it realistic for someone ramping up, and flag what I (the manager) need to prepare before day one. Output as three phased sections.

Why it works: Naming a small win per phase gives the new hire momentum and you a progress signal.

20. Vendor comparison

Use web search to compare [VENDOR A], [VENDOR B], and [VENDOR C] for [USE CASE]. Evaluate on price, key features, integrations, support, and lock-in. Cite current pricing with links and dates. Build a comparison table, flag any red flags in reviews, and recommend one for a [BUDGET / TEAM SIZE] buyer. Note what you could not verify.

Best for: A sourced short-list you can defend, not a gut pick.

Finance & documents

Le Chat's code interpreter and 256K context handle numbers and long documents. Keep it anchored to the data you give it.

21. Budget model in Sheets

Help me build a simple [12-month] budget model for [BUSINESS / PROJECT] in Google Sheets. Inputs: [REVENUE ASSUMPTIONS, FIXED COSTS, VARIABLE COSTS]. Give me the sheet structure, the formulas for each row, and how to add a best/expected/worst scenario toggle. Explain what each formula does and where it could break. Keep it maintainable by a non-finance person.

Why it works: Explained formulas plus a scenario toggle give you a model you can actually run and update.

22. Invoice and expense summary

Here are my invoices/receipts: [UPLOAD FILES]. Using OCR and the code interpreter, extract vendor, date, category, and amount into one table, total by category and by month, and flag any duplicate or unusually large item. Preserve exact numbers, and mark anything you could not read as "unclear" rather than guessing. Output the table plus the summary totals.

Best for: Turning a pile of receipts into a reconciled summary without manual entry.

23. Contract plain-English review

Read the attached contract and explain it in plain English. List the key obligations on each side, the term and renewal/termination rules, payment terms, liability and IP clauses, and anything unusual or one-sided I should push back on. Quote the relevant clause for each point. This is not legal advice — flag where I should consult a lawyer.

Why it works: Quoting the clause behind each point makes the review checkable against the actual document.

24. Board or investor update

Draft a monthly investor update from these inputs: [KEY METRICS, WINS, LOWLIGHTS, ASKS]. Structure: a one-line TL;DR, metrics with the change versus last month, wins, challenges (be honest), and specific asks. Keep it confident but straight — no spin on the bad news. Under 400 words, ready to send. Then suggest one metric I am not tracking but should.

Best for: A credible update; investors trust founders who report the lowlights plainly.

For the full set across writing, coding, and research, start with the best Mistral prompts roundup, or grab reusable skeletons from the Mistral prompt templates.

Frequently Asked Questions

What is Work mode in Le Chat?

Work mode is Le Chat's setting for complex, multi-step tasks like long research, document drafting, and structured analysis. It routes you to Mistral Medium 3.5 with extended reasoning enabled and default-on connectors, so it plans before it answers. Use it for anything that needs more than a one-shot reply.

Can Le Chat connect to my email and calendar?

Yes. Le Chat supports connectors for services like Gmail, Calendar, Drive, and Slack, which let it pull real context into a prompt — for example triaging your inbox or turning a thread into action items. Enable the connectors you need in settings before running those prompts.

Is Mistral good for European business communication?

It is a strong fit. Mistral's models are strong across European languages and take an EU-centric view of data and privacy, so drafting in French, German, Spanish, or Italian reads natively rather than translated. Name the language and the local courtesy register in your prompt.

How do I keep Mistral from inventing facts in a brief?

Give it the real inputs and tell it not to add anything beyond them: "use only the information I provide, and flag any gap instead of filling it." For anything external, turn on web search and require a cited link with a date for every claim.

Which model handles a long document best?

Mistral Medium 3.5 has a 256K-token context window, so it can hold long reports, contracts, and transcripts at once. Upload the file, ask for page or section references in the summary, and it will keep the analysis anchored to the source.

Do these prompts work on the free tier?

Most do. Le Chat offers web search, Canvas, code execution, image generation, and the Agent Builder broadly, and Work mode for multi-step tasks. Heavier usage, enterprise connectors, and higher limits sit on paid and Enterprise plans, but the prompt structure is the same on every tier.

How do the [BRACKET] placeholders work?

Anything in square brackets is a swap-in. Replace [DECISION], [AUDIENCE], or [PASTE NOTES] with your own details, and delete brackets you do not need. Keep the wording around them, which is what makes the prompt produce a usable result.

Advertisement