iWMS O2O AI Agent Workshop — Session 2 (Email Push + User Share)

Purpose

Session Goal

Goal: master the new Email Push capability to send real reports to any mailbox — and collect your honest feedback, best practices, pain points, and feature requests so the next roadmap matches how you actually work.

Pre-workshop

Confirm Agent login, store scope, and that the email push is ready. No binding needed for email — you just give the recipient address.

During session

Hands-on Email Push practice first, then an open discussion where you share experience and raise requests. You set the agenda.

Post-workshop

Schedule a recurring report email, and keep logging best practices and requests into the shared feedback sheet.

Schedule

July 23 Agenda: 13:00-17:00

13:00-13:30Setup buffer: Agent login, store scope, email readiness

Everyone can follow the same session without technical interruption.

13:30-13:45Session 1 recap + today overview

Quick review of Session 1, then today's two topics.

13:45-14:45Module E1: Email Push — send your first report email

Email a report to any mailbox, no binding needed.

14:45-15:00Break

Collect quick questions.

15:00-15:45Module E1 hands-on: design and send a real report email

Build an HTML email with KPI cards, table, and a chart.

15:45-16:00Module E1 wrap: schedule a recurring report email

Preview the scheduled daily email via scheduler.

16:00-16:55Module S: User share & feedback discussion

Share best practices, pain points, and feature requests.

16:55-17:00Next steps and close

Leave with a scheduled email and a clear feedback channel.

Before 13:00

Pre-workshop Setup

00Readiness Checklist

Complete this before business users start the guided session.

30 MIN BUFFER

1Confirm Agent login and store authorization

Each participant logs in using their normal account.

Expected outcome: the Agent can show the current authorized warehouse/store context.

Verify: store name and scope match the participant's role.

2Confirm the email push works

Participants ask the Agent a business-friendly readiness question. The Agent checks the email connector in the background.

Can you send emails now? Please check if the email push is ready.

Expected outcome: the Agent confirms the email push is ready, or explains in business language that the sending mailbox is temporarily unavailable (and has logged it for follow-up).

Verify: the Agent never exposes technical details like the connector code — it only talks about "the sending mailbox".

3Confirm your work email address

Email push needs no binding or bind code — you simply tell the Agent the recipient email address when you ask for a report.

Expected outcome: each participant knows the work email address they will use to receive the report.

Verify: unlike LINE push, email requires no QR code or binding step.

Topic 1 · New Capability

Email Push — Send a Report to Any Mailbox

E1Send Report Emails Without Any Binding

Use the email-push skill to email a report to any address. HTML report with KPI cards, table, and a static chart. Scheduled emails go to the scheduler.

60 MIN

1Ask the Agent to email a report

Start with a simple, immediate send. The Agent gathers what it needs before sending.

Send today's outbound summary to my email [your email].

Expected outcome: the Agent uses email-push and starts collecting the recipient, content, and subject. If you did not give an email, it asks which mailbox to use.

2Provide the recipient

Give the Agent the work email address to send to. You can add cc/bcc later if needed.

Verify: the Agent never guesses or invents an email address — it always asks you for the mailbox if one is missing.

3Design the email content

Ask for a richer HTML report: KPI cards on top, a data table, and an optional trend chart.

Make it an HTML report: OTIFS KPI cards on top, a shortage table, and a trend chart.

Expected outcome: the Agent builds an HTML email with KPI cards, a table, and a static chart image. For a quick one-line alert, it can also send plain text instead.

4Confirm delivery

The email is queued and sent in the background. Confirm it actually lands.

Expected outcome: the Agent tells you the email was sent and asks you to check your inbox.

Verify: if you do not see it, check the spam folder. Click "Show images" in the email to see the chart — remote images are blocked by default, and key numbers also appear as plain text so you never miss them.

5Schedule a daily report email (optional)

For a recurring report, the Agent hands off to the scheduler with email as the channel.

Set up a daily 08:00 outbound email report for manager review.

Expected outcome: the Agent routes to scheduler-manager and picks "email" as the channel. Participants understand schedule, content, recipient, and manual review requirements.

Topic 2 · Open Discussion

User Share & Feedback

SShare Your Experience, Shape the Roadmap

Open discussion. Tell us what works, what does not, and what you need next. The facilitator logs every share into the feedback sheet.

55 MIN

1 · Best practice

Share one task where the Agent saved you the most time. What did you ask, and what did it do well?

2 · Pain point

What is the most frustrating part of using the Agent? Where does it waste your time or get the answer wrong?

3 · Wish list

What capability do you wish the Agent had? Name your top 3, in priority order.

4 · Trust & verify

How do you verify the Agent's output before acting on it? Share a time it was wrong or surprising.

Feedback workflow: the facilitator asks the Agent to log each share into the feedback sheet with columns: scenario, user, insight, request, priority, and follow-up owner.

Ready-to-use

Prompt Library by Scenario

Email a report

Send today's outbound summary to my email.

HTML report email

Make an HTML email with OTIFS KPI cards, a shortage table, and a trend chart.

Quick text alert

Send a one-line email to [email] saying the OTIFS rate dropped below target today.

Scheduled email

Set up a daily 08:00 outbound email report for manager review.

Post-workshop

Practice Cases Before Follow-up

Case	Task	What to verify
1	Email yourself a real report.	It arrives in your inbox (check spam if missing).
2	Design an HTML email with KPI cards, a table, and a chart.	KPI cards render, table is readable, chart shows after "Show images".
3	Set up a scheduled daily email report.	Agent routes to scheduler-manager with email channel.
4	Log one best practice and one feature request.	Both appear in the feedback sheet with priority.

Feedback workflow: after each practice case, ask the Agent to append the result to the feedback sheet with scenario, insight, request, priority, and follow-up owner.