Philippine AI voice agents for UK payment customer support

Executive Summary

1. The Philippine supplier can structure the proposed inbound service as outsourced technical and administrative support. That conclusion depends on its actual functions: taking no funds does not by itself exclude account-information or payment-initiation services. The institution's authorisation does not become the supplier's licence. (Payment Services Regulations 2017 (PSRs), SI 2017/752, Sch 1, Part 1, para 1, and Part 2, para 2(j); FCA PERG 15.3, Q25A–Q25B.)
2. Payment instructions, executable refunds and changes to payment authority require a new assessment before activation. The parties must distinguish outsourcing from provision through a registered agent and from the supplier's own regulated service. A customer mandate supplies neither registration nor authorisation. (PSRs, regs 2, 34, 67 and 138.)
3. The institution retains responsibility for outsourced acts and omissions. It must notify the Financial Conduct Authority (FCA) when it intends to outsource a payment-related operational function; additional restrictions apply where failure would materially impair compliance, financial performance or service continuity. (PSRs, regs 25 and 36.)
4. Customer explanations, complaint intake and vulnerability support remain subject to the institution's applicable conduct duties. Payment-service complaints normally require a final response within 15 business days after receipt day. Human review must have the information, time and authority needed to change an outcome. (FCA PRIN 2A.5–2A.6; DISP 1.6.2AR; UK General Data Protection Regulation (UK GDPR), Arts 22A–22C.)
5. UK hosting does not remove the international transfer created by access for a separate Philippine supplier. That access needs an appropriate transfer route and the current data protection assessment. The model provider's identity, locations and reuse terms must be fixed before personal data enter its service. (UK GDPR, Arts 28, 44A and 46.)
6. The Philippine foreign-data exception requires an assessment of the information, its original collection and the processing purpose. It does not give the supplier blanket immunity from privacy or security duties. Ordinary recordings, voice identification and health disclosures also require different classifications. (Republic Act No 10173, ss 3–4 and 20; implementing rules, ss 5–6; UK GDPR, Arts 4(1)(14) and 9.)
7. Outbound marketing and collections should remain outside the first contract. Automated marketing rules turn on the actual calling system and recorded content; an AI-generated greeting can require specific prior consent. Genuine collection activity still needs its own purpose, permission and customer-treatment assessment. (Privacy and Electronic Communications (EC Directive) Regulations 2003, SI 2003/2426 (PECR), regs 19, 21 and 24; FCA CONC 7.1.1R.)
8. The contract should allocate change approval, testing, incident response, audit access and exit duties across all three providers. Those allocations support the institution's compliance but cannot remove statutory responsibility or customers' rights. New FCA incident and material third-party reporting provisions take effect on 18 March 2027 and need a separate implementation plan. (PSRs, reg 36; UK GDPR, Arts 28 and 82; FCA 2026/6, cl C.)

The proposed inbound call path

The initial service should answer factual questions within the payment institution's existing customer relationship. The supplier would provide the voice software and Philippine escalation staff. The institution would approve the information, authentication process, permitted account fields and escalation rules. These are recommended contractual controls for the hypothetical service, not additional facts about an existing deployment.

The recommended call path has five stages:

1. The opening identifies the institution and automated assistant, explains recording or transcription, and gives an accessible route to a person. Any recording authorisation required for the proposed capture arrangement is obtained before capture starts.
2. The institution's approved process authenticates the caller before account information is disclosed. An unsuccessful check sends the caller to an alternative verification route without revealing account data.
3. A restricted interface retrieves only the authenticated customer's permitted fields. The language model cannot select another customer's records or change the access rules.
4. The assistant explains the retrieved facts using approved material. A disputed fee, request for a transaction, sign of vulnerability or expression of dissatisfaction moves to the appropriate human queue. Uncertainty about an answer also triggers escalation.
5. The receiving person sees the relevant conversation and original contact time, can correct the explanation, and can take the action within that person's authority. The case record preserves what happened and the reason for any consequential decision.

These controls implement the institution's duties to provide understandable communications and accessible support, alongside risk-appropriate data security. They should be tested against wrong-customer retrieval, ambiguous speech, interrupted calls and unavailable escalation staff. A successful demonstration on a standard script does not establish performance under those conditions. (FCA PRIN 2A.5.3R, 2A.5.10R and 2A.6.2R; UK GDPR, Art 32.)

The first release should disable transfers, refunds, beneficiary changes, changes to authentication credentials, credit decisions, investment recommendations and final complaint decisions. This extends the stated limits by reserving security-sensitive account changes and executable refunds for the institution's authorised process. The restrictions should exist in application permissions and tool interfaces, rather than depend only on a spoken instruction to the model.

The supplier's payment-services boundary

