Use case · Cowork
Reply to a foreign-language customer in one screen
Magnis reads a Chinese procurement note forwarded by your partner, names what is actually blocking the deal, surfaces who owns each piece of evidence, and drafts a reply you can send in Telegram — all from email, notes, meetings, and project context already in your graph.
Step 1
Describe the task
A partner forwarded a Chinese procurement email mid‑week. You have roughly five minutes between meetings to figure out whether the deal is actually slipping, who owes what, and to send something useful back. The prompt is a single sentence — Magnis is responsible for walking the graph.
You ask
Kenji forwarded an email in Chinese from Lin. Translate it to English, tell me what blocks the Meridian pilot, and draft a reply I can send in Telegram.
The prompt does not name SOC 2, retention terms, or the people who own them. Magnis has to find them.
Step 2
Give Magnis context
Magnis answers from the graph that already exists in your workspace. The Meridian pilot project links the partner, the procurement contact, the calendar review, the security checklist note, and the forwarded email thread. You do not paste documents into the prompt.
Required context
- ·Forwarded email from Kenji Watanabe containing Lin Xia's Chinese note
- ·Project Meridian Pilot Readiness linking the partner, contacts, and the security checklist
- ·Calendar event Meridian procurement review scheduled before Friday
Optional context
- ·Telegram connector to send the drafted reply directly
- ·Note Meridian Security Checklist with current owners
- ·Trigger that watches Lin's address for follow‑up procurement replies
Step 3
What Magnis creates
One pass returns three artifacts: a clean translation, a named blocker with owners, and a reply you can send. Each claim is anchored to a record in your graph, not invented.
Read Fwd: Meridian procurement note from Kenji Watanabe.
Original (zh)
您好 Kenji， 我们可以继续推进试点，但是采购评审需要在周五前看到 SOC 2 bridge letter，以及数据保留条款的英文说明。如果这些材料不能及时提供，我们可能要把启动时间推迟到下个月。 谢谢， Lin
English
Hi Kenji, We can keep the pilot moving, but procurement review needs to see the SOC 2 bridge letter and an English summary of the data‑retention terms before Friday. If those materials are not available in time, we may have to push the launch to next month. Thanks, Lin
The blocker is procurement evidence, not product readiness. Lin needs the SOC 2 bridge letter and an English data‑retention summary before Friday; otherwise launch slips to next month.
Owners (from project graph)
- Priya Nair — SOC 2 bridge letter
- Sara Patel — product rollout / retention note
- Kenji Watanabe — partner communication
Kenji — Priya is sending the SOC 2 bridge letter to Lin today. I'll attach the English data‑retention summary in the same thread. Could you ask Lin whether procurement needs a redline or a signed addendum, so we keep Friday on the table?
Step 4
Follow‑up prompts
Three things you usually do next, written as one‑liners. The graph already has the answers.
Send the drafted reply
“Send the Telegram draft to Kenji and add a follow‑up trigger if Lin replies with a redline.”
Brief Priya on what procurement needs
“Summarise the SOC 2 evidence Lin needs and message Priya in Slack with the deadline and the Friday calendar link.”
Watch for procurement replies
“Set a trigger on Lin's address — when she replies, append the answer to the Meridian Security Checklist note and ping me.”
Step 5
Tips & troubleshooting
Let Magnis pull from the project, not the prompt.
If you paste the email body into the prompt yourself, Magnis will translate it but cannot tell you who owns the SOC 2 letter. Forwarded mail linked to the project is what unlocks the blocker analysis.
Name the destination surface.
Asking for a reply “in Telegram” vs “in email” changes the tone Magnis drafts. Telegram replies are concise and direct; email replies include the explicit redline / addendum question.
Trust the “awaiting your approval” state.
Magnis drafts but does not send by default. The Telegram connector requires you to confirm before any outbound action, so a wrong translation never ships to the partner.
Ready to try it on your own pilots?
Magnis runs locally on your machine, connects to your inbox and chat, and stores the graph that makes this answer possible.