By Artem Korsakov ·
A company maintaining equipment typically starts with a ticketing system: the dispatcher receives an inquiry, assigns an executor, and the executor closes the work order. For a simple internal service department, this may be sufficient if there are no additional requirements regarding guarantees, access permissions, and financial settlements. When the network begins to include external partners, manufacturer warranties, and inter-company financial settlements arise, requirements change. Let us examine where the boundary lies.
What a Ticketing System Does
A ticketing system addresses the needs of an internal service department. Off-the-shelf field service tools can manage assigned work and technicians’ mobile workflows. For example, Dynamics 365 Field Service supports offline work after configuration in its supported mobile interface; the refreshed mobile experience does not currently support offline mode. Check the exact version before choosing a product. For your own staff, this is a solved problem, and there is usually no point in developing a proprietary system for it.
Signs that a ticketing system is sufficient:
- all executors work for the same company;
- warranty decisions are made by that same company;
- there is no settlement with external executors, or it is rare;
- the client only needs to know the status and sign off the completed work.
What Changes with External Partners
When work is performed by partners, three new requirements emerge.
Data separation. A partner sees only their own tickets. They must not see other partners' clients or terms. Within a single company, this was not required.
Assignment by rules. A partner is selected based on region, specific equipment qualifications, and workload. If the rules are not codified, assignment turns into dispatcher phone calls.
Qualifications are maintained by equipment models. A single checkmark for a partner is insufficient. A partner may be confident working with boilers of one series but lack authorization for another. If qualifications are recorded as a single checkmark, the dispatcher will assign tickets that the partner cannot resolve on the first visit.
Reporting to the network owner. The manufacturer or head company wants to see timelines and quality for each partner, while partners want to see their accruals.
What Changes with Manufacturer Warranties
If the warranty is paid for by the manufacturer, but work is performed by a partner, one company's solution must operate within another's process. The partner requests a replacement; the manufacturer decides on each component; the partner continues operations. If the manufacturer denies warranty coverage for certain components, the client is offered a paid estimate.
Here, a single-company ticketing system often hits its limits. The manufacturer's decision arrives via letter and is transferred manually; mixed cases are resolved by phone.
What Changes with Financial Settlements
Settlements with partners require justification: exactly what was done, at what rate, and after whose acceptance. Each basis for accrual is recorded once. The client sees their portion, the partner sees theirs, and the manufacturer sees everything. If these amounts are calculated in a separate spreadsheet, reconciliation at the end of the period becomes a separate task.
Settlements also depend on acceptance. No remuneration is accrued until the client accepts the work. If acceptance is delayed, the partner waits for payment, which affects their attitude toward future tickets. Therefore, acceptance must have a deadline and a clear procedure for cases where the client does not respond.
Selection Criteria
Let us summarize the signs into a checklist. Mark what applies to your network:
- More than three external partners in different regions.
- Warranty decisions are made by another company.
- Mixed cases occur: part covered by warranty, part paid.
- Partner remuneration depends on the type of work and is calculated according to specific rules.
- Partners must not see tickets or clients belonging to other partners.
- The client needs a work-completion record without internal monetary amounts.
If one or two points are checked, it is reasonable to start with an off-the-shelf ticketing system and test how well it configures to your rules. If four or more points are checked, you should consider a partner portal: an off-the-shelf product with customizations or proprietary development built on top of the existing ticketing system.
Three points in the middle mean the decision depends on your plans. If the network is growing and will include more partners, it is better to check in advance how an off-the-shelf system handles data separation and settlements. If the network is stable, you can operate with manual operations and review the issue once a year.
Подпись: Example: four out of six criteria are checked, so a portal should be considered. The scale boundaries are derived from the checklist in this article.
Honestly About Options
An off-the-shelf ticketing system quickly handles dispatcher and executor workflows, mobile applications, and status updates. You should test it against your rules: partner separation, component-level decisions, and settlements. If the configuration suffices, no development is needed.
A proprietary portal is justified when network rules are more complex than what can be configured. However, it does not necessarily need to be built from scratch: ticket management and mobile operations can remain in the off-the-shelf product, while the portal handles warranty decisions, partners, and settlements. How to divide functions is determined during implementation.
In any case, start by documenting your network's rules: who makes warranty decisions, how partners are assigned, how remuneration is calculated, and what each party sees. This documentation is required for configuring off-the-shelf systems and for development. Without it, comparing options is meaningless: each vendor will demonstrate what their product can do, and you cannot know if it aligns with your network's needs.
In the demonstration scenario, you can trace a chain that extends beyond a single company: warranty, partner assignment, diagnostics, manufacturer decision, acceptance, and remuneration.
Related article: Who is responsible for repairs if one company sells the equipment and another services it.
Sources and Example Boundaries
Sources confirm the described functions of off-the-shelf products, not demand or return on investment for proprietary development. Scenarios and amounts are educational. Demonstrations use fictional data; real integrations, AI, payments, and external publication are not included.