Architecture Overview and Flow

flowchart LR

subgraph Client
A[📩 Incoming email]
end

subgraph Microsoft 365
B[📥 Manager mailbox]
end

subgraph Teemant Platform
C[⚡ START]
D[🤖 AI Engine]
E[🧠 TRI Router]
F[📋 Extraction Guide]
G[🧮 Reference Layer]
H[📤 Outputs Engine]
I[⏹ END]
end

subgraph Client IS
J[📦 Archiving]
K[📊 SFTP / API]
L[📧 Notification]
end

A --> B --> C --> D --> E --> F --> G --> H --> I
I --> J
H --> K
I --> L

<aside> 💡

Incoming email ↓ Manager mailbox (ACME-ENV) ↓ START event ↓ AI mailbox (ACME-ENV-IA) ↓ TRI (routing decision) ↓ Guide (data extraction) ↓ Reference layer (lookup) ↓ Outputs (JSON/EML/SFTP) ↓ END event (tag + archive + reply)

</aside>

Mailbox architecture (mandatory)

Each environment operates as a pair:

Mailbox Role
📥 Manager mailbox Receives incoming emails
🤖 AI mailbox Processes emails (the “AI assistant” mailbox)

ACME example (recommended):

👉 Typical total: 3 or 4 pairs (depending on the customer lifecycle)

Typical setup

Step 1 — Create and prepare the mailboxes

✅ Mandatory for each mailbox

1) Short name

⚠️ Names that are too long can overflow in Outlook and in connectors.

2) Add members