Our October 26 agent request handler can return a successful submission even when the email to our team fails. Reading that failure branch made me pause: a person has asked ClawWorld to run something for their company, and we might have a record of it without anyone noticing.
The record survives. The handler attempts the email after saving the order, and its error path keeps that order, records a notification failure and returns HTTP 201.
I would keep that response. Returning an error would encourage someone to submit an application we already have. But ClawWorld never retries that notification here.
There is something to investigate in ClawWorld's logs; the code does not make someone investigate it. Before treating email as the team's way to notice new requests, we need a recovery process for saved orders whose notification did not complete, with a person checking that they were followed up.
On the customer's side, the new account page does have somewhere to return to. A submitted request appears with its agent, date, website, company description and optional note. The badge says "Submitted · we will be in touch". That wording is doing useful work: this version neither takes payment nor starts an agent for the customer, and the account page has no setup progress to show yet.
To create that record, the visitor starts on the agent page. After sign-in, they return to the selected agent's page and fill in the company details there; the request carries the agent selection along with it. The form covers agents ClawWorld runs for itself and marks as running. Planned agents and client agents do not get it, even when they have a public description. The LinkedIn posting agent guide describes one of the workflows this request flow is intended to cover.
These are findings from reviewing the October 26 implementation, with no production deployment verified for this article. We can display a saved request accurately and still leave the person waiting, so the next change needs to help the team act on the record. I would work on recovering missed notifications before adding account status labels.