User Stories & Acceptance Criteria

Prepared by Isaac Olaosebikan · Sample artifact · Version 1.0

Epic: Own every new lead

Sales representatives need a predictable lead queue and managers need visibility into exceptions.

US-01 · Territory assignment

As a sales representative, I want new leads assigned by territory so that I can respond without waiting for manual allocation.

1. Given a new lead with State = Lagos, when it is saved, then its owner is the Lagos Sales Queue.
2. Given State = Abuja, when saved, then its owner is the Abuja Sales Queue.
3. Given an unknown or blank state, then its owner is the Lead Triage Queue and it appears in the exception report.

US-02 · Follow-up task

As a sales manager, I want an automatic follow-up task so that every lead has a visible next action.

1. On creation, exactly one open follow-up task is linked to the lead.
2. Urgent leads use the one-business-hour target; standard leads use four business hours, subject to approved business hours.
3. The assigned queue or responsible user receives a notification.

US-03 · Duplicate review

As a CRM administrator, I want likely duplicate leads flagged so that records can be reviewed without losing legitimate inquiries.

1. A potential match on email or phone produces a warning.
2. A reviewer can inspect both records before a merge.
3. The rule does not silently delete either record.

US-04 · Management reporting

As a sales manager, I want a dashboard for lead age and backlog so that I can identify stalled work.

1. Dashboard filters include territory, source and date range.
2. Unknown-territory leads are separately visible.
3. Counts reconcile with the underlying report.

Open decisions

Confirm business hours, queue membership, territory mapping, what qualifies as urgent and whether duplicate warnings should block creation.

This document is a fictional portfolio demonstration. It contains no client data and makes no claim of completed implementation or measured results.