What would a generated utility connection case contain?

A retail energy provider approves connection request `REQ-4410` for a small commercial customer. The sales team has recorded the approval and chosen tariff `TAR-BIZ-2`.

The generated case contains:

- The approval record with tariff, start date and approver role. - A customer record `CUST-2086` with a trading name and a registered name that differ slightly. - A candidate service point `SP-90417` from the network lookup, whose address uses a unit number the application omitted. - A policy extract: connections with an address mismatch need a manual confirmation task before billing starts. - A billing profile template and a welcome notice template.

The set-up officer, played by the agent, should link the existing customer, attach `SP-90417` only after confirming the address match, create a confirmation task for the field coordination team, and leave billing in `draft` until that task closes.

The expected end state lists each record and status: customer linked, service point attached, billing `draft`, one open task, no welcome notice sent.

**What it teaches**

- Policy text decides the outcome, not the approval alone. - Near-matches are as important as exact matches. - Sending a notice early is a state change with a customer-facing consequence.