Live prototype Governed decisioning

Every route
has a reason.

Configure the available team, publish a versioned routing policy, and see exactly why every lead landed where it did.

Reproducible by designSame lead + policy + agent snapshot = same decision
About this demo

How the routing proof of concept works.

RAIFE turns a defined set of agent availability and routing rules into a versioned, reproducible decision—so every simulated lead assignment has a visible reason.

  1. 01
    Configure the agent snapshot

    Set availability, capacity, territories, capabilities, and languages.

  2. 02
    Publish an explicit policy

    Active requirements and preferences are saved together as a new policy version.

  3. 03
    Resolve fictional test leads

    The engine filters, scores, and selects an agent, then records the explanation trace.

How information is used

Information entered here is sent to this demo's Firebase backend when you select Save & route. Policy versions and routing decision records may persist across sessions.

Use fictional information only

This is a proof of concept, not a live production service. Do not upload real leads or personal, confidential, customer, health, financial, or other sensitive information.

Routing vault / 01

Who can receive a lead?

3of 4 agents available
MC
Available
Territory
Capabilities
Languages
TB
Available
Territory
Capabilities
Languages
PS
Available
Territory
Capabilities
Languages
JK
Unavailable
Territory
Capabilities
Languages