The strongest case for the initial arrangement is that the supplier supports the institution's payment service without supplying a payment service of its own. The PSRs identify regulated activities by function. Their technical-service exclusion covers qualifying support provided without possession of the funds, but expressly leaves account-information and payment-initiation services outside that exclusion. A description of the business as software or business-process outsourcing cannot replace that analysis. (PSRs, Sch 1, Part 1, para 1, and Part 2, para 2(j).)

For the recommended service, the institution remains the customer's provider. Its system authenticates the customer and controls access to its own account records. The supplier answers on the institution's instructions under a business-to-business contract. Those features support a technical and administrative classification. FCA perimeter guidance distinguishes support to a regulated provider from a supplier contracting to provide its own account-information service. That guidance is persuasive because it explains how the FCA applies the statutory definitions. (PSRs, reg 2; FCA PERG 15.3, Q25A–Q25B, and 15.5, Q39.)

The adverse case arises if the supplier undertakes to supply account information directly to users, controls credentials or adds a service that initiates payments. Account-information services can concern one account; access to only one institution's records is therefore no complete answer. The customer contract, interface, permissions and actual operation must support the claimed supporting role. The institution's own status cannot authorise a separate service supplied in the contractor's name. (PSRs, regs 2 and 138; FCA PERG 15.3, Q25A.)

Territorial scope is a separate question. The UK prohibition concerns provision of payment services in the United Kingdom. FCA guidance says that an overseas person supplying from abroad is generally outside that authorisation requirement. UK customers and UK servers do not alone settle where the supplier provides the service. A UK establishment, the arrangements for provision through an agent, and the actual distribution of functions can change the result. The UK institution's outsourcing duties remain relevant even where its Philippine contractor does not itself need UK authorisation. (PSRs, regs 25, 34 and 138; FCA PERG 15.6, Q46.)

The Philippine payment-system test also concerns functions. Bangko Sentral ng Pilipinas (BSP) rules identify operators by activities that maintain payment platforms or networks, process payments or perform equivalent operations. Factual support and escalation do not, on the stated functions, amount to operating those mechanisms. The initial scope should therefore remain outside control of payment processing. Adding that control requires a fresh Philippine assessment; absence of custody alone would not settle it. (BSP Manual of Regulations for Payment Systems, s 502.2; BSP, FAQs on Registration of Operators of Payment Systems, pp 3–4.)

Transaction powers change the classification

The parties should divide each proposed expansion into its actual action. Logging a refund request differs from deciding entitlement and executing a transfer. Correcting a display error differs from changing a beneficiary or authentication factor. The word refund does not identify the payment service, the legal entitlement or the party taking the decision. (PSRs, reg 2 and Sch 1, Part 1.)

If the supplier actually provides the institution's payment services on its behalf, the agent regime needs consideration. Regulation 34 requires registration before the institution provides UK payment services through that agent. If the supplier instead offers its own payment-initiation or account-information service, its own status and territorial position require assessment. Merely adding a human approval button does not resolve either classification. (PSRs, regs 34 and 138; FCA PERG 15.4, Q28.)

A payment mandate must fit the agreed procedure for the payer's consent. It does not expand the institution's permissions or give the contractor a regulatory status. Before activation, the institution should map who receives the payment order, authenticates the customer, controls credentials, submits the instruction and can stop it. The authentication assessment must follow the real telephone and application flow; the parties should not assume that every voice interaction has identical requirements. (PSRs, reg 67; FCA PERG 15.3, Q20 and Q25B.)

The controlled route is a documented change to scope, legal classification, permissions and customer terms, followed by testing of the precise action. It must cover complaint consequences, fraud controls, reversal and customer redress. (PSRs, regs 25 and 34.)

Where an outsourced banking or payment-service function requires authorisation or registration where the institution is authorised, European Banking Authority (EBA) guidance sets additional conditions for a third-country provider. These concern the provider's local authorisation or registration and supervision, together with an appropriate agreement enabling supervisory cooperation. They do not require a banking licence for ordinary technical support. (EBA/GL/2019/02, paras 62–63.)

The payment institution's outsourcing responsibility

The institution must assess this arrangement as a payment-related operational outsourcing. Regulation 25(1) requires notice to the FCA of an intention to outsource an operational function relating to payment services. The notice requirement is not confined to functions classified as important. Under regulation 36, the institution remains responsible for outsourced acts and omissions as if it had expressly permitted them. A supplier indemnity changes contractual recourse, not that statutory allocation. (PSRs, regs 25(1) and 36.)

A function is important where defective or failed performance would materially impair compliance, financial performance, or the soundness or continuity of payment services. An assistant dealing with account access, payment complaints and vulnerable customers can meet that test even without executing payments. The institution should assess volume, customer dependence, alternative channels and the effects of failure. A small pilot with a fully effective fallback can have a different impact from the sole customer contact channel. (PSRs, reg 25(3).)

For important functions, outsourcing must preserve management responsibility, obligations to users, authorisation conditions, internal controls and effective FCA supervision. The institution needs staff capable of understanding the service, challenging the supplier and running an exit. It cannot retain only the contract while the supplier controls the knowledge, records and practical ability to serve customers. (PSRs, reg 25(2); EBA/GL/2019/02, paras 37–40.)

