Trusted by — among others
Connect your request handling system with sales platforms, shipping carriers, and your CRM. With Debesis integrations, your agent sees order history, shipment status, and customer data in a single window – without switching between systems.
Two-way communication between systems, lead updates and edits directly from the ticket.
Two-way integration with orders, shipment statuses, and event history from all connected marketplaces.
Order import and updates, access to customer data, payments, and fulfillment statuses directly from the ticket.
Access to order list, status history, events, and inventory – ideal support for customer service in online stores.
Manage shipments, labels, courier pickups, and return codes – track statuses directly in the request handling system.
Two-way CRM integration: leads, accounts, and sales opportunities linked directly to tickets in the ticketing system. The agent sees the contact history and Salesforce activity status in a single window.
Generate waybills and pickup protocols, and view shipment history – all from within the Debesis panel.
The integration between the request handling system and BaseLinker lets you manage
tickets and see, in one place, the customer's orders from connected sales platforms
along with shipment tracking information sent by shipping carriers.
Thanks to the integration of our system with BaseLinker, order handling and the related
tickets happen on a single platform. This means faster case resolution,
shorter wait times for customers, and higher customer satisfaction.
The integration works by generating an API token in the BaseLinker panel. In the Debesis
integration module, you select the integration type, paste the copied API token, and define
the integration scope.
In our ticketing system we identify the customer by phone number or email address.
The integration between the ticketing system and BaseLinker lets you display the customer's orders
in real time directly in the ticketing system through an additional widget.
From within a ticket, you can access the order list and details such as order date,
shipping and payer information, ordered products, and payment method. The system also displays
the list of order events (order edits, status changes) along with shipment statuses
such as handed over to courier, out for delivery, and delivered.
The Debesis ticketing system integrates with Bitrix24 via API. The integration supports
updating an existing lead in Bitrix24 and assumes two-way
communication between Bitrix24 and the Debesis ticketing system.
The update process works as follows:
– a record is sent to the Debesis ticketing system,
– a ticket is created in the Debesis system,
– the ticket is assigned to an agent,
– the agent performs the required actions,
– the lead status in Bitrix24 changes based on the ticket status update.
Further processing of the ticket can also update previously sent data.
You can also integrate the Debesis phone system with Bitrix24.
SIP accounts are configured in the CRM, and inbound and outbound
calls are routed through them.
InPost integration configuration is available from the Debesis ticketing system
admin panel. The integration scope covers what data will be pulled from InPost
(courier availability/booking, shipment tracking, label and pickup protocol generation,
inbound shipment handling). Configuration involves filling in
sender data and shipment templates.
The InPost integration supports testing in a sandbox environment.
The InPost integration enables shipment management:
– sending multiple shipments at once,
– printing address labels and pickup protocols for previously declared shipments,
– calling a courier to pick up the prepared parcels,
– canceling pickup orders.
The integration of our database with InPost's databases allows return codes to be configured.
A return code is generated after providing a phone number, email address, and indicating
which outgoing shipment the code should be created for. Generating a return code
creates an incoming shipment and updates the shipment number and status.
DPD integration configuration is available from the ticketing system
admin panel. Authorization happens through login, password, and customer number.
The integration scope covers what data will be pulled from DPD
(courier availability/booking, shipment tracking, label and pickup protocol generation).
Configuration involves filling in sender data and shipment templates.
The Debesis ticketing system integration with DPD enables shipment management:
– generating waybills for parcels or envelope shipments,
– sending multiple shipments at once,
– printing address labels and pickup protocols,
– calling a courier to pick up the prepared parcels.
The Debesis request handling system integrated with DPD lets you track
shipment status and view shipment history.
Shoper integration configuration is available from the admin panel.
The configurator includes the following fields: store domain, login, password.
The administrator also defines the integration scope. The integration of our database with Shoper
was developed in cooperation with an e-commerce company. In just a few simple
steps, we connected Customer Service to the sales system, achieving
a fully automated handling process.
Features and capabilities of the Shoper integration:
Order/product import from Shoper into our database. This lets you
display the order list with products, photos, and process orders directly
in our customer panel. Order processing is based on showing the customer's
billing data, shipping data, customer notes, and payment method and status.
Order update functionality – all product-related changes made in our
system are propagated to Shoper. This includes changes to product quantities, removing
and adding products to an order with the ability to search the Shoper inventory, and
price changes.
IdoSell integrates with the Debesis request handling system via API. The integration
can be configured for:
– order status changes,
– shipment status history,
– order events (shipping data changes, order updates),
– inventory search (adding, removing products),
– order details,
– order list.
The Debesis ticketing system integrates with Salesforce via API, with data mapping
and import.
You can add a new source – Salesforce – to a campaign. Configuration takes
a few steps:
– entering Salesforce authentication credentials,
– verifying the connection,
– displaying the list of available objects,
– selecting a Salesforce object as the data source,
– displaying the object's available fields,
– mapping Salesforce fields to Debesis fields,
– defining query parameters and the polling interval.
Once parameters are defined, the ticketing system pulls records from Salesforce and creates
a customer and a ticket in Debesis. If the customer already exists, only a new ticket is created.
Debesis integrates with PocketECG via RESTful API. The integration covers:
1. Setting up an examination in PocketECG – form data is sent to PocketECG
(the "device programming" button opens a modal with the customer's data and the option
to scan the device QR code, which fills in the device ID).
2. Receiving the unlock code, programming the device and sending it to the patient,
conducting the examination, receiving the examination-completed notification, downloading the report from PocketECG, and attaching
it as a document to the ticket in the ticketing system.
See how ticketing system integration with e-commerce, CRM, and shipping carriers helps your team handle customers and complaints faster.
Yes – many companies start with a single integration, such as BaseLinker or Shoper, and only later add more, like InPost, DPD, Salesforce, or Bitrix24. The ticketing system integration with Bitrix24 lets you connect CRM data with request handling without manual data re-entry. We design the Debesis architecture so that new integrations can be added without interrupting team work.
Synchronizations run via API at controlled intervals, with data cached on the Debesis side. As a result, users get the information they need quickly, and the system stays stable even with a large volume of orders and shipments.
If your system has an API or supports data export, we can build a custom integration. In practice, this means analyzing business needs, the scope of data, and synchronization frequency, then deploying and testing the connection with Debesis.