Platform
What an agent is allowed to do
Every workflow Kadre designs has the same six-stage shape, whatever the work is. The agent reads within its grants, acts within its rules, and stops at the boundary. A person decides. The outcome is recorded.
Six stages. One of them is a person.
Click any stage to see when it runs, the rule it follows, who owns it, and what gets recorded. The fourth stage is the boundary: nothing is sent or posted without a decision.
What each agent may do, and never does
Permissions are written per workflow before anything runs. The agent cannot widen them. Pick a workflow to see its boundary.
Illustrative example. Permissions are set per workflow and cannot be widened by the agent.
One workforce, organized like your org chart
One agent is a tool. A coordinated workforce is a capability. Every agent runs in one place, organized by team, with shared memory, approval queues, and full audit trails. The first takes weeks to stand up. Every one after is configuration, not another vendor.
How an engagement starts
The catalog, by role. Which roles a company runs, and in what order, is decided by the diagnostic, one workflow at a time.
Ask Kadre
A question in plain words, answered from the company's own records: contracts, billing, tickets, quotes. Each answer names the sources it read, and anything that would change a record goes to a person for approval.
Watch the scripted demo
Grounded in your records
Answers come from the systems the agent is granted, not from general knowledge. The sources read are shown with the answer.
Stops at the boundary
If an answer leads to an action, the action is drafted and waits for approval. Ask Kadre never sends or posts on its own.
Company-specific
What one company's agent reads and learns stays inside that company. Nothing is shared across clients.
On this site
The Ask Kadre panels on this website are scripted demonstrations with synthetic records. There is no live model behind the page.
Triggers
CRM signalsInbox and documentsDates and renewalsTicket eventsPolicy
Eligibility rulesAuthority limitsData grantsCadenceApproval
Edit, approve, rejectException routingReasons recordedWrite-back
System of recordSequences and portalsReceipts only, automatedSee a workflow drawn for your operation
Bring one recurring process. We will map it to the six stages and show where the approval sits.