The FCA expects payment institutions to continue to comply with the EBA outsourcing guidelines to the extent that they remain relevant. Those guidelines address due diligence, an outsourcing register, risk assessment and detailed written terms. They are supervisory guidance, distinct from the binding PSRs. Bank-only Prudential Regulation Authority requirements should not be applied to this authorised payment institution merely because the service concerns money. (FCA, Outsourcing and operational resilience, updated 14 July 2026; EBA/GL/2019/02, paras 7–10, 53–55, 61 and 74–75.)

An important supplier becomes a designated critical third party only through Treasury designation of the particular entity. Designations took effect on 13 July 2026, but using a designated cloud provider does not discharge the institution's own duties or extend designation to every model provider. Licentium's analysis of the UK critical third parties regime explains that separate supervisory regime. (The Critical Third Parties (Designation) Regulations 2026, SI 2026/777, regs 1(2) and 2.)

Service continuity and reporting

Operational resilience applies directly to authorised payment institutions under SYSC 15A. The institution must identify its important business services, set impact tolerances and understand the resources needed to deliver them. An outsourced function and an important business service are different units of assessment. Customer support may be a resource needed for a wider payment service, or a service requiring its own analysis. The supplier's availability percentage does not establish the customer's tolerable disruption. (FCA SYSC 15A.1.1R(3), 15A.2.1R, 15A.2.5R and 15A.4.1R.)

Tests should cover loss of the model provider, Philippine connectivity failure, corrupted approved content, wrong-customer retrieval and a surge in complaints. The institution needs a tested way to disable unsafe answers while preserving customer access. A human fallback must have sufficient capacity and relevant records when the AI channel fails. Scenario testing must address severe but plausible disruption and the institution's impact tolerances. (FCA SYSC 15A.2.9R and 15A.5.1R.)

Current PSR duties require operational and security risk controls and notification of major incidents without undue delay. If an incident has or may have an impact on users' financial interests, the institution must inform them without undue delay. That notice must cover the incident and measures users can take to reduce its adverse effects. Data-protection breach reporting has a different threshold and clock. The incident playbook should make both assessments without waiting for a complete technical diagnosis. (PSRs, regs 98–99, particularly reg 99(3); UK GDPR, Arts 33–34.)

A further change is already made but takes effect on 18 March 2027. FCA 2026/6 introduces revised operational-incident reporting and new material third-party notification and register requirements that expressly include authorised payment institutions. Material third-party arrangements can extend beyond outsourcing. The future annual register submission must not be confused with existing outsourcing records or used to defer present notification duties. The contract should require the supplier to supply the necessary information before that commencement date. (FCA 2026/6, cl C; new SUP 15.18.1R(2), 15.18.3R(7), 15.18.6R, 15.19.1R(3), 15.19.6R, 16.33.1R(3) and 16.33.6R.)

The institution should assign a person to check operative rule changes against its service and contract. Licentium Horizon lists FCA coverage and custom-source monitoring as an available monitoring aid. Any alert still needs review against the applicable instrument and commencement provision.

Customer understanding and complaint deadlines

The institution should assess the proposed retail support service under the Consumer Duty. The Duty applies to payment institutions through its own application provisions and covers relevant activities connected with retail payment services. It should not be extended automatically to every wholesale customer relationship. For the first release, a defined retail customer population and approved products would make the intended support outcomes testable. (FCA PRIN 3.1.1AR, 3.1.12R and 2A.1.7R.)

Spoken explanations must support customer understanding and be clear, fair and not misleading. The institution remains responsible when another firm communicates on its behalf. Approved fee content needs effective dates and product conditions; the system should not invent an explanation when the retrieved record does not answer the question. Testing must examine customer understanding and correct identified deficiencies. (FCA PRIN 2A.5.1R, 2A.5.3R and 2A.5.8R–2A.5.10R.)

Support must account for customers' needs, including vulnerability, without unreasonable barriers. The assistant should recognise difficulty understanding, distress, repeated failed authentication and requests for another channel. The institution should test actual access to trained staff, rather than measure only the percentage of calls contained by automation. A reduction in transfers is not a successful outcome if customers abandon unresolved problems. (FCA PRIN 2A.6.1R–2A.6.2R; FCA FG21/1, Guidance for firms on the fair treatment of vulnerable customers, sections 3–4.)

A payment-service complaint can be oral and need not contain the word complaint. Relevant dissatisfaction includes alleged financial loss, material distress or material inconvenience. The supplier should preserve the original receipt time and send the full context to the institution. Late recognition by a classifier does not create a new receipt date. (FCA Glossary, PSD complaint; DISP 1.1.10AR and 1.3.1R.)

