RatioCore Book a demo
RatioCore
Book a demo

Build with RatioCore

Reinvent your own function with agents.

The applications already on RatioCore were built from the same parts you get: how work starts, the steps it follows, the systems agents can touch, the limits they work within and the people accountable for decisions. Use them to reinvent any process in your business.

Dialogs in your channels

Design it once. Use it where your people are.

This access request was built with the dialog builder and is shown here in WhatsApp. The same dialog can run in other channels you approve, such as Microsoft Teams or Telegram, with the approval step built in.

How to build

From process to application.

  1. Pick one outcome

    Start with one business outcome. Decide which steps follow fixed rules, where context calls for an agent and which decisions belong to a person.

  2. Design the intake

    Use the dialogue builder to choose what to ask, branch on the answers and capture the evidence the next step needs.

  3. Map the workflow

    Use the visual workflow builder to lay out decisions, agent tasks, approvals and system actions.

  4. Set the boundaries

    Connect documents, channels, APIs or approved tools. Define role permissions, approval thresholds and the actions allowed for this process.

  5. Pilot, then widen

    Agree on the source data, a target system and one observable outcome. Test a permitted action, a denied action and an exception.

The builders

Design how work starts. Decide how it runs.

Use the dialogue builder for the steps people see and the visual workflow builder for the steps the business needs. Specialist agents and approved tools do the work in between.

Dialogue builder

Choose what to ask, branch on the answers and capture the details and evidence the next step needs. Start from an approved channel or a guided interface.

  • Questions that branch on answers
  • Evidence captured at intake
  • Approved channel or guided interface

Access request: which system, which role, when access should expire.

Visual workflow builder

Map decisions, agent tasks, approvals and system actions. Fixed rules control routing; agents gather evidence or recommend a next step.

  • Fixed rules control routing
  • Approval steps inside the flow
  • Outcome recorded for audit

Check eligibility, route to the system owner, grant time-limited access.

Agents and tools

Give specialist agents a clear job and connect native, API or MCP tools. Policy and role permissions govern what each one can run.

  • One clear job per agent
  • Native, API and MCP tools
  • Approval thresholds per process

Invoice exception: an agent pulls evidence from invoice and purchase order.

Your processes, the same pattern

Build around the way your teams work.

These are illustrative designs. Start with a guided service, add agents where the work calls for judgment, or start a workflow from a system event.

TRIGGER · An employee asks for system access

Employee access requests

  1. Collect system, role, expiry
  2. Check eligibility
  3. Route to system owner
  4. Grant through identity connector

Decision owner: System owner

TRIGGER · Invoice and purchase order disagree

Invoice exceptions

  1. System event starts workflow
  2. Agent pulls both records
  3. Finance reviews the discrepancy
  4. Approved adjustment sent back

Decision owner: Finance reviewer

TRIGGER · A technician records a fault

Maintenance dispatch

  1. Fault evidence attached
  2. Urgent cases routed
  3. Duty lead approves dispatch
  4. Work order created

Decision owner: Duty lead

Illustrative workflows. Your own triggers, steps and owners are configured per application.

What every build inherits

New application. Same controls.

01

Policy rechecked at execution

After a request is approved, RatioCore checks policy again at execution and records the result from the configured system.

02

Named approvers for exceptions

Route exceptions and sensitive actions to the person authorized to decide. Missing authority blocks the tool call.

03

Tools scoped to the process

Connect the documents, channels, APIs and tools this workflow needs, and define the actions allowed for this process.

04

Placement per workload

Place data, inference and connected systems according to each workload's requirements.

FAQ

Building questions.

Still deciding? Bring your questions to a walkthrough.

Can an application run without a conversation?

Yes. A workflow can start from a system event, such as an invoice and purchase order that disagree. Use the dialogue builder for the steps people see and the visual workflow builder for everything else.

When should a step use an agent instead of a rule?

Use fixed rules for predictable routing. Use an agent where context or judgment is needed, such as gathering evidence or recommending a next step. Decisions with business consequences can stay with a named person.

How do we start without a large project?

Start with a pilot you can verify. Agree on the source data, the target system and one observable outcome. Test a permitted action, a denied action and an exception before widening the scope.

See it on your business

Which function would you reinvent first?

Bring a process your team runs today. In a demo we show how agents could run it, where your people stay in charge, and what a focused pilot could prove.

See it on your workflowBook a demo