# Lifecycle and Lead Handling with Conflicting Permission and Outcome Records

**Synthetic practice case — learner version.** All record keys, organisation rules, events and values are fictional. No real personal data appears. This is practice material, not a real organisation, legal rule or audit finding.

## Your decision

A fictional software trial business plans a promotional onboarding email and an advertising audience upload at 12:00 UTC on Monday 5 October 2026. A manager wants every CRM lead included because it was “already collected”. Marketing operations has received conflicting exports and a complaint about slow lead handling. Decide what must be held, clarified or separately authorised; do not contact or upload anything.

## Evidence A — scenario rules, not law

The fictional organisation's approved rule v3 says promotional email requires a traceable affirmative email choice for the stated offer and no later withdrawal. A trial-service request alone is not promotional permission. Advertising matching requires a separate recorded owner assessment and approved destination; email permission does not cover it automatically. A known suppression must not be overridden by an older extract. Ambiguous records are held for the privacy/channel owners. This fictional rule is not a universal account of legal permission.

Routing rule v2: newly accepted trial requests go to the trial queue. SLA = assigned to a responsible owner within **two business hours**, Monday–Friday 09:00–17:00 UTC, excluding no additional holidays in this exercise. This SLA measures assignment, not first contact. Automated promotional contact remains subject to permission checks. All timestamps below are UTC; do not invent a different timezone or clock.

## Evidence B — minimal permission and source records

| Key | Actual supplied source record | Later event / restriction | 5 Oct 08:00 CRM export |
|---|---|---|---|
| L01 | 1 Oct 10:00 trial request; offer-email choice Yes; notice v3 captured | No withdrawal in supplied source history; complete destination check not supplied | Marketing=True |
| L02 | 1 Oct 11:00 offer-email choice Yes; notice v3 | 4 Oct 16:00 withdrawal acknowledged in permission service | Marketing=True |
| L03 | 2 Oct 15:00 webinar attendance list from partner | Partner says contacts are “approved”; underlying notice, choice and onward-use terms absent | Marketing=True |
| L04 | 2 Oct 16:30 trial request; offer-email choice No; notice v3 | No later promotional choice supplied | Marketing=True |
| L05 | 5 Oct 08:30 offer-email choice Yes; notice v3 | Not yet present in the earlier CRM extract | Missing |
| L06 | 1 Oct 12:00 offer-email choice Yes on key A; withdrawal 3 Oct 09:00 on key B | CRM says A/B may be one person; approved merge/match evidence absent | Marketing=True on A |

Keys are artificial exercise labels, not hashes of real identifiers. No phone, address, email or demographic attribute is supplied. The destination upload specification includes offer-interest and a hashed contact field, but no separate advertising-use assessment or destination approval is supplied. Do not infer that hashing resolves this gap.

## Evidence C — suppression and export chronology

- Sending system snapshot at 3 October 08:00 shows none of L01–L06 suppressed. It predates the L02 withdrawal and the L06 key-B event.
- Integration log at 5 October 09:00 says “sync job accepted”. It supplies no per-record result, payload scope or destination acknowledgement.
- Promotional audience file assembled at 5 October 09:15 contains L01, L02, L03, L04 and L06-A from the 08:00 CRM export. L05 is not included.
- No send or advertising upload has occurred in this case. The manager's requested noon launch is a proposal.

## Evidence D — routing and service observations

| Trial key | Accepted trial time | Assignment record | First human-response record |
|---|---|---|---|
| L01 | Thu 1 Oct 10:00 | Thu 1 Oct 10:30 | Thu 1 Oct 12:30 |
| L02 | Thu 1 Oct 11:00 | Thu 1 Oct 14:00 | Thu 1 Oct 14:20 |
| L04 | Fri 2 Oct 16:30 | Mon 5 Oct 09:45 | Mon 5 Oct 10:10 |
| L05 | Mon 5 Oct 08:30 | No assignment observation by Mon 5 Oct 10:00 | Not supplied |

The rules do not say webinar attendance is a trial request. L03 has no acceptance timestamp, so the assignment SLA cannot simply be applied. L06's routing identity cannot be resolved from the supplied keys. Service-response evidence does not establish a later marketing right.

## Evidence E — message and outcome summaries

A previous, separate test cohort—not the six leads above—had 100 send attempts: 92 accepted by receiving servers, 5 rejected and 3 deferred. The dashboard reports 60 unique opens and 8 unique clicks out of those 100 attempts. Inbox placement and human-only opens were not measured. The message was promotional despite an account-related subject. No outcome attribution study exists.

A retention slide compares two different start cohorts: 100 trials starting 1 September had 28 paid accounts by day 30; 100 trials starting 1 October had 20 paid accounts by day 4 as of 5 October. Outcome definition is a paid account at the stated observation point. No matched-maturity or mix-adjusted comparison is supplied. The manager calls this “proof that the new routing hurt retention”.

## Your working output

1. Prepare a source-and-time permission map for each proposed use. Distinguish plausible evidence from final authorisation, absence and conflict.
2. Identify which records/uses require containment and which evidence the human owners need before deciding. Preserve withdrawals and ambiguity; do not invent a consent result.
3. Reconstruct the routing clock separately from response time. Explain which SLA conclusions are supported, pending or inapplicable.
4. Distinguish server acceptance, inbox placement, opens, clicks and business outcomes. Challenge the retention assertion without inventing a cause.
5. Complete the Campaign Evidence and Human Decision Record. Keep promotional email, trial service and advertising matching as separate decisions. Name review roles, with actual people left Unassigned.

Useful methods: AMO-P-000364; AMO-P-000025 for lifecycle logic, AMO-P-000220 for routing/SLA review, AMO-P-000255 for deliverability questions, AMO-P-000267 for cohort interpretation. AI cannot approve permission, overwrite a CRM record or send a message.

Do not treat higher conversion as permission to ignore restrictions. More than one proportionate investigation plan may be defensible. The separate facilitator debrief is not part of the evidence supplied here.