Data & Integrations
Connect Liberrex to the systems you already use.
Liberrex complements the existing environment by using only the data needed for customer journeys, frontline execution and performance management.
Architecture
Liberrex complements the existing environment.
Liberrex does not need to replace existing business systems to create value. The platform can use the information required from applications already in place.
Integration scope depends on the use case: only the data needed for customer experience, execution or performance management should be connected.
Existing systems
Examples of data:
- Customers
- Products
- Organization
- Users
- Objectives
- Interactions
Integration
According to the environment available:
- APIs
- Structured files
- Database
- Scheduled synchronization
Liberrex
Data feeds the capabilities required:
- Customer Experience
- Workforce Experience
- Customer Intelligence & Engagement
- AI & Agents
Integration methods
Choose the integration method that fits the environment.
Not every organization has the same information system. Liberrex can adapt to several exchange models, according to technical constraints and the level of synchronization required.
APIs
Connect systems that expose suitable application interfaces.
Files
Exchange structured data when APIs are not available.
Database
Use a controlled data source when the client architecture allows it.
Scheduled synchronization
Refresh data on an agreed frequency rather than assuming every connection is real-time.
Data context
Different product families use data differently.
Each family uses the data required for its operating problem. Access remains governed through roles, permissions and organizational structures.
Customer Experience
Uses the data required for the journey and the service interaction.
- Customer visits
- Appointments
- Service context
- Feedback
Workforce Experience
Uses organizational and execution data to turn priorities into action.
- Organization
- Objectives
- Campaigns
- Performance
Customer Intelligence & Engagement
Uses customer and operational data to support commercial insight.
- Customer attributes
- Products
- Interactions
- Opportunities
AI & Agents
Uses approved knowledge and supported operational context in assisted workflows.
- Approved knowledge
- Conversation context
- Supported operational data
Governance
Connect data without losing organizational control.
Access to information should stay consistent with each person’s responsibilities. Users see and use only the data required for their role and perimeter.
Roles
Define the responsibilities and capabilities of each type of user.
Permissions
Limit actions and information according to the user’s profile.
Organizational visibility
Apply the network perimeter that corresponds to the user’s function.
Controlled access
Keep control over the information exposed across the different applications.
Implementation approach
Start with the data required for the first use case.
There is no need to integrate the entire information system on day one. Connect what the first operating model needs, then expand if necessary.
01
Define the use case
02
Identify the data required
03
Identify the source systems
04
Connect
05
Validate
06
Expand if necessary
FAQ
Questions about data and integrations
Does Liberrex require replacement of our existing systems?
No. Liberrex is not a core banking, core insurance or CRM replacement. It is designed to sit alongside existing enterprise systems and connect customer-facing operations to those systems where interfaces are available.
What integration methods can Liberrex support?
Liberrex can connect through APIs and other integration mechanisms supported by each deployment. The method used depends on the systems and interfaces available in the organization.
Can Liberrex connect to different systems across different customers?
Yes. Integration scope is defined per organization. Depending on the project, this may include customer, operational, CRM, core-business or communication data sources.
Does every use case require real-time data?
No. Some journeys need timely operational context; others can run on agreed update cycles. The integration pattern is chosen for the use case rather than assumed to be real-time.
Can the integration scope grow over time?
Yes. A first use case can start with the data required to operate, then expand as additional families, locations or workflows are validated.
How are roles and data visibility managed?
Access is governed through roles, permissions, organizational structures and access control on the shared foundation. Users see the context required for their role, not every record in the environment.
Discuss your integration environment.
Map the systems, interfaces and data needed for the first Liberrex use case.