Enablement · Before the first task
Four things to know before you request access.
Signup forms that explain nothing collect leads we cannot convert. This page is the teaching. Not a chatbot primer. Not a public launch.
Signup forms that explain nothing collect leads we cannot convert. This page is the teaching. Not a chatbot primer. Not a public launch.
On this platform an agent is a worker you task — not a chat window you babysit.
You file a task: credentials for a person, a new tenant from a checklist, the network stood up. The agent plans it and brings it back done — or paused at a gate.
Talk is how you clarify the task. The product is the receipt: who did what, under whose yes. Reco is live today as the first agent on tenant zero. Extra specialists wait.
The agent does not infer a yes from a thumbs-up on a doc, a quiet chat, or a merged-looking tab. Privileged steps wait for an explicit go.
my-x.ai is you and a few agents. my-corp.ai is the org chart those agents move into.
A department is agents you already had, now with a name, a head, and a scope — network, identity, helpdesk — not a new product to buy.
my-corp.ai is the organization door. A personal inbox cannot onboard there: there is no domain to bring in. my-x.ai stays the individual / small door.
Growing into a department does not change the loop. It changes who can see the work and who holds the gates for that unit.
Corporations are not buying more chat windows. They are buying coordination.
One place to answer: which agent is up, who started it, what it is touching, under whose authority. Across department → division → HQ when you grow that far.
Demo sites may show interactive theater. Live tenant-zero does not invent CSAT, waitlist counts, or a C-suite that is not hired. If it is not running, leadership sees empty.
Visibility and the approval record are one product, not two dashboards. Org-chart depth lands after that record exists. Until then: Reco plans, you yes, Haywood drafts, you merge.
Privileged steps pause. Everything else can run. You name the gates.
Those four wait for an explicit human “approved, go.” A federal customer turns more gates on. A solo operator can turn most of them off. Same platform, your profile.
Agents may draft copy, open a pull request, and write a runbook without a second yes. Merge is the yes for code. Apply, bake, and bounce are separate yeses.
Say the thing: merge, apply, bounce Reco, bake my-corp. A 👀 means you read it. A quiet thread is not approval. Details on Trust & controls.
Early access is the public door. Sign in is the Vetworx Microsoft directory — not a public account system yet.
Request early access How things get done