INTEGRATIONS

Connect the work.
Keep the systems you know.

Explore the information that moves into and out of a Briano workflow, then scope the connection around your operation.

Discuss your systems Read the API documentation

FOLLOW THE INFORMATION

One connection.
A clearer path.

Choose a route to see what moves, where it goes, and what to confirm.

INFORMATION INWeb or app

Customer messages, locale and conversation reference.

briano

CX Agent

Context · configured actions · insight
INFORMATION OUTConversation thread

Assistant responses and the conversation history.

Documented API

Web and in-app conversations

Bring a Briano conversation into an existing digital experience.

WHAT TO CONFIRM

The public Chat API documents thread creation, messaging, response streaming and history retrieval. Confirm authentication and delivery details with Briano.

Read the Chat API

Illustrative information flow. Availability and permissions depend on your agreed deployment.

CONNECTION DIRECTORY

Choose a starting point.

Connection status distinguishes public documentation, a published customer implementation and connections to scope together. These are connection patterns, not a list of universally available native connectors.

6 connections

Documented API

Channels · CX Agent

Web and in-app conversations

Bring a Briano conversation into an existing digital experience.

Information in
Customer messages, locale and conversation reference.
Information out
Assistant responses and the conversation history.
What to confirm

The public Chat API documents thread creation, messaging, response streaming and history retrieval. Confirm authentication and delivery details with Briano.

Read the Chat API
Customer implementation

Operational systems · ClaimPilot

Claims system connection

Move structured document data into an existing claims workflow.

Information in
Claim documents and existing data used for validation.
Information out
Structured claim information delivered to the existing system.
What to confirm

GPI’s published story describes an API integration. Each new system, field mapping and exception route requires its own scope.

See the GPI implementation
Scope with the team

Knowledge · CX Agent · ClaimPilot

Policies and service knowledge

Ground the workflow in the information your team approves.

Information in
Policy documents, FAQs, service content and internal guidance.
Information out
Workflow context for answers, information collection and configured checks.
What to confirm

Agree sources, access rights, ownership, update frequency and how conflicting content is reviewed.

Discuss your knowledge sources
Scope with the team

Operational systems · CX Agent

CRM and support handoff

Carry the customer’s context to the people taking over.

Information in
Permitted customer and case context from connected systems.
Information out
A request and conversation context for the receiving team.
What to confirm

Confirm the specific CRM or ticketing system, read and write permissions, routing rules and handoff experience. No universal native connector is implied.

Map your support workflow
Scope with the team

Channels · CX Agent · Pulse

Voice and conversation data

Connect voice service and conversation review to your operation.

Information in
Authorized calls, chat records and the context approved for analysis.
Information out
Customer support or conversation insights, depending on the product.
What to confirm

Validate the provider, consent process, recording access, language coverage and handoff behavior for your setup.

Review your channels
Scope with the team

Reporting · Pulse

Analytics and BI exports

Bring service insights into the reporting your team already uses.

Information in
Connected conversation data and agreed quality criteria.
Information out
Structured analytics for internal dashboards and reporting.
What to confirm

Agree export fields, delivery method, refresh schedule and access controls with Briano and your reporting owner.

Explore Pulse reporting

PLAN THE CONNECTION

A useful integration
starts with five answers.

Bring your system owner into the conversation early.

Get the integration checklist
  1. Which system holds the information?
  2. Which fields and actions are permitted?
  3. How will access be authenticated?
  4. What happens when data is missing or a connection fails?
  5. Who owns testing, monitoring and ongoing updates?

HELPFUL BY DESIGN

Your operation.
A connected next step.

Tell us the workflow and systems you want to connect.

Talk to the team Explore the demos

Stay connected.