Klyro
Back to blog
November 18, 2026

Call recording: legal uses and limits

Defines when call recording is mandatory and when it is the company's choice. Explain the difference between prior notice and explicit consent, retention periods according to the LGPD, use in training and quality auditing, security of
Public phone for customer service at a bustling station entrance with signage.
Photo by K on Pexels

Why record calls on answering

Recording service calls serves three main purposes: quality auditing, ongoing attendant training, and legal protection in commercial disputes. The recording allows you to review what was said, confirm promises made, and identify knowledge gaps in the team. In regulated operations, such as health call centers, banks, and insurance companies, recording may be mandatory; in other segments, it is a company choice.

The LGPD requires the company to notify the customer about the recording, explain the purpose, and ensure storage security. The absence of adequate control makes recording passive, especially if the file contains sensitive data and is not deleted at the end of the retention period.

Companies that record conversations in a systematic way are able to monitor quality evolution over time, identify service patterns that generate satisfaction or complaints, and calibrate responses from AI agents and chatbots based on real conversations.

When recording is mandatory and when is it chosen

The requirement to record calls depends on industry regulations. Banks, health insurance providers, insurance companies, and financial institutions often have specific rules from regulatory bodies that require recording of telephone service, with minimum retention periods.

For companies outside these sectors, recording or not is an internal decision. The recording offers traceability: when a customer claims that they received wrong information or that they were poorly served, the company can review the conversation and make an informed decision.

Before deciding to record, the company must evaluate:

  • Purpose: quality auditing, training, dispute resolution, or compliance with external regulations.
  • Volume: how many calls per day, how much storage space will be needed, and how long each file will be kept.
  • Privacy: if the conversation contains sensitive data, such as health, financial, or underage information.
  • Operating cost: secure storage, controlled access, and destruction of recordings at the end of the term.

Record for the sake of recording, without a clear purpose and without a review process, generates cost and risk without benefit.

Difference between prior notice and explicit consent

The LGPD requires consent from the holder for the processing of personal data, but provides for exceptions. In the context of service, the recording usually falls within the framework of “execution of a contract” or “legitimate interest”, provided that the customer is clearly notified before the recording begins.

The advance notice is the automated message that states: “This call is being recorded for quality and training purposes.” This notice complies with the transparency required by the LGPD, but does not replace consent when the purpose of the recording requires it.

Explicit consent is required when the recording will be used for something other than the service itself, such as marketing campaigns, use in public training, or sharing with third parties. In these cases, the company must obtain active authorization from the customer, register that consent, and allow revocation at any time.

In practice, most service operations work with advance notice, because the recording serves to audit quality, resolve disputes, and train staff — legitimate purposes that do not depend on additional authorization.

Retention periods according to LGPD

The LGPD requires that personal data be kept only for as long as necessary to fulfill the purpose for which they were collected. For service recordings, the deadline depends on the purpose:

  • Quality Audit: 30 to 90 days, sufficient to review the monthly sample and identify deviations.
  • Dispute Resolution: up to 5 years, in line with the statute of limitations of the Consumer Protection Code.
  • Team training: 60 to 180 days, reasonable time to capture examples of good practices and recurring problems.

Companies regulated by sectoral bodies must follow the specific deadlines of these regulations. Banks, for example, keep recordings for longer periods due to Central Bank requirements.

The important thing is to document the retention criteria in the privacy policy, configure automatic deletion at the end of the deadline, and ensure that retained files have operational or legal justification. Keeping recordings indefinitely without a clear purpose violates the minimization principle of the LGPD.

Use in training and quality auditing

Recordings are valuable material for training new attendants and retraining those who are already in the operation. The review of real conversations makes it possible to identify:

  • Tone of voice and pace of speech that make the customer comfortable or irritated.
  • Moments in which the attendant missed the opportunity to solve the problem at the first interaction.
  • Incorrect or incomplete information that generated a recontact.
  • Creative solutions applied by an attendant that can be replicated by the entire team.

For quality auditing, the recording must be accompanied by a structured checklist: script compliance, data confirmation before finalizing, offering a complete solution, tone and courtesy. The audit cannot depend on memory or subjective impression; the file allows revision as many times as necessary.

Omnichannel service platforms, such as [BRANDunified inbox] (URL0), centralize WhatsApp, Instagram, email, and chat conversations on the site. In this context, the concept of “recording” extends to the complete history of messages exchanged on each channel, allowing auditing and training based on written and voice conversations, when applicable.

The frequency of the audit must be calibrated: weekly review of a random sample works better than a massive monthly review, because it allows for quick correction of deviations.

Storage security and restricted access by profile

Service recordings contain personal data and, in many cases, sensitive data. The LGPD requires the company to adopt technical and administrative measures to protect these files against unauthorized access, leakage, and accidental destruction.

Good safety practices include:

  • Encrypted storage: audio files must be encrypted at rest and in transit.
  • Profile access control: only supervisors, quality auditors and, when necessary, attendants reviewing the conversation itself should be allowed to listen to recordings.
  • Access Log: record who listened to each file, when and for what reason.
  • Segregation of environments: recordings cannot be on the same server as systems facing the public or shared in uncontrolled network folders.

