Skip to content
Revactio

By Getelis Ltd

← Integrations

Developer

This platform owns the commercial layer, not the runtime.

Agent identity, execution, tool permissions, generic approvals and audit belong to the agent platform underneath. This one owns the commercial part: sales objectives, playbooks, commercial context, engagement channels, authority and outcomes. The separation is deliberate and it is worth understanding before you build on it.

Start engaging

What connects

The agent runtime and its permission layer, connected as the execution environment.

What crosses the boundary

  • Into the platform: agent identity, run records, tool call outcomes and approval decisions.
  • Out of the platform: sales objectives, commercial context, authority limits and engagement instructions.
  • Never: credentials. Those are held by the runtime's vault and never enter an agent's context.

What this makes possible

  • Gives each sales agent its own identity, so every action is attributable
  • Enforces tool permissions and generic approvals outside the model
  • Provides the audit record of what an agent did and under which version

Setting it up

  1. 1Connect the runtime and confirm the workspace.
  2. 2Define a sales agent here; review its identity and permissions there.
  3. 3Confirm the commercial authority ladder.
  4. 4Deploy once both the commercial limits and the tool permissions are right.

Permissions

The sales layer requests the specific capabilities an agent needs and nothing more. It cannot widen its own permissions, grant itself a tool, or approve its own requests.

Where it stops

This platform deliberately does not reimplement agent identity, runtime, generic permissions, tool authorisation or agent audit. That means some questions about an agent belong to the runtime rather than here, and the pages say which. It also means a commercial authority limit set here is enforced in addition to the runtime's permissions, not instead of them — both have to pass.

Developer

Others in this category.

Events and webhooksTrigger a motion from your systems. Receive what happened.

Make sure every opportunity gets a next action.

Let AI handle the repetitive engagement, keep follow-up moving, and bring your team in when a customer needs a real conversation.

Start engaging See a revenue motion

Agents identify themselves on every call · Nothing commits without you · [email protected]