This year we are going to incorporate clients into a staging environment to validate real changes before production and to completely redefine the ticket module, separating it by areas such as sales, support, repairs and call center.
If you made it this far, you already know that at anatod ® we don't really like the “Happy New Year and let's go for more!”
We prefer to count what are we going to do, why we do it, and how it impacts those who use our systems every day.
And 2026 begins with two big decisions, designed for something very simple: that everything works better, with fewer errors, less stress and more predictability for everyone.
A new intermediate step: clients in staging
Until now, the path was quite direct: development → production
And although it always worked, the reality is that the systems grew, the use cases multiplied and the impact of a change today is much greater than a few years ago.
For this reason, in 2026 we will formally incorporate a staging environment, with real clients who agree to participate in this intermediate step between testing and production.
What does this mean?
- Real changes, with real data, but without affecting daily operation
- Deeper validations before releasing something to everyone
- Fewer hot fixes
- More stable and predictable updates
Who will be staging?
Some specific clients, with prior consent, who:
- Want to access new features sooner
- Be willing to give real feedback
- Get in return better quality, more stability and commercial benefits
This is not “trying unstable things”, it is exactly the opposite: it is protect production and improve everyone's experience.
The ticket module is no longer “just another module”
The second decision is something we have been thinking about for a long time.
The ticket system is no longer just “support.”
Today they live there:
- Sales
- Repairs
- Call centre
- Remote support
- Internal follow-ups
- Completely different flows from each other
Forcing all that within the same logic no longer makes sense.
What are we going to do in 2026?
Let's go redefine, separate and specialize the ticket module:
- Different flows depending on the type of care
- Specific statuses and metrics for each area
- Better operator experience
- Better traceability for the client
- Less friction, fewer unnecessary steps
The idea is not to “make it bigger”, but make it clearer, faster and more usable.
2026 is not about adding features for the sake of adding.
It is about order, try better, specialize and make systems more robust for real everyday use.
Thank you for being there, for using the system, for reporting errors, for suggesting improvements and for accompanying this growth.
See you in 2026.
With fewer surprises, more stability and better tools 🚀