Who owns the ticket and the customer relationship in each model?
In white-label and subcontract, you keep the customer relationship and the ticket. The provider does the on-site task and returns notes, photos and test results to your record. In direct engagement, the customer deals with the provider, so the provider owns its own ticket flow.
This matters because the owner of the ticket decides what the customer is told and when. In a white-label arrangement, agree how the provider updates your ticket: directly in your system, by email-to-ticket or by structured updates. At Deploris, that method is written into the scope and depends on your platform and security rules.
How are liability and escalation handled?
Contracts decide liability, not the model's name. As a general pattern, your customer holds you responsible, and you in turn rely on the provider under your contract with it. A well-drafted agreement lines up the two, so that obligations you owe your customer, such as site rules or confidentiality, are matched in what the provider owes you. Take legal advice on the wording.
Escalation follows the same logic. In white-label, escalations go to you first, and you decide whether to involve the provider. In direct engagement, the customer contacts the provider directly. Whatever the model, write down the escalation contacts, the out-of-hours route and who can approve extra work. NIST guidance on supply chain risk management is a helpful reference for the questions to ask about any provider that works inside a customer's environment.
- Check that obligations to your customer are flowed down to the provider.
- Agree the insurance and incident reporting expectations in the contract.
- Name the escalation contacts and the route for urgent issues.
What does Deploris agree in a white-label or subcontract arrangement?
Deploris agrees the details in a written scope before work begins, and does not assume them. The scope covers the sites, the tasks, exclusions, access rules, escalation contacts, branding instructions and how reporting works. Pricing, response expectations and engineer arrangements are set in that scope, not published as fixed terms.
You keep control of the customer relationship, your branding where you choose white-label, your ticket system and approval of work. A small first job is a sensible way to check that access, communication and reporting work as planned. The partner page describes the models and the steps in more detail.
The verdict
White-label wins if you are an MSP or reseller who needs to keep the customer, the ticket and the brand. Direct engagement wins if you are the end customer, or want one accountable provider without an intermediary, and subcontract fits a named project beyond your coverage. In every case the written contract and scope decide the real terms.