Except where DISP's summary-resolution procedure applies, the institution must send a prompt written acknowledgement with the applicable response times. For a PSD complaint, it normally owes a final response by the end of 15 business days after receipt day. Only exceptional circumstances beyond its control justify a holding response by that deadline, giving the reason and the final-response date. The final response must follow no later than 35 business days after receipt day. It must be on paper or another durable medium agreed with the complainant and include the applicable Financial Ombudsman Service referral information. Ordinary supplier delay does not itself establish the exception. Non-Financial Ombudsman Service-eligible payment users have the separate complaints route in PSR regulation 101. (FCA DISP 1.5.1R, 1.5.4R, 1.6.1R, 1.6.2R(1) and 1.6.2AR; PSRs, reg 101.)

The institution should reserve disputed entitlement, vulnerability adjustments and final complaint decisions for trained staff in the initial contract. This is a proposed control, not a universal rule that AI can never assist with those tasks. The legally required result is competent and impartial complaint investigation, appropriate explanation and redress where due. The supplier needs enough time and authority to pass the case to someone who can deliver that result. (FCA DISP 1.4.1R.)

Human review that can change the outcome

Meaningful human involvement depends on what staff can do in the particular decision. Under the current UK GDPR, a decision is solely automated when there is no meaningful human involvement in taking it. A significant decision produces legal effects or similarly significant effects for the person. Simple topic classification and factual assistance ordinarily do neither. An automated refusal of account access, relief or a complaint can be materially different. (UK GDPR, Art 22A.)

Article 22C requires safeguards for significant solely automated decisions based on personal data, including information, representations, human intervention and the ability to contest the decision. Article 22B restricts significant solely automated decisions based entirely or partly on special-category data. One route requires the decision to rely entirely on data processed with the person's explicit consent. The other requires the decision to be necessary to form or fulfil a contract between the person and a controller, or to be required or authorised by law; Article 9(2)(g) must also apply. Article 22B also prohibits reliance on the recognised-legitimate-interest basis in Article 6(1)(ea) for significant solely automated decisions. The remaining lawful-basis, fairness and accuracy duties continue to apply. These provisions replaced the former Article 22 regime from 5 February 2026. (UK GDPR, Arts 5–6 and 22B–22C; Data (Use and Access) Act 2025, s 80; SI 2026/82, reg 2(j).)

A human who merely accepts an answer without relevant records, decision authority or time cannot supply the missing involvement. The contract should give reviewers access to the conversation, the underlying account facts and the model's action history. They must be able to stop an action, correct an answer and record their own decision. The Philippine National Privacy Commission (NPC) supports competent and authorised intervention where automated decisions risk significantly affecting individuals. Its AI advisory applies existing privacy duties to AI rather than creating a separate AI licence. (UK GDPR, Art 22A(1)–(2); NPC Advisory 2024-04, s 2(B)(2)(a).)

Philippine law needs its own automated-decision assessment. Where the Philippine rules apply, section 48(b) of the Data Privacy Act's implementing rules prohibits decisions with legal effects based solely on automated processing without the person's consent. The foreign-data scope rules and the actual effect of the decision therefore matter before adding transactional or conclusive decision powers. (DPA implementing rules, ss 5–6 and 48(b).)

Control of customer data and model reuse

The institution will normally be controller of the defined support processing because it decides why customer data are used and the essential arrangements. The Philippine supplier is a processor while it acts on documented instructions. If the institution contracts directly with the model provider, that provider may be another processor of the institution. If the Philippine supplier appoints it to carry out the instructed processing, it is a subprocessor. The contract structure must follow the actual decisions and data flows. (UK GDPR, Arts 4(1)(7)–(8) and 28.)

The adverse case is a provider using conversations for its own general-model development, indefinite retention or unrelated analytics. It may become controller of that processing despite a processor label. Joint controllership requires joint determination; it does not arise merely because two companies handle the same transcript. The proposed initial contract should prohibit general-model training and reuse across clients, with any later proposal requiring its own role, purpose, lawful-basis and transparency assessment. Removing names alone does not establish that information is anonymous. (UK GDPR, Arts 4(1)(1), 5(1)(b)–(c), 26 and 28(10).)

Each purpose needs a lawful basis. Necessary account assistance may fall within contractual necessity. Recording for quality assurance requires its own necessity and proportionality assessment; a balanced legitimate-interest basis may be available. Consent is neither invariably required for every UK recording nor sufficient to cure unrelated reuse or an unlawful transfer. Processing special-category information requires an Article 9 condition as well as an Article 6 basis. (UK GDPR, Arts 5–6 and 9.)

The Article 28 agreement must cover instructions, confidentiality, security, subprocessors, assistance with rights and incidents, return or deletion, and audit information. It must identify the processing's subject, duration, nature and purpose, the personal-data types, the categories of individuals and the controller's rights and obligations. Supplier staff assessment and independently selected quality research should be identified separately from quality checks performed solely for the institution. These distinctions determine who must justify each use and respond when a customer challenges it. (UK GDPR, Art 28(2)–(4), (9)–(10).)

