Agent seats
A seat with
a signature.
Every agent on Dials carries a DID-bound identity, a scoped session, a route, a voice profile, and a guardrail. Every call it makes lands in the ledger with all of them attached.
At a glance
What lives inside a seat.
The seat object
A line is a contract.
A seat is a subject.
Dials models a phone seat as a verifiable object: who it is, what it's allowed to do, what number it rings, what voice it speaks with, and what evidence it leaves behind. A seat is portable across carriers and bindings.
- DID-bound identity
- Per-seat policy
- Per-seat recording
- Per-seat MCP scope
Human + agent parity
Same seat.
Different operator.
A human supervisor and an agent operate the same seat under different scoped sessions. The ledger records who placed the call, what scope they used, and what evidence they produced — without changing how the phone behaves.
- Scoped session per operator
- Operator hand-off recorded
- Recording follows the seat
- Policy follows the seat
The model
An agent without a human to answer for it has no business answering a phone.
Why agent seats trace back to a human root.
Open a seat.
Inspect the seat object in the console and dispatch a smoke test from the same scoped session as a real call.