How it works

From sign-up to answering customers.

A business connects what it already uses and tells SoRex what it knows. The routing, the takeover, the audit trail and the reply-window rules are the same for everyone.

What the agent does with a message.

Six steps, every time. Pick any step to see it, or watch it play through.

SoRex agentWorking

Example run

Four steps to live.

No script to write and no decision tree to maintain.

Step 1

Create your account

Invite your team, each with a role that decides what they can see.

Step 2

Connect your channels

Enter credentials once. They are stored encrypted and never shared between businesses.

Step 3

Teach the agent

Add knowledge, connect your data as views, and define custom tools.

Step 4

Go live

The agent answers what it can and hands over the rest, with routing and takeover built in.

What happens to a message.

Every incoming message takes the same path. Cheap checks run first, so the agent only runs when it should, and a person who has taken over is never talked over.

channel webhook→adapter→queue→dedupe→bot enabled?→taken over?→pre-filter→read receipt→identity→agent loop→persist→send

Decision	Who makes it	Why
Who the customer is	Code, not the model	Phone parsing and OTP are deterministic, so nobody can talk the agent into another account.
Whether to answer at all	A pre-filter	“ok”, “hello” and emoji get instant templated replies instead of a model call.
What something costs	Your systems	Amounts come from your data through tools. No tool takes an amount from the model.
Whether to follow up	A policy	Only after a question is resolved, and at most once a day.

The same agent, over an API.

Everything the agent can do is reachable over /v1, through the same registry and the same checks. There is no privileged back door.

# list the tools your agent can use
curl https://sorex-console.digiqulus.com/v1/tools \
  -H "X-API-Key: sa_live_..."

# run a full agent turn from your own code
curl -X POST https://sorex-console.digiqulus.com/v1/agent/run \
  -H "X-API-Key: sa_live_..." \
  -H "Content-Type: application/json" \
  -d '{"message": "where is my order?", "user_id": "..."}'

Scope	Grants
`tools:read`	List the catalog
`tools:invoke`	Call a tool
`agent:run`	Run a full agent turn
`identity:assert`	Name which customer to act for
`conversations:read`	Read threads

Ready when your channels are.

Pick a plan and start with the channels you already use.

See plans →How it works