Philippine processing and the foreign-data exception

The Philippine supplier needs a local privacy assessment even where servers remain in the UK. Access, consultation and use are processing activities. The Data Privacy Act's foreign-information exception is material: section 4(g) concerns information originally collected from residents of foreign jurisdictions in accordance with those jurisdictions' laws and processed in the Philippines. It must be applied to the information and purpose concerned. (Republic Act No 10173, ss 3(j) and 4(g).)

The implementing rules require proof of the foreign law relied on, preserve security requirements and limit non-application to what is necessary for the specified purpose. They retain data-subject rights, privacy principles and lawful-processing requirements except where directly incompatible with that purpose. A claim that all UK customer information is exempt would omit these conditions. The NPC's opinion concerning foreign financial records and overseas regulatory inspection supports a purpose-specific assessment; it is a fact-specific advisory opinion, not an exemption granted to this supplier. (DPA implementing rules, ss 5(f) and 6; NPC Advisory Opinion 2024-019, pp 2–4.)

Existing account records, new call recordings, derived vulnerability flags and supplier workforce records require separate treatment. New information is not automatically inside or outside section 4(g); the collection circumstances and legal conditions decide. Supplier model training also needs its own purpose assessment. Philippine sensitive personal information includes categories beyond UK special-category data, including certain government identifiers and education information. Where Philippine processing requirements apply, legitimate interests cannot justify sensitive or privileged information; an applicable section 13 condition is required. (Republic Act No 10173, ss 3(l), 4(g), 11–13 and 20; NPC Circular 2023-07, s 3(B).)

Where the outsourcing provisions apply, the contract must address processing locations, instructions, further processors, assistance, audits and return or deletion. Security duties remain material to foreign-data processing. The supplier should document its privacy impact assessment, endpoint access, remote-work controls, incident procedures and continuity arrangements. The NPC security circular expressly addresses these operational matters. (DPA implementing rules, ss 43–45 and 50; NPC Circular 2023-06, ss 5, 13–18, 21–22 and 29.)

Registration needs a system-specific decision under the applicable Philippine rules. NPC Circular 2022-04 requires registration where a controller or processor employs at least 250 people, processes sensitive information about at least 1,000 individuals, or processes data likely to pose a risk to rights and freedoms. Systems involving automated decision-making or profiling must be registered. The allocation rules distinguish the supplier's own platform from a system supplied by the client. The procurement response should contain current data protection officer (DPO) and system registration evidence, or a reasoned non-registration position tied to the actual processing and the scope rules above, including evidence of submission of the sworn declaration required by section 6 where applicable. Headcount below 250 is not a complete exemption. (NPC Circular 2022-04, ss 1, 5–7 and 26.)

Overseas access and model transfers

Access to identifiable customer information by the separate Philippine company creates a restricted transfer from the UK. The transfer occurs when the company accesses the information, even without downloading a file; the transfer mechanism must already be in place when access is made available. The UK data regulator's guidance expressly addresses overseas customer-service access to UK servers. The institution must therefore complete the transfer arrangement before enabling that access. (UK GDPR, Art 44A; ICO, Are we making a restricted transfer?, overseas remote-access guidance.)

The Philippines is not covered by UK adequacy regulations. For routine support, an appropriate route is a properly completed UK International Data Transfer Agreement (IDTA), or the relevant EU standard contractual clauses with the UK Addendum. The processing contract and transfer instrument serve different requirements. Signing either instrument without examining the real recipients and protection would not satisfy the current Article 46 test. (UK GDPR, Arts 44A and 46(1A); ICO, Is the restricted transfer covered by adequacy regulations?; IDTA, version A1.0, Part 4, paras 1.4 and 8.)

That test requires a reasonable and proportionate assessment that protection after transfer would not be materially lower than the UK statutory standard. It considers the likely circumstances, including the nature and volume of the information, and protection as a whole. The assessment should cover local legal obligations, public-authority access, enforceable remedies, security and restrictions on onward disclosure. A blanket customer consent clause does not establish this for continuous outsourcing. (UK GDPR, Art 46(1A), (6)–(8).)

The model arrangement needs a separate map of contracting entities, hosting, support access, logs, retention and onward recipients. A directly appointed model provider is not automatically the Philippine supplier's subprocessor. The party initiating each transfer must establish the applicable route; direct UK GDPR territorial application to an overseas supplier also needs its own assessment. Contractual onward-transfer protections remain necessary even where the overseas recipient is not directly subject to every UK GDPR provision. (UK GDPR, Arts 3, 28 and 44A; IDTA, Part 4, paras 16–17.)

The initial service should not send personal data to a model provider until the institution has approved those facts and controls. A provider that cannot identify processing destinations, prevent unapproved reuse or deliver the required assistance cannot support this proposed deployment. Philippine transfer accountability and the UK transfer requirements must both be addressed; the NPC's model-clause advisory does not make a particular Philippine form compulsory or replace the UK instrument. (DPA implementing rules, s 50; NPC Advisory 2024-01, ss 6–7.)

