Most "AI for business processes" stories are about agents using software that a developer already built for them — filling in a form here, summarizing a record there. This one is about an agent that had nothing to start with — no account, no object model, no form — and ended it with a real employee, on a real phone, submitting a branded damage report that same afternoon. Every step in between was the agent's own work.
Telesherpa is an ontology-based platform with roots in field-service management. Its premise is that most operational software is the same handful of moving parts — typed objects, forms, documents, notifications, mobile access — reconfigured per industry rather than rebuilt. Car rental is one such vertical, and everything from reservation to a vehicle damage report is fair game as a first workflow.
The part worth dwelling on isn't the workflow. It's that nothing above needed a human to exist first — not the account that built it, not the objects it operates on, not the form, not the document.
register() creates the account, activate() redeems the seven-digit code in its inbox, login() exchanges client credentials for a bearer token. auth_status says plainly whether the token is valid and how much of the platform is visible. None of this happened in a browser, and none of it was a service account handed down by IT — the agent onboarded itself.
A form needs something to be a form about. Before "damage report" could be a set of fields a renter fills in, it had to be a typed object in the ontology — property definitions and an object type, living in a scope for this customer's car-rental vertical. That model didn't pre-exist; the agent built it, the same way it later built the form. There's no seam between "defining what a damage report is" and "defining what filling one out looks like" — both are the same agent, the same kind of tool call, one layer apart.
onto_formdef_save) defines every field, widget and dropdown option against the object type the agent just created.##key## placeholders, iterated conversationally, revised against feedback, wired in.buttons property turns a submission into an email with the generated PDF attached.
It also found the template mechanism wasn't documented anywhere, and filed a service request rather than quietly relying on undocumented behavior — the same instinct that makes write access to your object model and forms trustworthy in the first place.
Not a deploy — a real person on a real phone, opening the PWA, filling out the exact form the agent had just defined on an object type that, an hour earlier, hadn't existed, photographing a scratch, and hitting send. The photo landed inside the generated PDF automatically. The moment the object model, form and document were saved, they were live on every phone an employee already carries.
Strip away the specifics and the pattern is: account → object model → form → branded document → mobile access, every layer expressed as MCP tool calls an agent can run from a conversation. The claim worth sitting with isn't "AI can fill out your forms" or even "build your forms" — it's that a customer's own agent can stand up an entire new piece of their business, data model included, in an afternoon, and staff can be using it before that afternoon is over.