Powered by Smartsupp

Ticketing with BaseLinker

BaseLinker integration with the Debesis ticketing system

Your support team sees orders, parcels and event history from every marketplace inside the ticket — without switching to the BaseLinker panel.

Orders in the ticketParcel statusMulti-marketplaceAPI token

Book a demo

Why connect them

What changes when both systems talk to each other

Debesis brings requests in from e-mail, phone, forms and other systems. BaseLinker holds the orders. Connected, they answer the question every agent asks first: what exactly did this person buy, and where is the parcel now?

Full order context in the ticket

Debesis identifies the customer by phone number or e-mail address. A widget inside the ticket lists their orders, products, delivery and payment details and the event history — no separate login.

Faster answers in e-commerce

An agent no longer jumps between marketplaces. Everything needed to answer a question about a complaint or a return is already on screen, which shortens replies and cuts mistakes.

Automation and reporting

Order status can change automatically when a ticket is closed. You can also report request volume against orders and shipments, which makes planning support staffing easier.

How it works

How the integration is set up

Two steps on the BaseLinker side, a short form on the Debesis side. No development work.

  1. Generate an API token in BaseLinkerMy account → API → Generate token. The token is what allows Debesis to read order data.
  2. Add the integration in DebesisIn the Integration tab enter a display name, select BaseLinker as the service and paste the token.
  3. Match the customerDebesis looks the customer up by phone number or e-mail address taken from the request — no manual searching by order number.
  4. Work inside one screenOrders, delivery and payment details and status history appear in the ticket widget, in real time.

Who it is for

Who benefits most

The integration pays off wherever order accuracy and speed decide how the customer rates the shop.

Online shops selling on several channels

Own store plus marketplaces means orders scattered across panels. Here they all meet the request that concerns them.

Teams handling dozens or hundreds of orders a day

At that volume, every switch between systems costs minutes. Removing it lets the same team handle more requests.

Complaints and returns desks

Return and complaint cases need the order, the payment and the parcel in one place — that is exactly what the widget shows.

Wholesalers and logistics operators

Large order volumes and questions about shipment status are answered without leaving the ticket.

FAQ — BaseLinker and Debesis

What do I need to connect BaseLinker to Debesis?

An API token generated in BaseLinker (My account → API → Generate token) and the Integration tab in Debesis, where you enter a name, choose BaseLinker as the service and paste the token.

How does Debesis know which order belongs to the request?

The customer is matched by phone number or e-mail address from the request, so agents do not search by order number.

Is the order data live?

Yes. The widget reads current data from BaseLinker, including delivery and payment details and the event history of the order.

Does it work with several sales channels at once?

Yes. BaseLinker aggregates orders from marketplaces and shops, and Debesis shows them in the ticket regardless of the channel they came from.

Can a closed ticket change the order status?

Yes, automation rules can update the order once a request is resolved. The exact scenario is agreed during implementation.

How much does the ticketing system cost?

Plans are priced per agent: 119, 149 and 169 PLN net per user per month, with a 10% discount on annual billing. Start with a demo and a trial period.

All integrations