Recording, identity and AI disclosure

The contract should distinguish ordinary recording from biometric authentication. A voice file linked to a customer is personal data. Biometric data involve specific technical processing of physical, physiological or behavioural characteristics that allows or confirms unique identification. Processing those data to identify a person uniquely engages Article 9. A transcript can separately contain health information even where no biometric processing occurs. (UK GDPR, Arts 4(1)(14) and 9(1).)

The first release should use an approved non-biometric authentication route. Introducing voiceprints requires a separate necessity, security and Article 9 assessment. If explicit consent is the proposed condition, customers need a genuine choice and a suitable alternative. Vulnerability support must also use an applicable Article 9 condition where health information is involved. The DPA 2018's economic-wellbeing condition has specific limits; it is not permission to collect unrestricted health histories. Criminal-offence data have a separate route under Article 10 and domestic law. (UK GDPR, Arts 9–10; Data Protection Act 2018, s 10 and Sch 1, para 19; ICO, Biometric recognition, How do we process biometric data lawfully?, consent guidance.)

The institution should document recording authority for its actual telephony system. UK interception law separately addresses the private-system controller exception and consent by the sender and intended recipient. The private-system exception removes the section 3 offence but does not itself establish lawful authority; interception may still be actionable under section 8. Where the institution relies on the business-monitoring regulations, capture must occur by or with the system controller's express permission. The interception must be solely for a permitted monitoring or record-keeping purpose concerning communications relevant to the controller's activities. The system must be provided wholly or partly for those activities, and the controller must make all reasonable efforts to inform users of possible interception. A generic reference to quality assurance does not establish those conditions. (Investigatory Powers Act 2016, ss 3(2), 8 and 44(1); SI 2018/356, regs 3 and 4(1), as amended.)

Philippine Republic Act No 4200 separately prohibits unauthorised secret recording or interception of private communications and addresses handling unlawfully obtained recordings. For capture through Philippine personnel, devices or recording arrangements, the proposed design should obtain clear authorisation from all participants before recording or transcription and offer an unrecorded support route. It should cover a human joining the call and any local duplicate. A UK server location does not by itself establish where capture occurs or who controls it. Access to a recording captured wholly in the UK does not, without further facts, establish that the Philippine recording prohibition applies. (Republic Act No 4200, ss 1–2.)

The opening should identify the automated assistant in plain language. Accessible privacy information must also explain the applicable purposes, lawful bases, recipients, transfer safeguards, retention and rights. Concealment can breach consumer law if it makes the practice misleading and is likely to cause the average consumer to take a different transactional decision. The Competition and Markets Authority (CMA) advises disclosure in that setting. Its AI-agent guidance applies consumer law and does not create a separate universal AI disclosure statute. (UK GDPR, Arts 12–13; FCA PRIN 2A.5.3R; Digital Markets, Competition and Consumers Act 2024, ss 225–227; CMA, Complying with consumer law when using AI agents, 9 March 2026.)

Retention, rights and security

The institution should set separate retention periods for audio, transcripts, complaint evidence, prompts, security logs and backups. Each period needs its own purpose and legal basis. The PSRs' five-year requirement for relevant compliance records does not establish that every recording must be kept for five years. The contract should implement deletion, restricted legal holds and a testable return or deletion process at exit. (UK GDPR, Arts 5(1)(c), 5(1)(e) and 28(3)(g); PSRs, reg 31.)

Access requests can reach identifiable recordings, transcripts and prompts. The institution must perform the required reasonable and proportionate search and protect others' rights when supplying information. Supplier delay does not create an unlimited extension. The ordinary period is one month from the relevant time, which can await necessary identity information. An extension of two further months requires necessity because of the requests' complexity or number, with timely notice and reasons. Reasonably required clarification of an access request can pause the applicable period. The contract should require retrieval quickly enough for the institution to meet that clock. (UK GDPR, Arts 12(6), 12A(1)–(5) and 15(1A), (4).)

A customer can also complain about the processing itself. Since 19 June 2026, the controller complaint duty requires facilitation, acknowledgement within 30 days, appropriate enquiries and an outcome without undue delay. That process is distinct from financial-service complaint deadlines. A call about disclosure of account data may require both routes, so the longer privacy acknowledgement period must not displace the payment complaint clock. (Data Protection Act 2018, s 164A; SI 2026/82, regs 3 and 7.)

The institution should require a completed data protection impact assessment before deployment. Article 35 makes this mandatory where processing is likely to create high risk; the ICO's list addresses innovative technology combined with further risk criteria. Account access, vulnerable-customer information and automated evaluation make a documented assessment particularly relevant here. If residual high risk requires prior consultation, that step precedes processing. (UK GDPR, Arts 35–36; ICO, Examples of processing likely to result in high risk, innovative-technology entry.)

