ALL PRODUCTS
rAgent / AI AGENTSP—01

Answers, actions and follow-through — from your own knowledge

rAgent is an AI agent layer for customers, partners and teams. It works with your knowledge, communicates across channels and completes workflow steps in your systems — not a chatbot that stops at the answer.

Try rAgentSee integrations
FIG. 05
AGENTIC LAYER
03 INPUTS → 01 LOOP → 04 RECIPIENTS
KNOWLEDGE · CHANNELS · ACTIONS
KNOWLEDGE
COMMUNICATION
WORKFLOWS
CUSTOMERS
PARTNERS
TEAMS
SYSTEMS
rAgent
UNDERSTAND · DECIDE · ACT
03 INPUTS ↓
RECIPIENTS ↓
01 / WHAT YOU CAN DO

What you can do with it

C—01
Customer & support assistance

Resolve customer questions from your knowledge base and account context, and escalate with the full conversation when a person is needed.

C—02
Knowledge & search

Contextual search across documents and internal systems for the people who answer questions all day.

C—03
Sales & onboarding

Guide enquiries and onboarding journeys, collect what is needed and hand over to the right workflow.

C—04
Workflow automation

Trigger and complete multi-step processes across systems, with agent actions where they are appropriate.

02 / ONE USE CASE

A withdrawal question answered with context — and routed when action is needed

01INPUT

A client asks in web chat why a withdrawal has not arrived.

02WHAT HAPPENS

rAgent checks the withdrawal status in the account system, finds the matching explanation in the knowledge base, replies with the status and expected timing, and opens a ticket for the payments team if the transaction is stuck.

03OUTCOME

The client gets an answer with context. If the withdrawal needs a person, the payments team gets a case with the conversation attached — rAgent routes it; it does not fix the payment.

04WHAT IT NEEDS

Account status through rPAM or your CRM API; a knowledge base connected to rAgent.

EXAMPLE SCENARIOAn illustrative operator flow, not a customer case study.
03 / HOW IT FITS

How it fits with what you run

rAgent takes in knowledge sources and account context, and puts out answers, tickets and workflow actions. It needs at least one knowledge source; everything else is optional.

Knowledge sources

Documents and internal systems, connected through API or import.

CRM & helpdesk

Customer context in; tickets and cases out.

rPAM

Account and lifecycle context for every conversation — native.

rWeb

The assistant inside your portal and website — native.

■ AI■ INFRASTRUCTURE■ EXPERIENCE▢ YOUR STACK
How integration works
04 / START WITH A WORKING DEMO

Start with a working rAgent demo

The demo is a working assistant on your own knowledge: connect a source, set behaviour and channels, test it in a real conversation.

YOU GET

A working rAgent environment for your company.

YOU CONFIGURE

Knowledge sources, assistant behaviour and tone, channels, permissions.

CARRIES INTO PRODUCTION

Your configuration and connected sources when production is activated.

YOU NEED

A business email and company details. Connecting your own systems needs API access.

Same process for every product — how it worksTry rAgent