Como conduzir uma campanha de BPO para um cliente estrangeiro
Calling another country's customers for a client? Whose calling rules apply, what the contract must say, caller ID, time zones and a pre-launch checklist.
Resposta rápida
When a BPO calls another country's customers, the rules where the called person lives can apply, not only those where its agents sit. The FTC says the US Telemarketing Sales Rule covers calls from outside the United States, and GDPR can reach non-EU companies serving people in the EU. Agree a processor contract and who scrubs lists, check caller ID and calling hours, then run a launch checklist.
A BPO wins a client in another country: a retailer in Europe, a lender in the US, a utility in another region. The agents, the platform and the management sit in one place, and the people being called sit in another. Which rules apply to the call?
The short answer is that distance does not remove the rules. This guide sets out whose rules apply, what the client contract should say, how to handle caller ID and time zones, and a numbered checklist for the day before launch. It is general information, not legal advice.
Whose rules apply when you call another country's customers?
Two sourced examples show the pattern.
United States: the Telemarketing Sales Rule
The FTC's guidance on the Telemarketing Sales Rule (TSR) states that it makes no difference whether the calls are made from outside the United States. If a call is telemarketing to a US consumer, the rule applies to the caller wherever the call starts. The same guidance says it is a violation to fail to transmit the phone number, and the telemarketer's name when the phone company makes that available, to the consumer's caller ID service. The rule also limits calls to a residence to between 8:00 a.m. and 9:00 p.m. local time at the called person's location, unless the person has given prior consent (16 CFR 310.4(c)). For how TSR sits within the wider US picture, see the Guia de conformidade TCPA.
European Union: GDPR
Your Europe, the EU's business information site, says GDPR applies to a company established outside the EU that processes personal data in relation to offering goods or services to people in the EU. Such a company has to appoint a representative in the EU. A BPO calling people in the EU for a client is processing their personal data, so the question is not whether to take GDPR seriously but which role you play, which is covered below. The Guia RGPD para centrais de atendimento de chamadas outbound goes into detail.
Other countries
Do not assume the answer for a country not covered above. Each has its own regulator, hours, consent model and register. DialerBee's calling-rule packs exist for the UAE (TDRA), Saudi Arabia (CST), Jordan (TRC) and Bahrain (TRA) only. For every other destination the client's counsel or a local adviser has to supply the rules, and you load them into the platform as configurable controls. The calling hours by region guide e o global calling rules report are the starting points for research, and the recursos de conformidade page describes what the platform can enforce.
A practical rule: apply the stricter of the two sets, the rules at the agent's location and the rules at the called person's location.
What must the client contract say?
An overseas client engagement lives or dies on its contract. Cover these points:
- Roles. Who is the controller (normally the client) and who is the processor (normally you).
- A written processor contract. Your Europe says the controller can only use a processor that offers sufficient guarantees, set out in a written contract with mandatory clauses, such as processing personal data only when instructed to by the controller. Do it before any list is loaded.
- Consent and suppression. Who collects consent, who holds the proof, and who supplies the do-not-call list.
- Recording. Whether calls are recorded, who owns the recordings, how long they are kept and how they are returned or deleted at the end.
- Script approval. Who signs off the script and any change to it.
- Complaints. Who handles a complaint and within what time, and what records each side produces.
- Saída. What data comes back and when. The contract exit terms guide covers this from the software side.
Which caller ID will customers see?
Caller ID is a legal and a commercial question. The TSR guidance lists a requirement to transmit Caller ID information, and customers decide whether to pick up from the number they see. For a foreign client:
- Show a number the customer can call back. A number that rings nowhere damages trust and invites complaints.
- Use a number you are entitled to present. Confirm it with your carrier. On DialerBee, when you bring your own PBX or carrier, the platform verifies that you are entitled to present a number, by Letter of Authorisation or a test call, before it can be used as caller ID (see the deployment page).
- Consider a local number. Matching the called person's area is possible with caller-ID pools and local presence, which should be configured responsibly and within the rules of the destination. See how to configure caller ID groups and local presence.
- Teste. Place a call to a phone in the destination country and read what it shows before launch.
Calling hours across time zones
Agents may start the shift at 9 a.m. in one time zone while the customer is at breakfast, or asleep, in another. The rule that governs is the time at the called person's location.
| Destination | Sourced rule | What to do |
|---|---|---|
| Estados Unidos | Calls to a residence only between 8:00 a.m. and 9:00 p.m. local time at the called person's location without prior consent (16 CFR 310.4(c)) | Schedule by the contact's own time zone; the country spans several |
| União Europeia | Hours vary by member state and are not covered by the GDPR sources used here | Get the rule for each country in the campaign from the client or counsel |
| UAE, Saudi Arabia, Jordan, Bahrain | Calling-rule packs exist in the platform for these four | Review the pack against the current regulator text before use |
Store the time zone with each record, and let the platform decide whether a number can be called now, instead of leaving it to agents. See the calling hours guide for how to set windows.
Lists, consent and DNC: who scrubs and who keeps the proof
Settle three questions in writing before the first list arrives:
- Where did these numbers come from? The client should be able to say, and to show consent where consent is required.
- Who checks suppression? A sensible split is that the client supplies the list with status, and you check it again at dial time with the controls on your platform.
- Who keeps the proof? Both sides should keep their own records of consent, opt-outs and calls, so a complaint is answered with evidence.
For the process side, see Gestão de consentimento em fluxos de trabalho de saída. Note that DialerBee's compliance features are compliance-supporting controls that you configure. They do not by themselves make a campaign compliant, and the client and you remain responsible for the rules.
Language, scripts and recording notices
Foreign-client work often means a language the BPO team does not use daily. Have a native speaker read the script, and have the client approve the final version. If recordings are made, the notice the called person hears has to match the rules of their country, so agree the wording with the client. The platform interface, answering machine detection and transcription cover 11 languages, which helps with multilingual teams. The AI voice agent has run on live calls in Arabic and English, so test any other language on a demo first.
Keeping each client separate on one platform
If you serve several clients, separation protects them and you. DialerBee's multi-tenant design keeps each client's compliance rules, recordings, users and billing apart, so a rule set for one destination does not leak into another client's campaign. For how BPOs structure this work, see the Página de soluções de BPO, o BPO dialer page and the guide on scaling BPO operations. If you are still choosing a platform, the BPO software checklist helps. For a definition of the term, see What Is a BPO.
Pre-launch checklist
- The client contract is signed, with roles, processor terms and the exit plan.
- You have written the destination country's calling rules, with a named source for each.
- Calling hours are set in the platform, by the called person's time zone.
- The list has its origin and consent status recorded, and the suppression list is loaded.
- Caller ID is authorised by your carrier and tested on a phone in the destination country.
- The script is approved by the client and checked by a native speaker.
- Recording notice wording is agreed, and the retention period is set.
- A test call has confirmed that the opt-out key works end to end.
- The client's workspace is separate from every other client's.
- Someone owns complaints, and the report that answers them exists.
Perguntas frequentes
Which country's calling rules apply to an offshore call center?
Often more than one set. The rules where the called person is located can apply, not only the rules where the agent sits. The US Federal Trade Commission says that for the Telemarketing Sales Rule it makes no difference whether the calls are made from outside the United States. GDPR can also reach a company outside the EU that processes personal data in offering goods or services to people in the EU. Local rules where the agents sit apply as well.
Does the Telemarketing Sales Rule apply to calls from outside the US?
According to the FTC's business guidance, yes: it makes no difference whether the calls are made from outside the United States. The rule covers calls that count as telemarketing to US consumers. Calls to a residence are limited to between 8:00 a.m. and 9:00 p.m. local time at the called person's location, unless the person has given prior consent. Confirm how the rule applies to your campaign with qualified counsel.
Does GDPR apply to a call center outside the EU?
It can. Your Europe, the EU's business information site, says GDPR applies to a company established outside the EU that processes personal data in relation to offering goods or services to people in the EU, and that such businesses have to appoint a representative in the EU. Whether it applies to your campaign depends on the facts, so ask counsel.
Do I need a data processing agreement with a BPO client?
If you process personal data on your client's behalf, you are normally the processor and the client is the controller. Under GDPR, the controller can only use a processor that offers sufficient guarantees, set out in a written contract with mandatory clauses, such as processing personal data only when instructed to by the controller. Agree this in writing before any list is loaded.
Who should scrub the list against do-not-call records?
Decide it in the contract, and record it. The usual split is that the client supplies the list with its consent and suppression status, and the BPO checks it again at dial time with the controls its platform provides. Either way, both sides should keep their own proof, so a complaint can be answered with a record and not a recollection.
Can one platform keep several clients separate?
Yes, with a multi-tenant setup. DialerBee's multi-tenant design keeps each client's compliance rules, recordings, users and billing separate, so one client's list, rules or recordings do not mix with another's. Check how that separation is described for your own plan before you promise it to a client.
Fontes
- FTC, Complying with the Telemarketing Sales Rule (it makes no difference whether the calls are made from outside the United States; failing to transmit the phone number, and the name when available, to caller ID is a violation). ftc.gov (checked 2026-11-19)
- 16 CFR 310.4(c), calls to a residence between 8:00 a.m. and 9:00 p.m. local time at the called person's location. law.cornell.edu (checked 2026-11-19)
- Your Europe, Data protection under GDPR (non-EU companies, EU representative, processor written contract). europa.eu/youreurope (checked 2026-11-19)
Isenção de responsabilidade: This article is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance. It summarises the FTC, Cornell Legal Information Institute and Your Europe pages checked on November 19, 2026, and the rules may be amended or interpreted by the authorities. Confirm current requirements for each destination with qualified counsel.
Leituras relacionadas
Artigos relacionados
KPIs e métricas de BPO: fórmulas, métricas de SLA e um scorecard semanal para o cliente
12 minutos de leitura
BPOMelhor software de discagem automática para BPOs
Leitura de 10 minutos
CobrançasCobrança por telefone no Brasil: o que o CDC proíbe
11 minutos de leitura
TecnologiaQuanta largura de banda um call center precisa?
Leitura de 10 minutos
Pronto para ver DialerBee em ação?
Solicite uma demo ao vivo de 15 minutos ou comece um teste grátis de 14 dias — sem slides, sem compromisso. As ligações começam assim que o seu próprio SIP trunk ou PBX estiver conectado e aprovado.
Teste grátis de 14 dias · crédito de IA gratuito · sem cartão · 11 idiomas · BYOC · controles de apoio à conformidade