One table per workflow
The quarterly-close table shows every run in the process, its state, and its owner. Your manager doesn't ask for a status update. The table is the status.
For operations teams
Long-running agent work, with oversight your auditors accept
Research sweeps, close processes, vendor reviews, support escalations. Agents now run the workflows your business depends on. Handbell gives the whole team one live view, with approvals and a full record built in.
The shape of the problem
The workflow runs for three days. Who's watching on day two?
Business-side agent runs outlive meetings, shifts, and attention spans. When they live in one person's chat window, oversight is an accident. Handbell makes it structural.
The agent rings you
When a run reaches a decision it can't own, like a payment or an external send, it rings the teammate who holds that permission. Approve, redirect, or stop, right there.
An audit trail by default
Every action, approval, and hand-off is attributed and timestamped. When compliance asks who authorized this, the answer is one click, not one archaeology project.
Roles, made visible
Who holds what
Each teammate holds specific permissions: payments, customer data, external comms. The agent can see who holds what, and so can everyone else. Delegation without diffusion. The run is shared; the responsibility is named.
Vacation coverage stops being a forwarding rule. Hand off the whole scope in one step, cleanly, with a record, and take it back on return.
vendor-review · the team
dana · holds: contracts, external-send
arun · holds: payments <$10k
kelly · holds: customer-data · steering
agent · holds: nothing it can't show you