Intake acknowledgement

Direction: Outbound email FROM Nexus to the initiator (not an inbound sample).

Template: T-02 from `email-templates/nexus-email-templates.md`

From: nexus@nexus-genesys.com
To: unknown@example.com
Subject: Project Intake Received: ACME Transport Migration

Hi Charly,

Nexus has received the intake for ACME Transport Migration.

Customer: ACME Transport
Tech Lead: Charly Yi <charly.yi@genesys.com>
Planned dates: 2026-08-04 to
Current focus: Gate 0 - Pre-Sales and Kickoff Preparation (In progress)

Migration from legacy platform to Genesys Cloud CX for approximately 2000 agents

Approximate 10-month duration with 6 go-live events aligned to Customer LOBs

Documentation received and captured in the project record

Structured SOW fields are available for review

1. Review uploaded documentation and confirm SOW fields on the project record match the attachment extraction
2. Pre-fill the Gate 0 gated process checklist from intake and SOW context
3. Send Charly the tech lead onboarding email with the Gate 0 checklist embedded
4. Begin Friday weekly status tracking when onboarding is complete

No email has been sent outside this local Nexus demo.

Thank you,

Nexus
Delivery Methodology & Gated Process Director
nexus@nexus-genesys.com

• Outbound T-02 draft; inbound samples are `inbound_*_project_intake_email.md` and `new_project_intake_email.md`.
• Initiation path: Path B. Path B: Delivery Manager initiated; no separate DM assignment email (T-04) required.
• Project record: ACME-TRANSPORT-MIGRATION-2026-001.
• Roster at intake:

| Role | Name | Email |
| --- | --- | --- |
| Tech Lead | Charly Yi <charly.yi@genesys.com> | charly.yi@genesys.com |
| Delivery Manager | Charly Yi | unknown@example.com |
| Manager | To Be Defined | To Be Defined |

• Documentation received (not shown in email body): SOW reference (simulated attachment)
• Attachments on record: ACME_financial_SOW_Document.pdf
• Detailed SOW extraction stays in Project Intake Agent and Overview.