Access enforcement should sit outside the language model. The proposed controls include customer-specific retrieval permissions, least-privilege staff accounts, managed endpoints, encryption, audit logs and tested separation between customers. Tests should attempt to obtain another person's data, override approved instructions and extract secrets through prompts. These are recommended implementations of risk-appropriate security, not a statutory promise that AI will never make an error. (UK GDPR, Art 32; NPC Circular 2023-06, ss 13–18, 29 and 32.)

Outbound marketing and collection calls

Outbound use requires its own approval because both the purpose and calling technology change the legal analysis. PECR regulation 19 addresses direct-marketing communications comprising recorded matter through an automated calling or communication system. Its automated-calling definition concerns systems capable of automatically initiating a sequence to multiple destinations under stored instructions and transmitting sounds that are not live speech. Those elements must be tested against the actual dialler, cached audio and speech-generation process. (PECR, reg 19(1)–(4).)

The ICO has addressed an AI-synthesised recorded greeting lasting three to five seconds before a human handler takes over. It treats that marketing call as requiring the subscriber's specific prior consent under regulation 19. The example supplies a strong adverse case for recorded segments within an otherwise conversational system. It does not establish that every wholly dynamic generative conversation has the same legal classification. The proposed contract should prohibit automated marketing until that architecture and the required permission are established. (ICO, Innovation advice, previously asked questions, AI-produced greeting and regulation 19.)

Ordinary live unsolicited marketing calls require screening against prior objections and the applicable telephone preference registers, subject to the subscriber's specific permission and the statutory conditions. Existing customer status does not create a general exemption. Caller identification and number-display rules also apply. A UK GDPR lawful basis cannot displace PECR consent where regulation 19 requires it, and direct-marketing objections must be honoured. (PECR, regs 19, 21 and 24; UK GDPR, Art 21(2)–(4).)

The institution should approve promotional content and retain records of the intended audience, permissions, suppression checks and script versions. For its retail customers, communications remain subject to the Consumer Duty's understanding requirements. A campaign promoting a controlled investment or activity also requires the applicable financial-promotion analysis; payment-institution status alone does not settle that question. The overseas origin of a communication does not remove section 21 where it is capable of having an effect in the UK. (FCA PRIN 2A.5.1R–2A.5.3R; Financial Services and Markets Act 2000, s 21(1)–(3), (8)–(9).)

Genuine billing, payment-failure and payment-difficulty messages can be service communications. Adding promotion or refinancing solicitation can change their purpose. The institution remains responsible as an instigator when it commissions a marketing contractor. Collections should therefore use a separate approved purpose and script, without hidden cross-selling. (ICO, Electronic and telephone marketing, service messages and instigation; ICO, Direct marketing and regulatory communications, billing and financial-support examples.)

Debt collection also raises a separate financial-services boundary. FCA guidance identifies steps to procure payment under relevant credit or consumer-hire agreements as a regulated activity. If the proposed work falls within the consumer-credit rules, CONC imposes specific contact, identity and third-party confidentiality requirements. Those rules should not be imported automatically into every unpaid payment-account fee. Before any collections release, the parties should identify the debt, agreement, creditor, supplier function and applicable permission route. (FCA PERG 2.7.8DG; CONC 7.1.1R, 7.9.1R, 7.9.4R, 7.9.6R, 7.9.7R and 7.9.10R.)

Control of changes and subcontractors

The contract should make the institution responsible for approved customer content, access policy, financial decisions and acceptance of material service changes. The Philippine supplier should operate the approved configuration, control its staff and disclose proposed changes to prompts, retrieval sources, tools and subcontractors. The model provider must supply enforceable commitments through the relevant contracting party. A direct model contract requires coordinated obligations across both suppliers. (PSRs, reg 25(2); UK GDPR, Art 28(2)–(4); EBA/GL/2019/02, paras 74–80.)

Changes should be assessed by effect. A model update that alters complaint recognition, retention, access or output behaviour can be material even where the advertised product name stays the same. The agreed process should require notice, testing against approved cases, acceptance criteria, version records and a workable rollback. Unannounced upstream changes need an escalation and suspension mechanism. The institution should receive evidence of missed complaints, wrong answers, failed handovers and customer harm alongside service availability. (FCA PRIN 2A.5.10R and 2A.8; EBA/GL/2019/02, paras 100 and 104.)

Audit and regulatory access must reach the service's real dependencies. For important outsourcing, the EBA guidelines address access, information and audit rights, including subcontracting. Certifications and pooled audits can assist assurance, but should not make direct access ineffective when the institution or regulator needs it. The parties should resolve overseas access restrictions and arrange usable evidence before contracting, with suspension or exit if necessary access cannot be provided lawfully. (PSRs, reg 25(2); EBA/GL/2019/02, paras 75, 87–93; UK GDPR, Art 28(3)(h).)

A failed call and the response it requires

