01
Sent through your WhatsApp number
The supplier sees a message from +60 14 **** — your number. Never atlas@edma, never a bot account. EDMA stays invisible to the counterparty.
AI · ATLAS
Atlas meets you
where you already work.
Trade operators run on WhatsApp with factories, email with clients, WeChat with Chinese partners, Slack with their team. Atlas lives in those channels — not a separate app. Forward an email to [email protected] and get a response drafted from live operational data. Tag Atlas in a WhatsApp thread and ask "where's order RD-2026-018?" Get an answer in the same thread, in the recipient's language, with full context.
Channels supported07WhatsApp · WeChat · Telegram · Email · Slack · Teams · TradeOS
Reply modeDraft-firstOperator reviews and sends · auto-send guardrails optional
Languages at v110Trade terms preserved: LC at sight, CIF, FOB, AQL 2.5
ContextLive graphReads orders, lots, shipments, payments, docs · not a doc upload
A SUPPLIER ASKS · 11:42 PENANG
A thread in WhatsApp. Atlas inside it.
A factory in Penang messages your account manager. Atlas reads the thread, queries the live operational graph, drafts a reply in Mandarin with English translation, and sends through your own WhatsApp number after you approve.
02
Pulled from your live operational graph
Production 78% · QC scheduled Apr 24 · shipment COSCO · ETA May 12 — read straight from the order, not from a PDF you uploaded last week.
03
Auto-translated, trade terminology preserved
Replies in the recipient's language with terms like FOB Shenzhen, AQL 2.5, LC at sight preserved — not what generic translation engines do.
04
Operator approves before send — drafted, not auto-sent
Default mode is draft. You review, tap Send. Auto-send is opt-in per channel and per counterparty, with guardrails (status-only replies, known counterparties, etc.).
THE PROBLEM ATLAS SOLVES
Operators don't want a new app. They want their channels to get smarter.
Your team manages 200 WhatsApp threads. Each one needs context.
The supplier asks where the order is. You open TradeOS, find the order, copy the status, switch back to WhatsApp, type it. Multiply by 50 active orders per week.
11 hrs / moper ops person
Comms tools and operational data live in separate worlds.
Forwarder emails about a customs delay. You read it in email. Update the shipment in TradeOS. Draft a client notification. Send it in email. Three apps, three context switches per event.
3 appsper single event
Time zones eat decisions.
Malaysian factory messages at 11pm your time. Mandarin. About a QC issue on a $200K lot. You copy to Google Translate, lose nuance, delay the response to morning.
12 hrsdecision slippage
WHAT ATLAS DOES
Five patterns, all anchored in your channels.
✉
Forward email, get a drafted reply
Forward any email to [email protected]. Atlas reads the thread, pulls operational context, drafts a response. You review, send. Reply leaves from your own email — recipient never sees EDMA.
→ FWD: "Updated PI for SHP-018?" ·draft attached in 6s.
@
Tag in chat, get an answer
@atlas in WhatsApp, WeChat, Telegram, Slack, or Teams. Ask a natural-language question. Atlas responds in the thread, in the recipient's language, with citations to the underlying data.
@atlas where's RD-2026-018? ·78% · QC Apr 24 · ETA May 12.
◐
Subscribe to a topic
"Tell me when anything changes on RD-2026-018." Atlas watches the operational graph and surfaces changes in your preferred channel — no polling, no missed updates.
/watch RD-2026-018 ·notifying you in Slack #ops-eu.
✓
Create tasks from signals
Atlas detects a needed decision — "margin on this order trending below threshold" — and creates a Task with the full operational chain attached. Not just a chat message you'll lose tomorrow.
margin alert · 14.2% on ORD-022 ·Task created → ops lead.
✎
Draft + send
Atlas drafts customer letters, supplier notifications, internal updates. Operator approves before send by default. Optional auto-send within configured guardrails — status-only replies, known counterparties, business hours only.
Draft delay note to Brevin Health ·DE + EN drafted · awaiting send.
WHAT MAKES ATLAS DIFFERENT
Atlas runs against your live operational graph.
Generic AI tools need you to upload a PDF and ask questions about it. Atlas reads the graph. When you ask "where's order RD-2026-018", it doesn't read a document. It reads the order.
Live, not static
Generic LLM tools need you to upload context. Atlas reads the graph. The graph is the context — it doesn't go stale between turns.
Cross-entity
A question about a supplier traverses to their open orders, recent communications, performance history, and capacity. No glue code, no integrations to build.
Language + trade terminology
Atlas preserves trade terms — LC at sight, CIF Hamburg, AQL 2.5 — across translations. Not what generic translation engines do.
REPRESENTATIVE QUERIES
What operators actually ask Atlas.
Eight representative queries Atlas is designed to handle — counterparty names anonymised, channels and answer shape from the v1 surface.
WhatsApp · opsEN
Where's order RD-2026-018?
↳ Atlas78% production, QC Apr 24, ETA May 12.
3 sources
Slack · #ops-euEN
Margin status for all open orders to EU clients
↳ Atlas12 orders · blended margin 18.4% · 2 below threshold (flagged).
12 sources
Email · QA teamEN
Which suppliers have certs expiring in 30 days?
↳ Atlas3 suppliers: Crescent (ISO 13485, Apr 28), Sapphire (FDA, May 12), Ariel (CE, May 18).
documents · 12
WhatsApp · salesDE + EN
Draft a delay notification to Brevin Health for SHP-2026-018
↳ AtlasDraft email attached · DE + EN · cause: Suez surcharge · revised ETA May 19.
awaiting approval
TradeOS · panelEN
Why is freight cost up 12% this quarter?
↳ AtlasSuez surcharge on 3 of 4 active routes · 14 orders affected · breakdown attached.
routes · shipments
Email · financeEN
Reconcile bank statement entries from Apr 1–15
↳ AtlasMatched 47 / 50 · 3 unmatched flagged for review · handoff to Accounting AI.
payments · invoices
Teams · QAEN
QC pass rate trend for Crescent over 90 days?
↳ Atlas94.2% → 90.1% · declining · outlier Lot-PL-058 with 18% failure rate.
lots · 312
WhatsApp · opsEN
Show me cold-chain excursions this week
↳ Atlas2 events: Container 7 (12°C for 6h), Container 11 (false alarm, within tolerance).
sensor feeds · 2
SEVEN CHANNELS
How Atlas works in each channel your team already uses.
Channel
Trigger
Response shape
Status
WWhatsApp
@atlas in thread
Answer in thread, sent from operator's WhatsApp number.
Internal · v1 surface
微WeChat
@atlas in thread
Answer in thread, in recipient's language, trade terms preserved.
Internal · v1 surface
TTelegram
@atlas in thread
Answer in thread; group + DM modes both supported.
Internal · v1 surface
@Email
Forward or CC [email protected]
Draft reply or new email, sent from operator's own domain.
Internal · v1 surface
SSlack
@atlas in channel or DM
Answer in channel or DM, with rich citations + action buttons.
Internal · v1 surface
MMicrosoft Teams
@atlas in chat or channel
Answer in chat with adaptive-card citations.
Internal · public Summer 2026
⌘TradeOS web
Atlas panel, always on right rail
Answer in panel + action buttons (create task, draft reply, watch).
Internal · v1 surface
SUITE-WIDE ARCHITECTURE
The trust currency under every Atlas response.
Atlas inherits the AI Suite's architecture — multi-provider, ZDR-by-default, three privacy tiers, per-channel controls, and a full audit trail.
Multi-provider
Claude primary, OpenAI + Gemini fallback, local Gemma 4 E4B floor. Failover routes to the next provider without context loss — invisible to the operator.
Three privacy tiers
Standard ZDR · Sovereign confidential computing · Air-Gapped on customer infra. Same Atlas across all three.
Zero data retention
ZDR contracts with every commercial provider. Your prompts and responses are never used for training — Anthropic, OpenAI, Google.
Per-channel · per-counterparty controls
Disable Atlas on WhatsApp for clients but keep it on for suppliers. Disable in WeChat entirely. Auto-send guardrails per scope.
Audit log of every action
Every read, every draft, every send, every approval logged inside the operating record. Exportable to your SIEM.
VS. ALTERNATIVES
Where Atlas fits versus the AI assistants you might already buy.
Each row is something a trade operator actually needs an AI to do. The honest answer for each tool — including ours.
| Capability | Atlas | ChatGPT Enterprise | Microsoft Copilot | Glean | Generic chatbot integrations |
|---|---|---|---|---|---|
| Native in operator's existing channels (no new app) | ✓ | — | Teams / Outlook | — | channel-specific |
| Live operational graph as context (not RAG-on-PDFs) | ✓ | — | — | enterprise search | — |
| Multi-language with trade terminology preservation | ✓ | generic translate | generic translate | — | — |
| Sends from operator's identity (recipient doesn't see AI/EDMA) | ✓ | — | — | — | — |
| Creates tasks, drafts replies, subscribes to topics | ✓ | drafts only | drafts only | — | — |
| Multi-provider with local resilience floor | ✓ | — | — | multi-model | — |
| ZDR on every commercial provider | ✓ | enterprise tier | enterprise tier | enterprise tier | — |
FAQ
Five questions buyers ask first.
If you have a sixth, we'd rather answer it in a call than write it here.
No, and yes. Atlas's responses are sent from your own email or WhatsApp number; the recipient sees a message from you. If they ask, you tell them you used AI to draft. The operator stays in control of disclosure — most counterparties don't notice or care.
Put Atlas in the channels your team already uses.
Book a 30-minute demo against EDMA Group's own operational graph and see Atlas answer a real factory thread — the same one we ran an hour ago. Public v1 ships Summer 2026.