Meeting Notes — Lead Management System | U.S-01: Lead Capture Form

Table summary: Meeting details for June 29, 2026, from 10:00 to 10:30 AM, facilitated by Sarah Chen (PM) with James Okafor (BA) taking notes. Attendees included Sarah Chen (PM), James Okafor (BA), Marcus Liu (Dev Lead), Priya Nair (UX), Tom Reyes (Sales Ops), and Dana Fong (QA Lead). The next meeting is scheduled for July 7 for Sprint Planning.

Reference: Attachment A — Full project scope, all user stories U.S-02 through U.S-08, risks & all action items

U.S-01: Lead Capture Form

As a sales rep, I want to capture lead contact info (name, email, phone, company) so I can follow up efficiently.

Acceptance Criteria

- Form fields: First Name, Last Name, Email (required), Phone (optional), Company, Lead Source, Notes.

- Email validates on blur; form blocked from submission without valid email.

- Duplicate check runs against C.R.M on email; inline warning with link to existing record (non-blocking — rep can override).

- On success: lead saves to C.R.M, rep sees confirmation with new lead I.D.

- W.C.A.G 2.1 A.A compliant; page load less than 2s.

:

Key Decisions

• Phone field is optional (not required). ✓

• Duplicate check: email-only match for Phase 1. ✓

- Duplicate warning is non-blocking — rep can override and save. ✓

- Lead Source = configurable dropdown; Sales Ops owns the list.

- W.C.A.G 2.1 A.A is a hard requirement. ✓

Discussion Highlights

- U.X (Priya): Single-page form, inline validation, non-blocking duplicate warning.

- Dev (Marcus): C.R.M A.P.I email-match endpoint needs confirmation; may debounce on field blur if A.P.I latency greater than 500ms.

- Sales Ops (Tom): Company Name = free text, no lookup. Lead Source values T.B.D.

- Q.A (Dana): Test cases needed for valid submit, duplicate, invalid email, special chars, and accessibility.

Action Items

Table summary: A list of action items for Story Details, with deadlines ranging from July 2 to July 5. Immediate tasks due July 2 include Marcus confirming the CRM API email-match endpoint, Tom providing the Lead Source dropdown list, and Sarah confirming SendGrid provisioning. Tasks due July 3 involve Priya sharing the US-01 wireframe and James adding US-01 to Jira with sub-tasks. The final item is for Dana to draft the QA test plan for US-01 by July 5.

You have reached the end of the document.