A customer response with human review.

1. Add the sample sources

Attach the supplied synthetic project record and customer request. The requested delivery is pending until a reviewer approves it.

2. Define the preparation step

In Process Builder, define the request and source records as process input. Add an agent step that prepares a response from those inputs.

Using only PROJECT-001 and REQUEST-001, prepare a concise customer response. State the committed delivery date, the requested delivery date, the project milestone and their relationship. Cite the source identifiers. The requested change is pending; do not describe it as approved. Mark information not supplied instead of inventing it.

Include the committed and requested dates, project review date, approval status and supporting sources alongside the response.

3. Add human review

Require approval before the response is treated as accepted. Give the reviewer the draft response, the source records and the pending status of the requested delivery change. The review includes a comment field and Approve and Reject choices.

This example stops at a reviewed response. It does not connect a send-message tool or update a customer system.

4. Test both paths

Approved

The response is accepted for the example. If a separate date-change approval is modeled, record that decision explicitly before changing the commitment.

Rejected

The proposed response is not accepted. Inspect the recorded decision and the configured rejection path.

In both paths, confirm that no customer message is sent.

5. Add a Quality Lab case

Use the same fixed input and source set. Check the expected dates, approval status and supporting sources.

Current commitment

15 October 2026

Requested delivery

22 October 2026

Project review

24 October 2026

Change approval

Pending

Sources

Project record and customer request

{
  "committedDelivery": "2026-10-15",
  "requestedDelivery": "2026-10-22",
  "milestoneDate": "2026-10-24",
  "approvalStatus": "pending",
  "sourceIds": [
    "PROJECT-001",
    "REQUEST-001"
  ]
}

Check the date fields and pending approval status against their exact values. Check the supporting source references using the available checks.

Review the explanation manually for unsupported assumptions and whether the cited source actually supports the claim. Matching individual values does not prove that the response is correct.

6. Inspect the run

Review the execution record, approval and final result. Return to the source records when checking the explanation.

Example response before approval

The current delivery commitment is 15 October 2026. The requested date, 22 October 2026, is still pending approval. It is two calendar days before the project acceptance review on 24 October 2026. The supplied project record requires the material to be available before that review; it supplies no other scheduling constraints, so this does not establish that every delivery risk is resolved. [PROJECT-001; REQUEST-001]

No customer message is sent by this example.