Integrations
Qliva can retrieve live data from the systems behind your operations and use it directly in the conversation – or take the next step when the integration supports it.
Order status, prices, availability, invoices, CRM, and other operational data – without making the customer leave the conversation.
Live data & actions
Some questions can be answered from documents and websites. Others need information that changes constantly. Qliva can then retrieve the answer directly from the right system.
Your order was dispatched today and is expected to arrive on Tuesday.
databaseCurrent information usedYes, there are two options for four people next weekend. The least expensive costs SEK 8,950.
event_availableAvailability and price usedThe invoice has been found and can be sent to the customer.
ruleThe exact action depends on the integrationThe sales team receives the contact details, requirements, and context from the conversation.
person_addLead created in CRMThe examples show typical flows. Available information and possible actions depend on the system and how the integration is configured.
Two capabilities
ReadCurrent information when the question is asked.
Qliva can retrieve information that changes over time and use it directly in the answer.
ActWhen the next step needs to happen in a system.
When the integration supports it, Qliva can also create or transfer information so that the conversation moves forward.
Actions always depend on what each integration permits and how it is configured.
E-commerce & orders
Order questions are often simple for the customer but require current information from the underlying systems.
Qliva can identify the order reference, retrieve the relevant status, and use it directly in the answer.
Order changes, cancellations, and refunds are not performed automatically unless a specific integration explicitly supports and permits them.Booking
In booking-led businesses, static website content is not enough. Price and availability need to be retrieved when the question is asked.
How much is a flight to London on Friday?
Duffel →We need 12 forklifts for a new warehouse and would like a quote.
Requirement12 forklifts · indoor warehouse
Contact detailsAnna · Nordlager AB
SummaryConversation context included
CRM & sales
When a customer shows purchase intent, Qliva can collect the right information and transfer the context to the CRM or sales team.
Lead creation in Lime and UpSales is supported when the respective CRM integration is configured.
Finance
Invoices, payment information, and other finance-related questions often need to be checked against the company's systems.
Fortnox is shown as a system example. Automated payments, credit notes, or bookkeeping are not promised.The Qliva platform
A system connection can be used across several parts of Qliva, depending on how the solution is configured.
“Where is my order?”
“My order has not arrived.”
New connections
Qliva is designed to connect to new APIs and data sources when the business needs it.
We start with the question you want to answer or the process you want to simplify – and then connect Qliva to the right system.
Scope and possibilities are assessed based on the system, the data, and the specific use case.“Can the customer see their current service history?”
Technical foundation
Qliva can integrate with external systems through APIs and structured data sources. How the integration is built depends on the system and the use case.
Control
Integrations can give Qliva access to current operational data. Each connection should therefore be clearly limited to what is needed.
Retrieve only the information needed for the specific use case.
Decide which actions may run automatically and which require human review.
See what Qliva retrieved, used, and did in connection with the conversation or case.
If information cannot be retrieved, Qliva can say so or hand over according to the configuration.
Get started
Tell us which system holds the information and what the customer or employee needs to be able to do. We will help you assess how Qliva can connect.
Start with one concrete use case – not a large integration project.