Use case · Just you · Inbox memory
Find every silent thread across email and Telegram
Every reply you don't write today is a decision someone else makes for you. Magnis surfaces the threads you've gone silent on — across email and Telegram — with last context and a one-click draft to close the loop.
Demo workspace — uses simulated data (Ava Chen / Lumen Labs). When you download Magnis, Gmail and Telegram connectors sync your real graph; the patterns below run on your data.
Step 1
Describe the task
One question, end of week. No filtering rules, no manual flagging — Magnis walks the graph for you.
You ask
Show me threads where I went silent for a week and people are waiting on me.
The prompt names no project, no person, no surface. Magnis has to find them.
Step 2
Give Magnis context
Magnis answers from your graph — entities, links between people and projects, a temporal events log of every sent and received message. Silence is a signal in this graph, not a missing field.
Required context
- ·Gmail + Telegram threads with last sent/received timestamps
- ·Project graph linking each person to the work they touch
- ·Events log — temporal append-only history that lets Magnis detect silence
Optional context
- ·Notes per person — context Magnis carries forward
- ·Custom silence threshold (default ≥7 days, can be ≥3 or ≥14)
- ·Trigger on schedule — daily morning digest at 8am
Step 3
What Magnis creates
A digest. Threads ranked by impact: project criticality × days silent × project-owner stakes. Each row clicks back to the source.
Lin Xia
Procurement Director · Meridian Health
“Following up — can your team confirm the SOC 2 bridge letter is ready before Friday's review?”
Suggested
Send the bridge letter ETA. Priya owns it — pull her status into the reply.
Daniel Price
Investor · Westbridge Capital
“Are we still on for the NYC dinner? Need to lock my calendar this week.”
Suggested
Confirm dinner date + time. No personal conflicts found in your calendar.
Marc Dubois
VP Operations · BluePeak Robotics
“Hi — the corrected import map you mentioned last week hasn't landed. Can you confirm timing?”
Suggested
Acknowledge the slip. Reconstruct what was promised — escalate to Sara if blocked.
Nora Singh
COO · Northstar Clinics
“Got the pilot proposal — quick question on the urgent-care examples.”
Suggested
Send the urgent-care examples package. Reply template ready.
Mateo Alvarez
Finance · Lumen Labs
“Hey — I need your sign-off on Q2 vendor renewal for AWS by EOW.”
Suggested
Sign off or flag. Vendor cost summary attached — quick decision.
Click any row → jump to the original thread. Click the “Suggested” chip → Magnis drafts the reply in the right surface (Telegram or email).
Step 4
Follow-up prompts
What you do next, written as one-liners.
Auto-draft all five replies
“Draft replies to all five threads above in the right surface. Hold for my approval before sending.”
Schedule the digest
“Run this every weekday morning at 8am. Ping me only if a critical-project thread crosses 5 days.”
Group by project
“Show ghost threads grouped by project. What's slipping where?”
Step 5
Tips & troubleshooting
Silence isn't the same as neglect.
Some threads end naturally — Magnis ranks by project criticality first, so a stale chat with a casual contact won't outrank a week-silent customer reply.
Rank, don't alarm.
The digest never paginates beyond the top 5-7 threads. If everything is urgent, nothing is.
Trust the “awaiting approval” state.
Magnis drafts but does not send by default. The connector requires you to confirm before any outbound action.
See the digest on your own threads.
Magnis runs locally. Connect your Gmail and Telegram, get the same digest tomorrow morning on your own graph.