Workflow

Session-bound relay flow

A relay session replaces the direct path.

Managed handoff in, managed handoff out.

XRelayPro starts with a controlled session model: create the session, distribute the session ID out of band, route text and voice through a relay surface, then wipe the path when the interaction is complete.

Review trust model Compare deployment modes

Bootstrap

Shared session ID plus PIN-derived context.

Bridge

Text lane -> relay surface -> voice lane -> return path.

Closeout

Wipe-capable session end with explicit retention policy.

Session bootstrapText ↔ voice bridgeHuman or AI relay surfaceWipe-capable closeout

Six-step launch flow

From session creation to wipe in six operational steps.

Session creation

Party A creates a relay session, receives a session identifier plus PIN, and shares the session identifier out of band.

Shared transform context

Both endpoints work inside the same VLS transform context so the relay surface receives only transformed relay material.

Relay intake

The operator or isolated relay node receives Party A text, prepares the correct voice output, and preserves directionality.

Voice bridge

Party B hears the transformed voice path, responds over the voice surface, and the relay node converts it back into the return text lane.

Return delivery

Party A receives the return text path inside the same relay session without ever exposing a direct endpoint connection.

Session close and wipe

Operators end the session, trigger wipe rules, and clear residual state according to the selected retention policy.

Relay surfaces

Three surfaces, one controlled session boundary.

Party A surface

Text input, session controls, PIN-derived context, and return message feed.

Relay surface

Operator dashboard or AI node for voice/text transformation, routing, and wipe execution.

Party B surface

Voice-only reception and reply path through phone, VoIP, or controlled audio bridge.

Deployment modes

Choose the relay surface that matches the operational reality.

The same session logic can run through human relay operators, isolated AI relay boxes, or chained relay nodes depending on throughput, trust, and endpoint separation requirements.

MVP coverage

Human relay operator

One operator relays a single active session with the fastest path to field validation and UX learning.

Scaled coverage

Air-gapped AI relay node

A local isolated model translates between text and voice lanes without cloud APIs or internet dependency.

Endpoint separation

Multi-hop relay chain

Three-hop topology reduces endpoint correlation by ensuring no single relay sees the full path.

Workflow briefing

Need the full operator flow mapped against your communication environment?

We can scope the exact session path, relay mode, and endpoint handling model before you commit to deployment architecture.

Session lifecycle review Human vs isolated AI comparison Multi-hop expansion path