
When the customer switches channels, can your operation keep the conversation going?
With ATRA + Denodo, your company can connect distributed data, preserve interaction context, and provide teams with greater visibility to move resolution forward.
How integrated access to data can help Telecom companies preserve service context and move demand resolution forward.
The customer starts a request through customer service, contacts finance to clarify a charge, and, unable to resolve it, escalates to the ombudsman. To them, it's always the same issue. To the company, it can mean different tickets, systems, and teams.
When information doesn't keep up with this journey, each new contact may require consumers to repeat what happened. Meanwhile, agents need to consult different platforms to rebuild the history and understand what actions have already been taken.
This scenario highlights a major challenge for Telecom companies: ensuring that service continuity depends not only on cross-channel communication, but also on access to information that contextualizes each request.
With the new rules established by Federal Decree No. 13.135/2026, this topic becomes even more relevant.
What changes with Federal Decree No. 13.135/2026?
Published in October 2026, Decree No. 13.135/2026 establishes new customer service provisions, including requirements related to channel availability, human support, wait times, request transfers, cancellation, and access to request history.
Among the key highlights is the need to ensure continuity and tracking of requests through to completion, as well as enabling support agents to access the history of requests related to the same generating event or contract, as stipulated by the regulation.
In practice, this reinforces the importance of an operation capable of preserving service context, even when a request moves across different channels, departments, or professionals.
For Telecom companies dealing with high volumes of interactions and information distributed across platforms, this scenario also presents an opportunity to review processes, integrations, and data structures.
What are the main changes in customer service rules?
In addition to the specific obligation in Article 2, the decree sets out a series of requirements for providers subject to general SAC (customer service) provisions. Changes involve channel availability, human support, wait times, cross-channel transfers, response deadlines, and access to request history.
More than adapting customer service channels, it is important to evaluate whether the operation has structured processes, accessible information, and systems capable of tracking each request until its completion.
Below, we highlight the main points of the decree:
Human support on electronic channels
Article 12 establishes that at least one electronic communication channel operates 24 hours a day, seven days a week. It also establishes real-time human support on electronic channels from 8 a.m. to 8 p.m. every day, subject to the regulatory conditions and exceptions provided in the rule.
This does not mean every contact needs to be handled by a human from the very first moment. Automation remains permitted, provided conditions for accessing human support are met.
Phone support and wait times
The decree mandates phone support for covered providers.
Article 15 sets limits for phone wait times to reach human support: up to 20 seconds for at least 80% of handled requests and up to 300 seconds, or five minutes, for the rest, subject to specific sector rules.
Consumers must also be informed of the estimated wait time.
The regulation also sets rules for situations where calls drop before service completion, including calling back within the timeframe established by the decree.
Limit on steps and cross-channel transfer
Articles 13 and 16 limit service levels to five on covered channels and restrict transferring consumers to another channel, except as provided by the regulation.
The goal is to prevent consumers from getting stuck in endless menus or being forced to restart support on another channel unnecessarily.
Continuity and tracking of requests
Article 7 sets rules for the continuity and tracking of requests through to their effective completion.
In practice, this reinforces the importance of recording contact history and allowing requests to be tracked without requiring consumers to repeat previously provided information, unless technically justified.
Deadline for responding to requests
Article 21 sets a deadline of up to seven calendar days to respond to non-urgent requests, counting from request registration.
The response must be clear, objective, conclusive, and address all points raised by the consumer.
The provision also requires immediate action to suspend improper or unsolicited services or charges, so that the issue is finalized within 48 hours.
Streamlined cancellation
Article 20 sets conditions for consumers to request cancellation without being forced to navigate another menu, speak with another agent, or use another service channel.
The request must be accepted through the same means available for contracting, under the terms of the decree. Its effects must be immediate, except when technical processing is demonstrably necessary, subject to applicable rules.
Access to history and record retention
Article 18 guarantees free access to request history and mandates it be made available within five business days upon request. History must be kept for at least six months following request resolution.
Meanwhile, Article 19 sets the retention period for voice or text recordings and messages from customer service channels to at least 90 days after contact.
These deadlines are distinct: one refers to request history, while the other applies to interaction records across service channels.
Important: the requirements in this section must be analyzed in light of the decree's scope and sector-specific rules. This summary does not replace reading the legal provisions applicable to the company's business activity.
How to prepare your operation for the new requirements?
Preparation begins with understanding the regulatory scope. Before modifying systems or procuring new tools, companies must identify which provisions apply to their business and which processes need to be reviewed.
More than adapting customer service channels, it is important to evaluate whether the operation has structured processes, accessible information, and systems capable of tracking each request until its completion.
A practical approach can be organized into five steps:
1. Verify applicability
Identify the business activity, business model, and applicable sector regulations. For marketplaces and intermediary platforms, specifically assess the obligation under Article 2.
2. Map customer service channels and processes
Document the channels used, operating hours, service stages, routing criteria, and procedures for complaints and cancellations.
3. Review indicators and records
Verify if the necessary data is available, organized, and up to date. Assess whether the company can consolidate information on complaints, request resolutions, consumer protection agency feedback, and customer satisfaction.
4. Evaluate automation and tech integration
Analyze whether systems allow tracking requests, preserving interaction history, connecting information across different channels, and properly routing requests while guaranteeing access to human support under required conditions.
5. Establish governance and monitoring
Define process owners, monitoring criteria, and routines to follow up on complementary regulations. When necessary, involve legal, compliance, technology, customer service, and operations teams.
The goal is to translate applicable requirements into clear processes, reliable metrics, and well-defined responsibilities, with integrated data available to support service continuity and decision-making.
How can data integration support service continuity?
Reviewing processes and channels is an important part of preparation. But there is another challenge: how do you ensure that necessary information is available when a request moves from one team to another?
In many organizations, customer service data is distributed across different platforms, such as CRM, billing systems, relationship tools, ombudsman applications, and operational databases.
Even when these solutions function properly individually, a lack of integration can make it difficult to build a complete view of the customer journey.
It is in this scenario that an integrated data access architecture can make all the difference.
With Denodo's data virtualization and integration technology, it is possible to connect information distributed across different sources and provide a unified view for authorized applications and teams.
In practice, this can allow a customer support agent to access:
- Protocols and records related to the customer.
- Interaction history across different channels.
- Departments involved and resolution stages.
- Recorded decisions and routing actions taken.
- Pending issues that still require attention.
Instead of relying on isolated queries across multiple systems, teams gain more context to understand what happened and follow through on the request.
This approach does not necessarily require replacing existing platforms. The data layer enables accessing and combining information from original sources while respecting the security, governance, and permission rules established by the organization.
ATRA + Denodo: connected data for a more consistent service journey
ATRA combines its expertise in data architecture, integration, engineering, and governance with Denodo technology to help organizations build an integrated view of their information.
The initiative begins by understanding the current scenario, identifying data sources, involved processes, and team needs. Based on this diagnosis, an architecture can be designed to deliver the required context to applications and support personnel.
The combination of our capabilities can help companies break down barriers between systems and departments, increase visibility into customer demands, and empower teams to maintain service continuity.
Is your operation prepared to maintain context in every interaction?
Discover how ATRA + Denodo can help your company integrate data, connect cross-channel information, and give teams more context to move request resolution forward with greater intelligence, control, and consistency.
Get in touch
Learn more about who we are and how we can shape the future of your business together.