---
schema_version: "1"
id: 2ca6019c4b6d1d843b7aed8938d0921cef23e080788a4f3fdef4d1cf86a7280f
title: Phase 6 — End-to-End Validation
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_day_1_validate_end_to_end_journey.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_day_1_validate_end_to_end_journey.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b8ce278184bb8d59057168d355b678dce5e953fd1c45439cfbe0647f161a02dd
description: 'Outcome: A complete, demonstrable round-trip from "employee reports a problem" to "fulfiller resolves it." This validation demonstrates that the configured components work together across one complete incident journey.'
products:
  - Service Cloud
  - Agentforce IT Service
release: "264"
---
# Phase 6 — End-to-End Validation

**Outcome:** A complete, demonstrable round-trip from "employee reports a problem" to "fulfiller resolves it." This validation demonstrates that the configured components work together across one complete incident journey.

**Owner:** Implementation Lead, with the pilot Employee and pilot Incident Fulfiller participating.

**The Day 1 happy path test**

Run these scripted scenarios in order. Don't move on if one fails.

1. Scenario A — Employee submits, fulfiller resolves
    1. Pilot Employee logs into the portal.
    2. Pilot Employee submits an incident (e.g., "Cannot access VPN").
    3. Confirm: incident appears in IT Fulfillers Queue with auto-assigned priority.
    4. The pilot fulfiller accepts the routed work or opens the assigned incident, depending on the configured routing method.
    5. The fulfiller applies and verifies the fix, records the resolution, and sets the appropriate lifecycle status.
    6. Confirm that the employee can retrieve the updated incident status or, if notifications are configured, receives the expected update.
2. **Optional:** Scenario B — Submit a Catalog Request (If Request Management Is in Scope)
    1. Pilot Employee opens the portal Service Catalog.
    2. Submits a standard service request (e.g., software access).
    3. Confirm: service request lands in the appropriate fulfillment queue.
3. **Optional:** Scenario C — Privileged employee triggers escalation (only if configured in Phase 4)
    1. A user assigned the **Privileged User** tag at access level ≥ escalation threshold submits an incident.
    2. Confirm: a banner displays on the incident record indicating prioritization.

**Validation**

- Scenario A passes. Run and validate the other scenarios only when their corresponding capabilities are included in the initial scope.
- Configured notifications are delivered through the expected channels.
- If Knowledge is in scope, at least one relevant Knowledge article—sample or customer-created—is findable from the Incident record.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-it_service-264-0-0-production-enus/0a574a10-4c7a-4681-aacf-0767f8beaad4/images/icon_important.png)

Important

**Common pitfalls**

- **No notification arrives:** Possible causes include missing notification preferences or incomplete email, Slack, or Microsoft Teams configuration.
- **Incident remains unassigned:** Possible causes include an inactive assignment rule, unmatched rule criteria, or an incorrectly configured owner.