Municipal software technical support: continuous versus incident-based
Compare technical support models for municipal software: incident reactivity versus integrated continuous support. Key factors to consider before signing.
Summary: When your town council negotiates a software contract for the recycling centre, the type of support included shapes daily operations as much as the platform’s features. This article compares the two predominant models—reactive support for incidents and integrated continuous support—with concrete criteria to help you decide which fits your reality.
Table of contents
- What each model means in practice
- The real cost of reactive support in small municipal teams
- What continuous support includes when properly defined
- Operational differences in recycling centre management
- What to check in the contract before signing
- TuPuntoLimpio’s support model
What each model means in practice
Incident-based support is the standard model in most municipal software contracts. It works like this: something fails, you raise a ticket, the supplier responds within an agreed timeframe—usually 24 to 72 working hours depending on severity—and the supplier’s technical team acts. Outside that scenario, there is no active relationship.
Continuous support is fundamentally different in origin. The supplier is part of the operational cycle from day one: they implement the platform, train your team, answer recurring questions, and adjust configuration when regulations change or your internal processes evolve. Support doesn’t wait for a problem to emerge before activating.
The difference isn’t just response speed. It’s a difference in position: in the first model, you manage the relationship with the supplier when something breaks; in the second, the supplier knows your operations and anticipates friction points before they become incidents.
The real cost of reactive support in small municipal teams
Galician town councils managing recycling centres with teams of two or three people operate with very tight margins. When software fails or raises questions, the effect is immediate: registration stops, data becomes incomplete, or the operative makes decisions without support.
A failure in waste registration for two working days can generate errors in the monthly GaIA report that later require hours of manual review. If that report reaches the Xunta de Galicia with incorrect data, the consequences go beyond lost time.
Reactive support also has a structural problem: it assumes whoever raises the ticket can identify what failed and describe it properly. In teams without specialised technical profiles—the majority in councils under 10,000 inhabitants—that identification isn’t always possible. The result is that the ticket is raised late, described poorly, and resolution takes longer.
68% of incidents in public management software are resolved faster when the supplier knows the client’s specific configuration before receiving the notice.
What continuous support includes when properly defined
The term “continuous support” is frequently used without precise content behind it. To be genuine and not just a sales pitch, it must include at least these elements:
- Complete initial training for all profiles who will use the platform: operatives, technicians, and administrative staff. Not a recorded tutorial: sessions with your actual team.
- Configuration adjustment when something changes in your operations or regional regulations, with no additional cost or formal request process.
- Direct communication channel with the person or team who knows your council, not a generic anonymous ticket system.
- Periodic reviews of platform use to detect friction points before they generate registration or reporting errors.
- Regulatory updates included: when the Xunta changes reporting requirements, the platform adapts without you needing to do anything.
If the contract you’re evaluating calls “continuous support” mere prioritised access to the ticket system, it’s not the same thing. The difference lies in whether the supplier knows your specific operations or just your contract number.
To understand what initial training should include in detail, you can consult this article on what municipal team training should include for a new waste management platform.
Operational differences in recycling centre management
In the specific context of a municipal recycling centre, the two models produce different results in concrete situations:
Change in regional reporting regulations
- Incident-based support: you detect the change, adapt the process manually, or request help. The supplier acts if you raise a ticket.
- Continuous support: the supplier updates the configuration before the change takes effect. You do nothing.
Onboarding a new operative
- Incident-based support: the new operative learns from existing staff. If questions arise, they’re managed internally or a ticket is raised.
- Continuous support: the supplier trains the new operative with the system configured for your recycling centre, not with a generic demo.
Error in last month’s GaIA report
- Incident-based support: you detect the error, describe the problem, wait for a response.
- Continuous support: the supplier can access the registration history, identify where the error was generated, and correct it with you.
The operational workflow management of the recycling centre has friction points that reactive support rarely prevents because it only acts once the problem has already occurred.
What to check in the contract before signing
When reviewing a municipal software contract with support included, these questions make the difference between the two models:
- Does the support include initial training for all users or just one?
- Are regional regulatory changes covered with no additional cost?
- Is there a fixed contact assigned to your council or is support centralised and anonymous?
- What is the average time to resolve a medium-level incident? Is it guaranteed by contract?
- Do configuration updates (new categories, adapted workflows) require formal request or are they included in the service?
- What happens if regulations change during the contract period? Is there an adaptation cost?
If the answers to more than three of these questions are “it depends” or “upon request”, the model you’re buying is reactive regardless of the terminology used in the contract.
Before signing any specification document, it’s also worth reviewing the evaluation criteria for digital tools for municipal civic amenity sites and the procurement guide for recycling centre software in Galicia.
TuPuntoLimpio’s support model
At TuPuntoLimpio, continuous support is not an optional service. It’s part of the product from day one of implementation.
Implementation is completed in 2 to 4 weeks with configuration tailored to your council: waste categories, registration workflows, user roles, and reporting dashboards are built to measure, not inherited from a standard template. Galician regional regulations—including GaIA reports—are integrated from the start, without you needing to do that adaptation work.
Training covers all profiles who will use the platform in your actual operations. Subsequent support has a contact who knows your configuration and context, not a generic ticket system.
When regulations change, the platform updates. When your team grows or changes, training adapts. That’s what it means for support to be integrated into the product.
If you’re evaluating whether this model fits your operations, visit tupuntolimpio.es and request a demonstration tailored to your council.