Client Requests / CR-40118-2 Operator A
Prototype control. Customer’s situation:

CR-40118-2 — Connect a domain

Northroad Pottery · env-40118 (Production) · opened 20 Sep, 09:14  Typed request — no domain type exists today

What the customer told us

Proposed — today a request carries a free-text title only
Domainnorthroadpottery.example
Targetenv-40118 · Production · env-40118.hostingdemo.invalid
Serve, or redirect?Serve this site at that name (the portal’s other option, Web forwarding, is a redirect — different thing)
Where DNS is managed
Mail live on this domain

Those last two answers are the whole reason this request can be worked without a phone call. They are also the two the current free-text form cannot capture.

Mail continuity checkpoint

Proposed — nothing like this exists Not started

Hostnames on env-40118

This control exists today

Hostnames this environment answers to. The internal address is always on and cannot be turned off until a customer hostname becomes the Server Name.

Jobs raised by this request

Jobs exist today Linking them to a request does not
No jobs yet.

Request status

Open / In progress / Resolved / Rejected, set inline
Current: In progress

The four statuses describe the operator’s handling of a ticket. They do not describe whether the customer’s domain resolves or their mail survived. In this proposal the customer-visible states are emitted by the work itself — adding the hostname, the certificate result, the resolution check, the mail comparison — so an operator is not asked to maintain a second, parallel story.

What the customer can see right now