Your client browses their own live site, clicks the exact element, and describes the change. It lands in your queue as a request with the screenshot, the URL, and the precise spot on the page.
Whether it came from the portal, a pinpoint on the live site, a form, or your own team, a request is one object with one path to done.
From the portal, a visual comment, a form, or an internal to-do you log yourself.
Per-client roles assign it by default: your team, your connected agent, or Agency Label.
Work comes back as a preview deploy on a branch, linked right on the request.
You or your client approve against the live preview. Nothing ships unseen.
Merged and deployed. The thread, the branch, and the history stay on the record.
We refuse to ship nested subtasks, template builders, and approval matrices. A request carries exactly what work needs and nothing more.
Every request has its own message thread, so context never scatters across email and chat.
Split a request into checklist items with assignees. No nesting, no dependencies, no ceremony.
Internal requests are your own to-dos on a client, like sending the proposal or the monthly check-in. The client never sees them.
Slice the same queue by status, client, or assignee. Views over one table, not five different systems.
Each request shows exactly who it routes to: my team, my agent, or Agency Label. Change it per request whenever you want.
The queue is where autonomy starts: connect your own agent and requests stop waiting for you.