A customer calls about a warranty claim. The service adviser has the vehicle history, the recent repairs and the status of the job on one screen. The customer gets a text when the car is ready.
Built for dealer networks, independent workshops, parts distributors and leasing companies running a fleet.
Automotive has three processes of its own: servicing, warranty claims and after-sales care. Each needs to be handled differently.
The customer leaves the car for a service. The workshop has to keep track of deadlines, parts, any claim arising, and of talking to the customer at every stage.
What Debesis does about it:
A dealer handles hundreds of customers a year. Once the contract is signed, they ask about the handover date, the paperwork, insurance and extras — and every one of those turns into a complaint if it is dropped.
What Debesis does about it:
The company sells parts B2B to workshops. Customers ask about availability, prices, compatibility, returns and claims — hundreds of emails and calls a day.
What Debesis does about it:
A ticketing system for automotive organises customer service in a dealer network, a workshop, a leasing company or a parts distributor. What sets it apart from a general helpdesk is that every ticket can be tied to a specific vehicle by VIN, along with its repair history and its owner.
In a car workshop it means the mechanic opens the vehicle history straight away instead of searching several systems, and the customer is told by text at each stage — received, diagnosed, ready. Less time per job, fewer calls to reception.
In a dealer network it joins the sales pipeline to after-sales. After the contract is signed the context stays with the customer: that they asked about insurance, that a spare key is owed, that handover is set for Thursday. Nothing dropped means fewer complaints later.
Questions from service managers, dealer directors and customer service managers in the motor trade.
Yes, over the API. Where the DMS offers a REST API or a data export, we configure the integration during the rollout: customers, vehicles by VIN and repair history are synchronised, so the ticket in Debesis carries what the adviser needs without switching screens.
A warranty claim runs its own workflow with escalation to the importer. The ticket holds the VIN, the fault description, photos, repair invoices and technical documentation. It is sent on automatically as an email with a PDF, or through the importer's own portal where one is available. The status is tracked in Debesis — sent, accepted, paid — and the SLA flags anything running late.
Yes. When a recall covers a range of VINs, you filter owners by VIN and send a text or email with a booking link. Each booking creates a ticket and is assigned to a mechanic automatically, and the report shows how many owners responded and how many cars have been dealt with.
Signing the contract opens an onboarding ticket with a checklist: a courtesy call after a week, a service reminder after a month, an inspection at six months, and a renewal or trade-in conversation at twelve. Nobody gets forgotten.
Yes. Every mechanic has their own queue view showing what is ahead of them and how long each job has taken. The manager sees all of them at once — who is overloaded, who is free, where the bottleneck is. Automatic assignment takes both workload and speciality into account: engine, bodywork, electrics.
Yes, and arguably more so. A small workshop has nobody working reception full time, so the mechanic is the one keeping track of appointments, customers and parts. A ticketing system takes that administration off them. The Basic plan, at 119 PLN per user / month, fits a team of three to five.