CRM HANDOFF — WORKING COPY
Scope: Russia / Yandex Direct; language does not establish availability.
No names, contact details, credentials or conversation transcripts here.

BLANK HANDOFF CONTRACT
Journey / service / landing version: ____
Ad promise / permitted exceptions: ____
Test environment / authorised test window: ____
Audit reference / received time and time zone: ____
Submission receipt / CRM record reference: ____
Required context / observed values: ____
Owner / backup owner / next action / due time: ____
Qualification rule and version: ____
Decision: accepted / rejected / duplicate / unknown: ____
Reason / evidence reference / reviewer / decision time: ____
Duplicate rule / original record reference: ____
Order outcome: open / lost / fulfilled / cancelled: ____
Outcome evidence / observation cutoff: ____
Unknowns / person responsible for checking: ____
Defect / correction version / retest evidence: ____
Decision: pass / fail / stop; decision owner: ____

FILLED EDUCATIONAL EXAMPLE — INVENTED, NOT CLIENT RESULTS
Journey: office equipment package; landing version B.
Reference: TEST-B; time: agreed test window, Europe/Moscow.
Promise: discuss a complete workstation package.
Required context: package category; preferred reply channel.
Receipt: TEST-RECEIPT-B; CRM reference: TEST-CRM-B.
Observed: category saved, but absent from the staff notification.
Owner: sales test lead; backup: shift lead.
Decision: accepted test enquiry; not a sale.
Reason: requested service is offered; receipt is confirmed.
Next action: open the full record and confirm the requested package.
Outcome: open; no fulfilment or cancellation evidence.
Unknown: whether other notification routes lose the category.
Defect owner: CRM administrator; correction: notification version C.
Retest: category visible to the assigned employee in the new version.
Decision: fail before correction; pass only after evidenced retest.

TEST FIXTURES — EXPECTED RESULTS
VALID: submit an authorised enquiry for an offered service.
Expect receipt, linked CRM record, context, owner and next action.
INVALID: omit a required field.
Expect visible validation; no accepted business enquiry.
REPEAT: repeat the same authorised request.
Expect a documented link to the original, no second accepted result.
DIFFERENT TASK: same test contact, different legitimate request.
Expect review under the duplicate rule, not automatic deletion.
REJECTED: request a service outside the stated offer.
Expect a reason tied to the offer version; preserve receipt evidence.
UNREACHABLE: review an authorised no-response fixture.
Expect unknown/contact not established, not invented fraud.
SHIFT END: test the agreed backup handoff.
Expect a named role, due time and acknowledgement.
DELIVERY FAILURE: simulate safely in a test environment.
Expect no false success; recoverable evidence and an assigned owner.

ACCEPTANCE CHECKLIST
[ ] Promise matches what the business can provide.
[ ] Receipt is proven separately from an analytics event.
[ ] Context, owner and next action survive handoff.
[ ] Duplicate and rejection decisions have reasons and evidence.
[ ] Unknown and open outcomes remain visible.
[ ] Tests are excluded from commercial results.
[ ] Retest evidence matches the corrected version.
PASS: every applicable fixture matches its expected result.
FAIL: record a mismatch and assign its correction; do not scale.
STOP: lost valid enquiry, false promise or missing owner; pause the affected route.
RESTART: correction, repeat test and sales-owner sign-off are recorded.