Suppose the assistant discloses another customer's account information, gives a misleading fee explanation and fails to recognise the caller's dissatisfaction. The disclosure is a personal-data breach. The fee explanation can breach customer-communication duties without itself being a data breach. The missed complaint can cause a separate failure of handling and response times. Each requires its own assessment and remedy. (UK GDPR, Art 4(1)(12); FCA PRIN 2A.5.3R; DISP 1.3.1R and 1.6.2AR.)

The supplier should immediately stop the affected retrieval or answering function, preserve the relevant records and alert the institution. The institution should restore a safe support route, correct the explanation and register the complaint at its original receipt time. It should check similarly affected calls and decide whether charges, losses or other harm require correction or redress. The Consumer Duty requires appropriate action when foreseeable harm becomes apparent through monitoring or another source; a complaint from every affected customer is not a prerequisite. (FCA PRIN 2A.2.5R; DISP 1.4.1R; UK GDPR, Arts 32–33.)

A processor subject to UK GDPR must notify the controller without undue delay after awareness. The processing and transfer contracts should impose the same duty on the Philippine supplier. The institution must notify the data regulator without undue delay and, where feasible, within 72 hours of awareness, unless the breach is unlikely to create a risk to individuals. High risk can require notice to affected individuals without undue delay, subject to Article 34's conditions and exceptions. All breaches and the reasons for the response must be documented. (UK GDPR, Arts 28(3)(f) and 33–34; IDTA, Part 4, para 15.2.1.)

The Philippine notification test is distinct. Where those rules apply, notification is required when the breach involves sensitive information or information enabling identity fraud, there is reason to believe it may have been acquired by an unauthorised person, and that acquisition is likely to create a real risk of serious harm. The controller remains responsible for notifying the NPC and affected individuals even where processing is outsourced. The rules require notification within 72 hours of knowledge or reasonable belief by the controller or processor, subject to their limited delay and exemption provisions. The supplier cannot use that period as a contractual delay before informing the institution. Pending requests for relief do not themselves suspend compliance. (NPC Circular 16-03, ss 11 and 15–18; NPC Advisory 2026-02, s 2(C).)

The institution must separately assess whether the event is a major operational or security incident under the PSRs. Contractual incident categories should capture all these possibilities and require prompt evidence sharing. A report to one regulator does not answer the other applicable tests. Restart should follow containment, correction and evidence that the identified failure no longer defeats the approved controls. (PSRs, regs 98–99; UK GDPR, Arts 32–34.)

Contract allocation and the launch decision

The commercial agreement should allocate losses by responsibility and causation, including incorrect institution content, supplier configuration defects, unauthorised staff access and model-provider breaches. It should distinguish customer redress, incident response costs and claims between the parties. Negotiated caps and insurance require separate treatment from statutory duties and mandatory transfer terms. Neither an AI disclaimer nor a supplier indemnity removes the institution's PSR responsibility. (PSRs, reg 36; UK GDPR, Arts 28(4) and 82.)

Data-protection compensation depends on the applicable infringement, damage and responsibility tests. Under Article 82, a processor is liable for damage where it breaches processor-specific obligations or acts outside or contrary to lawful instructions. Contractual contribution cannot reduce a customer's statutory rights. The agreement should preserve evidence and cooperation for claims, without promising that every regulatory penalty is transferable or insurable. Governing law, dispute forum, service of proceedings and recoverable assets should be chosen for the actual counterparties; selecting a contract law cannot disapply mandatory regulatory duties. (UK GDPR, Art 82(1)–(5); IDTA, Part 4, paras 6.4–6.7.)

Exit must be practicable before service begins. The institution needs customer records, complaint histories, approved content, configuration information and sufficient rights to maintain or replace the service. The contract should require an orderly transition, continued assistance and verified return or deletion, with defined legal-retention exceptions. Model dependence should not leave the institution unable to answer customers when the commercial relationship ends. (EBA/GL/2019/02, paras 98–99 and 106–108; UK GDPR, Art 28(3)(g).)

The proposed initial release should proceed only after the institution accepts the function map, outsourcing assessment, applicable notification, data contracts, transfer assessment and tested human route. The supplier should provide its Philippine privacy position, recording design and operational evidence. Payment tools and outbound campaigns remain disabled under that release. These are contractual acceptance conditions derived from the duties analysed above, not a representation that a regulator has approved the hypothetical service. (PSRs, regs 25 and 36; UK GDPR, Arts 28, 35 and 46; DPA implementing rules, ss 5–6 and 44.)

The institution should require suspension of the affected function when customer isolation fails, escalation ceases to work or unapproved processing appears. A new country, model provider, reuse purpose, voiceprint, payment power or outbound campaign should trigger the relevant permission and data review before activation. The right to stop, correct and replace the service must remain effective throughout operation. (PSRs, regs 25(2), 34 and 98; UK GDPR, Arts 28, 32 and 35(11); EBA/GL/2019/02, paras 98 and 106.)