---
title: "Customer service data and attachments: what to request and keep · Lyntev"
description: "Ask only for necessary information, choose a suitable channel and define where attachments go. Includes triage, retention, deletion and a fictitious scenario."
url: "https://lyntev.com/en/guides/customer-service-data-attachments"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. Which data and attachments should you request during online service?

# Which data and attachments should you request during online service?

Request only what the current stage needs and explain the purpose. Before receiving attachments, check that the channel, tool and team can handle them appropriately. Define where they go, who needs them and when they should be reviewed or deleted; a conversation’s existence does not justify keeping everything forever.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 20 November 2026.
About 6 minutes to read.

[Start reading](<https://lyntev.com/en/guides/customer-service-data-attachments#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/dados-anexos-atendimento.txt>)

**The answer starts with the source**Approved information, defined access and a verifiable answer.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/dados-anexos-atendimento>); source revision 20 November 2026.

By the end, you can:

- Justify the data needed at each stage
- Distinguish ordinary content from information needing another channel
- Track copies, retention and deletion of attachments

In this guide

1. [Connect each item of data to a service decision](<https://lyntev.com/en/guides/customer-service-data-attachments#finalidade-primeiro>)
2. [Separate triage, contracting and delivery of the service](<https://lyntev.com/en/guides/customer-service-data-attachments#etapas-e-minimo>)
3. [Choose the channel according to the information type](<https://lyntev.com/en/guides/customer-service-data-attachments#canal-e-conteudo>)
4. [Define formats, limits and safe handling](<https://lyntev.com/en/guides/customer-service-data-attachments#regras-anexos>)
5. [Apply the rule to a fictitious scenario](<https://lyntev.com/en/guides/customer-service-data-attachments#exemplo-fotografia>)
6. [Map where copies remain and when they are needed](<https://lyntev.com/en/guides/customer-service-data-attachments#copias-e-retencao>)
7. [Explain processing and prepare for corrections](<https://lyntev.com/en/guides/customer-service-data-attachments#transparencia-e-pedidos>)
8. [Test the journey with fictitious information](<https://lyntev.com/en/guides/customer-service-data-attachments#ficha-dados-anexos>)
9. [Sources and criteria](<https://lyntev.com/en/guides/customer-service-data-attachments#fontes>)

## Connect each item of data to a service decision

List the questions the team needs to resolve and the data that allows an answer. Giving opening hours or a service area may require no document. Assessing a fault may need only the equipment type and an initial description. Requesting full identification in the first message adds data processing without demonstrating usefulness for that task.

The GDPR requires, among other principles, a defined purpose, data minimisation and proportionate retention. The lawful basis and information to provide depend on context; adding the same consent sentence to every flow does not resolve them. This guide organises operational-design questions and does not, on its own, determine the legal framework for each activity. Validate sensitive situations with competent support.

## Separate triage, contracting and delivery of the service

Data may become necessary later without being necessary at the start. Distinguish what guides the person, prepares a proposal, formalises a relationship or delivers the service. This allows progressive information requests and prevents exploratory enquiries from generating extensive files. Where something is optional, the person should understand they can continue without supplying it.

Prepare alternatives. If a general photograph clarifies the situation, do not request a complete document also containing third-party information. If only a reference is needed, explain where to find it and what should not appear in the image. Staff and AI should both be able to follow the rule without expecting every customer to guess how to protect what they send.

Separate triage, contracting and delivery of the service

| Stage | Information to justify | Control question |
| --- | --- | --- |
| Guidance | Intended service and minimum context | Can I answer without identifying the person? |
| Assessment | Data that changes the proposal | Would a less detailed version suffice? |
| Delivery of the service | Information needed for the agreed work | Are the channel and recipients appropriate? |
| Closure | Records still needed | Which copies should be reviewed or deleted? |

## Choose the channel according to the information type

Not every attachment should enter the same message inbox. Financial data, identity documents, health information or confidential content may require another route and specific measures. WhatsApp’s own rules restrict requesting and sharing certain identifiers and give healthcare situations particular requirements. Consult the channel’s and service’s current conditions.

Do not conclude that everything is suitable simply because transmission is encrypted. Content may be seen by people, applications, AI services and backups with different conditions. Ask what happens after it reaches the device. Where information should not be received through that channel, explain a valid alternative and avoid asking customers to resend it to the same destination.

## Define formats, limits and safe handling

State accepted file types, their purpose and what to do if they cannot be opened. Do not ask staff to run programs or enable document features to read a quote. An unexpected attachment should follow the defined security procedure, particularly with an unknown sender or context. Pressure to respond quickly does not remove that need.

Where data extraction or AI analysis exists, confirm which documents enter the service, the purpose, recipients and applicable contractual conditions. Do not upload an entire conversation to an external tool merely to obtain a simple summary. Use fictitious examples in initial tests and assess whether the task can be completed with less content or structured fields.

## Apply the rule to a fictitious scenario

Assistência Ponte, a fictitious business, receives a request about domestic equipment. The team asks for the model and a description of the symptom. Only if assessment needs a photograph does it explain the required framing, avoiding faces, documents and surrounding information that does not help the work. Material is associated with the request in an authorised location rather than scattered across personal phones.

If the customer accidentally sends a document containing excessive data, the team does not reuse it for other purposes or forward it to everyone. It applies the defined procedure for restricting processing and correcting collection, with appropriate assessment of the case. The scenario teaches minimisation and destination; it is not legal advice or a real Lyntev incident.

## Map where copies remain and when they are needed

An attachment may exist in the conversation, device, CRM, project folder and backups. Deleting just a message may not remove the other copies. Map the journey and define who manages each destination. Retain what the purpose and applicable obligations require rather than choosing a universal period for every document.

Distinguish assessment drafts, service materials and records with their own retention needs. Record reviews and deletions proportionately without keeping sensitive content in a new file merely to prove it was deleted. If the tool cannot apply the defined lifecycle, document the limitation and reassess the process before increasing the information received.

## Explain processing and prepare for corrections

People should be able to know why information is requested and how to contact the business about processing. Coordinate service wording with the privacy policy and how the tools actually work. A website description omitting an important recipient or AI analysis may no longer match the process the team carries out.

Prepare a way to locate a request to correct data, respond to a request or investigate an incorrect submission. Verify identity and scope through appropriate procedures without requesting more documents than necessary. Questions about rights, mandatory retention and incidents may require specific legal and technical assessment. The team should know where to refer them rather than improvise guarantees of total deletion.

## Test the journey with fictitious information

Work through a case from the first question to closure: receipt, access, any extraction, use, copies and planned deletion. Use fictitious data and ask another person to identify each material’s destination. If you cannot explain where an attachment remained, operations are not yet sufficiently understood to accept more sensitive documents.

The following worksheet complements permission design but focuses on the information lifecycle and necessary minimum. Review it when adding an integration, AI tool or new purpose. The quality criterion is being able to justify collection and handle content according to the approved process while keeping service understandable for the customer.

### Worksheet for your project

```
Task and processing purpose:
Data needed at each stage:
Optional fields and less intrusive alternatives:
Information that should not enter this channel:
Attachment formats and limits:
Recipients, tools and any AI use:
Locations holding copies:
Retention, review and deletion criteria:
Information provided and contact channel:
Procedure for an incorrect submission or correction request:
Fictitious case tested and gaps found:
Person responsible and next review:
```

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [EUR-Lex — RGPD, em especial artigos 5.º, 6.º, 13.º e 32.º](<https://eur-lex.europa.eu/eli/reg/2016/679/oj?locale=pt>)
- [WhatsApp — política de mensagens empresariais](<https://whatsappbusiness.com/policy/>)
- [WhatsApp — ferramentas da aplicação Business](<https://whatsappbusiness.com/products/business-app-features/>)

## Continue to your next decision.

- [Organise customer data](<https://lyntev.com/en/guides/organise-customer-data-history>)
- [Define appropriate permissions](<https://lyntev.com/en/guides/define-team-permissions>)
- [Assess AI-powered data extraction](<https://lyntev.com/en/guides/extract-document-data-with-ai>)

This guide is part of [Improve customer service with AI.](<https://lyntev.com/en/guides#atendimento-whatsapp>)

- [How to measure whether customer service resolves requests](<https://lyntev.com/en/guides/measure-customer-service-resolution>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
