01 / Detect
Verify what is claimed.
Three entry routes converge here: a direct partner API, a Behalf website entry point, and detection during a customer-service handoff. Identification grants no permission.
Agent entry
Resolve the company, provider, individual agent, claimed customer and ticket. A routing tag is not identity.
Resolution
Company, provider, agent instance, customer and returning relationship. A matching name or email never becomes proof.
Raw response
The exact server response, kept visible for verification.
—
02 / Protect
Authority is decided here.
Protect is the authority for customer access and the permitted action. An agent's claim, an AI model, or a ticket's security level never grants access or approves work.
Consent
The human authenticates in the company channel, sees the named agent and scopes, and approves. Representation continues until revoked, with periodic review.
Agent requests representation
Each agent has an independent purpose, scope, grant and revocation state. Selecting more scopes never combines another grant.
Hold the platform key to select more than one scope.
Human customer
The customer session is resolved on the server. The browser selection below is only a demonstration convenience.
Customer inbox
New customer (provisional registration)
Contact verification does not create an account and does not authorise an agent. Activation requires a company-signed result. A new passkey proves control of that credential, not ownership of an existing telecom account with a similar name.
Authorize
A new account change needs the human's explicit approval of the exact terms shown here, valid for at most 24 hours and executed once.
Agent proposes an exact change
The proposal freezes the operation, values and material terms. A changed price, resource or agent needs a new decision.
Behalf executes approved item
The adapter rechecks authority and terms, consumes the item once, and records the receipt. Unknown outcomes are reconciled, never blindly redispatched.
Encrypt
Application-level authenticated encryption of proposal parameters, material terms, disclosures and results. Authorization is checked before decryption.
Token generation
OAuth-style access credentials, capped at 15 minutes, bound to the agent, provider, grant and scopes. Renewal repeats every check and cannot widen permission.
Issue and renew
A grant is not a permanent bearer token. Every routine renewal rechecks identity, provider affiliation, relationship, scope, review and revocation.
Credential
03 / Resolve
Coordinate the work, not the authority.
The existing orchestrator coordinates billing, product, sales, customer-profile, communication and validation agents. Behalf AI agents may propose and coordinate, but they cannot approve for the human, override a security decision, or become the authoritative record.
Create the service ticket
A ticket is created only after the intake and consent boundary is satisfied. Ticket creation never authorizes customer access.
Related views
Behalf workbench
Tickets, runs and responses.
Agent portal
The existing external-agent intake surface.
Security API
The authoritative routes mounted at /security/v1.