3.1 Email Management & Structured Follow-ups
You get 10+ supplier emails a day, each with a Tech Pack PDF, product images, or a quote. Information is scattered across your inbox — untrackable, unqueryable. A general-purpose AI assistant can help you draft replies, but it isn't connected to your inbox or your tables — you'd still move everything in and out by hand. AOS Work turns key information from emails directly into structured records in a Base.
Resources Used
| Type | Resource | What it does here |
|---|---|---|
| Connector | Outlook or Gmail | Reads inbox mail and sends replies |
| App | Library | Stores extracted attachments and images |
| App | Base | Stores the extracted structured records |
What You Can Do
-
Read Outlook / Gmail inbox emails, extract key info (supplier/order/amount/delivery date) and write it to a Base
-
Auto-extract email attachments (images/PDFs/Excel files), save them to Library with tags
-
Draft multi-language email replies, confirm, then send — all from AOS Work
Before starting, configure the mail connector using Connector setup and authorization, then add Library and Base. See Base tables and fields for linking Library files to records.
Steps
-
In 【Explore】 → 【Connectors】, add Outlook or Gmail and follow its authorization prompts (Connectors are enabled and approved by your IT admin — ask IT if it isn't listed)
-
Tell the Agent which emails to process, what fields to extract, and which table to write to
-
The Agent reads the emails, extracts the data, and creates structured records
-
Attachments are saved to Library automatically, linked to the table records
-
Need to reply? State your key points and language — the Agent drafts the email
-
Confirm, send — all inside AOS Work
Exercise: Create follow-ups from email materials
Read the example email archive named Course Mail in Library. Its two messages concern orders PO-401 and PO-402.
Select Library to read supplier names, quantities, and attachments. Select Library and Base to save the attachments in Library and write order details and attachment paths to the Supplier Follow-up table. Finally, query PO-401 and generate Reply Draft.md, a reply asking for its shipment date.
Sample Prompt
Extract the following and write to a Base: supplier, email date, order number, quantity, key request, attachment list.
Save any images from attachments to Library, named "supplier_order_date" and tagged "supplier email".
Expected Results
-
Fields from 10 emails written to the specified Base table
-
Attached images saved to Library, searchable by supplier/order
-
Later, you can just ask the Agent "What did Hartmann send this week?" and get the answer from the table
Sub-scenario 1-A: Customer Service — Batch Complaint Email Follow-ups
You're a customer service lead. Your team gets 20+ complaint emails a day, each with attached photos (quality issue shots). Complaints scatter across individual inboxes — trends stay invisible, progress is hard to track.
With AOS Work, the Agent batch-reads complaint emails, auto-classifies and rates severity, files images to Library, and writes everything to a trackable Base.
Sample Prompt
1. Auto-classify complaint type by analyzing email body keywords
2. Auto-rate severity (P1 = batch impact/escalation, P2 = single-item issue, P3 = general inquiry)
3. Save attached images to Library using customer_order_number and retaining the original extension.
Expected results:
-
Fields from 20 complaint emails written to the specified Base table
-
Complaint images auto-filed in Library, searchable by customer/order
-
Supervisors can spot trends directly from the table: "Quality complaints are up this month"
-
Downstream: the Agent can reference "Hartmann's complaint photos" in later conversations — less time digging through emails
Sub-scenario 1-B: Project Manager (see Chapter 2) — Supplier Emails + Attachments → Project Tracking Table
You're a project manager. 10+ supplier emails a day, each with a Tech Pack PDF, product images, or sample photos. Information lives in your inbox. When you meet with the team, you're digging through emails.
With AOS Work, the Agent reads recent supplier emails, auto-extracts key info and attachments, and writes to a project tracking table grouped by supplier.
Sample Prompt
1. Auto-classify attachments: Tech Pack PDFs → extract key parameters (fabric/size/color) into the table
2. Product images → save to Library, named "supplier_style_date"
3. Highlight the "action needed" column so it's easy to review in meetings.
Expected results:
-
Scattered supplier emails → one project tracking table grouped by supplier
-
Tech Pack parameters are no longer buried in PDFs — they're queryable in the table
-
Sample photos auto-filed in Library, linked to the supplier row
-
Project manager asks AOS Work: "What did Hartmann send this week? How's the progress?" → the Agent answers from the table
-
Downstream: Friday's weekly report auto-pulls table data to generate a progress update.