Companies that operate with [platforms that declare compliance with LGPD/GDPR and access auditing] (URL1) reduce the operational complexity of maintaining this security, because control is already embedded in the system.

When the company hires outsourced call centers, the contract must make it clear who is the controller and who is the operator of the data, according to the definitions of the LGPD, and require the same security measures.

Sample extraction for analysis without exposing sensitive data

Auditing every call for a month is impractical and unnecessary. Random sampling is sufficient to identify patterns and deviations. The sample size depends on the total volume: operations with up to 500 monthly calls can review 10% to 15%; operations with thousands of calls can work with 3% to 5% and are still representative.

Sample extraction must consider:

  • Distribution by attendant: each attendant must have conversations reviewed to avoid selection bias.
  • Cutout by channel and category: WhatsApp sample, phone, and chat; cancellation sample, technical support, and sales.
  • Time of day: peak demand conversations may have a different quality than quiet hours.

When the recording contains sensitive data, the review must be carried out by a trained professional and bound by a confidentiality agreement. Automatic audio transcripts can help analyze content without exposing the client's name and phone number to the auditor, as long as the transcript is anonymized.

[real-time analytics] (URL2) platforms allow monitoring quality indicators — such as first response time, resolution rate, and customer satisfaction — without relying solely on manual review of recordings.

Exclusion at the end of the deadline and right to delete

The LGPD requires that personal data be deleted when the purpose of treatment is achieved or when the owner requests it. For service recordings, this means setting up an automatic deletion routine at the end of the retention period defined by the company.

Manual deletion, dependent on someone's reminder, creates a risk of non-compliance. The ideal is for the system to delete recordings automatically after the stipulated period, keeping only metadata (date, duration, category) for statistical purposes, without the possibility of identifying the customer.

When the customer exercises the right of deletion provided for in the LGPD, the company must locate all recordings containing their personal data and delete them, unless there is a legal or regulatory obligation that justifies the maintenance. In this case, the customer must be informed of the legal basis that prevents immediate deletion.

Companies that keep recordings longer than necessary, without documented justification, assume regulatory risk and can be fined by the National Data Protection Authority (ANPD).

Conversion of recording into a compliance indicator

Recording calls without turning material into action is wasteful. The recording must provide operational and compliance indicators that guide management decisions.

Useful indicators derived from recordings include:

  • Script compliance rate: percentage of calls where the attendant followed the mandatory steps (opening, identification, data confirmation, closing).
  • Resolution rate on the first interaction: how many times the problem was solved without recontact.
  • Average quiet time: long pauses indicate a lack of knowledge or a slow system.
  • Use of inappropriate language: words that generate complaint or escalation.
  • Satisfaction declared by the customer at the end of the conversation: when the company asks and registers.

When these indicators are followed month by month, it is possible to identify trends and calibrate training before the problem becomes a public complaint. Weekly sample review, followed by individual feedback and calibration session with the entire team, keeps quality stable.

Companies that operate with multiple channels - telephone, WhatsApp, Instagram, e-mail, chat - need to extend the recording concept to a complete conversation history. [BRANDcentralizes WhatsApp, Instagram, Facebook, Telegram, email, and website conversations on a single platform] (URL3), preserving context and allowing auditing and training from the unified history.

Frequently Asked Questions

**Does every company need to record service calls? ** No. Recording is mandatory only in regulated sectors (banks, insurance companies, health operators, when required by law). For the others, it is an internal decision based on the need for auditing, training, or legal protection.

**Do you need to ask the customer for permission before recording? ** Yes, but the format depends on the purpose. For use in quality auditing and training, the advance notice (“this call is being recorded”) complies with the LGPD. For uses other than service - such as marketing or sharing with third parties - explicit consent is required.

**How long can the recording be kept? ** It depends on the purpose. For auditing, 30 to 90 days is usually sufficient. For dispute resolution, up to 5 years, in line with the statute of limitations of the Consumer Protection Code. Regulated companies follow specific deadlines set by sectoral bodies.

**Who can listen to the recordings? ** Only authorized people: supervisors, quality auditors and, when necessary, the attendant himself reviewing the conversation. Access must be logged and the company must ensure that files are not shared outside the work context.

**How to use recordings to train staff without exposing clients? ** Anonymize personal data before using recordings in group training. Replace names, phone numbers, and sensitive information with generic identifiers. Alternatively, work with transcripts or short clippings that illustrate good practices without revealing the customer's identity.

**What to do when the customer asks to delete their recording? ** Locate and delete the recording, unless there is a legal or regulatory obligation that justifies the maintenance. Inform the customer about the action taken and, if deletion is not possible, explain the legal basis that prevents it.

**Does recording a conversation on WhatsApp follow the same rules? ** Yes. WhatsApp conversations are personal data and must be treated in accordance with the LGPD. The company must notify the customer, keep the messages only for as long as necessary, and ensure storage security. Platforms that centralize omnichannel service, such as BRAND, preserve the history of conversations in a controlled environment, with access restricted by profile.

References

  • [Call Recording: Uses and Best Practices] (URL4)
  • [Management service report: what to measure and what to decide] (URL5)

Share

Open Instagram and paste the link in your post/story.