In most businesses, outsourcing customer support is a question of cost, quality and speed. In a regulated industry it is also a question of who is accountable when something goes wrong. A lender, an insurer, a payments firm, a health administrator or a university that hands customer contacts to an outside team still answers to its customers and its regulator for what that team says and does. That does not make outsourcing impossible. It makes it a matter of design.
This guide explains how to think about customer support in regulated industries when a partner is involved. It sets out the principle that runs through almost every regulatory regime, the themes that regulators in different countries share, a way to decide which contact types can move and which must stay with authorised staff, sector-by-sector notes, the safeguards that make outsourced support safe (scripts, identity checks, complaints, vulnerable customers, call recording, data), a due diligence checklist, contract clauses, oversight and exit. There is a readiness checklist, a risk grid and a glossary for every technical term.
What Does "Regulated" Mean For Customer Support in Regulated Industries?
Support teams in regulated industries touch the rules in at least six ways:
- Conduct. How customers are treated: fairness, clarity, no misleading statements, support for people in difficult circumstances.
- Advice and decisions. Who may explain, recommend or decide things such as eligibility, pricing, claims, clinical matters, admissions or immigration status.
- Complaints. How complaints are recognised, recorded, handled and reported, often within set timescales.
- Data. How personal and special categories of data are collected, used, shared and protected.
- Records. What must be kept (call recordings, notes, decisions) and for how long.
- Suppliers. How the firm chooses, contracts with, monitors and, if necessary, leaves the companies it relies on.
The Core Principle: You Cannot Outsource Accountability
Across financial services, health, data protection and many other regimes, the same idea appears in different words: a firm that outsources an activity remains responsible for it. In the UK, for example, the Financial Conduct Authority's outsourcing rules (SYSC 8) say that outsourcing does not change the firm's obligations to customers and the regulator. The US interagency guidance on managing risk in third-party relationships takes a similar line, as do data protection laws that keep the controller responsible for the processors it uses.
In practice, this means four things for support:
- Choose carefully. You must be able to show that you checked the partner before you relied on it.
- Write it down. A contract and written procedures set out what the partner may and may not do.
- Watch it. Ongoing oversight, not just a signature at the start.
- Be able to leave. If the partner fails, you need a way to carry on serving customers.
A Working Model: Prepare, Check, Decide
A helpful way to apply the principle to day-to-day work is to split support tasks into three roles:
- Prepare: gather, organise and present information. For example, collect a customer's documents, fill a checklist, summarise a case, draft a reply for approval.
- Check: verify that what has been collected is complete and consistent with a written standard. For example, confirm that a form is signed, that the name matches, that all pages are present.
- Decide: make a judgement, give advice, approve, refuse, price, diagnose or promise.
A partner can often take the first two under your instructions, with your staff keeping the third. This is how we approach regulated work at Connecgen: we prepare and check, you decide. We do not give financial, medical, legal, visa or admissions advice, and we follow your scripts and escalate decisions to you.
What Regulators Typically Expect of Firms That Outsource
Rules differ, but regulators in different countries tend to expect the same ten things when a regulated firm relies on a supplier. Use this table as a checklist of questions for your own compliance team, not as a statement of any particular rule.
| Theme | What regulators commonly expect | A question to ask |
|---|---|---|
| Responsibility | The firm stays responsible for outsourced activity | Who is accountable in our firm for this supplier? |
| Due diligence | Checks before relying on a supplier, recorded | What evidence did we collect, and when? |
| Written agreement | A contract that sets out services, standards and rights | Does it cover audit, sub-outsourcing, incidents and exit? |
| Oversight | Continuing monitoring in proportion to risk | What do we review, how often, and who signs off? |
| Regulator access | The regulator can obtain information and, where required, inspect | Does the contract give us and the regulator access? |
| Sub-outsourcing | Controls on the supplier passing work on | Who else touches our customers' data? |
| Data protection | Lawful, secure handling by processors under written terms | Do we have processing terms and security evidence? |
| Complaints and conduct | Fair treatment, complaints recognised and handled on time | How do we know complaints reach us on time? |
| Records | Required records kept, retrievable and secure | Where are recordings and notes and who can reach them? |
| Resilience and exit | Tested continuity plans and a way to leave | What do we do if the supplier fails tomorrow? |
Public sources worth reading are listed at the end of this guide. They include the UK Financial Conduct Authority's outsourcing rules (SYSC 8), its guidance on the fair treatment of vulnerable customers and its complaints rules (DISP 1), the US Federal Reserve's interagency third-party risk management guidance (SR 23-4), the health privacy guidance on business associates from the US Department of Health and Human Services, the UK Information Commissioner's Office guidance on contracts between controllers and processors, and industry guidance on protecting telephone-based payment card data. In the European Union, financial firms may also face the Digital Operational Resilience Act (DORA), which applies to ICT third-party risk. Whether it applies to a given support arrangement is a question for your adviser.
Customer Support in Regulated Industries: Which Contact Types Can Move?
Not all support contacts carry the same regulatory risk. A practical way to decide is to place each contact type on a grid of two questions:
- How much judgement does it need? Following a script, or weighing a situation?
- How serious is the harm if it goes wrong? Minor inconvenience, or financial loss, health risk, legal consequence or distress?
- Bottom left (low judgement, low harm): the easiest candidates to outsource under scripts and sampling. Examples: opening hours, how to find a form, appointment booking, order status.
- Top left (low judgement, higher harm): can be outsourced with strict scripts, hard-coded checks and high review. Examples: collecting documents for an application, identity checks that follow a fixed procedure, taking card details through a secure method.
- Bottom right (more judgement, low harm): can work with skilled agents and good knowledge. Examples: explaining a general process in plain language, handling a frustrated customer.
- Top right (high judgement, higher harm): keep with authorised staff. Examples: giving advice, deciding eligibility, assessing a claim, discussing symptoms or treatment, interpreting a legal position, deciding a complaint outcome.
A Decision Path For One Contact Type
Sector by Sector: What Changes
The notes below describe themes, not rules. Check the current rules for your country and sector with your adviser.
| Sector | A partner can often | Stays with authorised staff |
|---|---|---|
| Banking, lending, payments | Answer information queries, chase documents against a checklist, log complaints | Credit and affordability decisions, product recommendations, complaint outcomes |
| Insurance | Answer policy questions from approved documents, collect claim information, book appointments | Coverage and claims decisions, pricing, suitability advice |
| Health administration | Book and change appointments, send reminders, collect forms, answer admin questions | Symptoms, diagnosis, treatment, medication, clinical triage |
| Education and admissions | Explain deadlines and documents, chase missing items, book calls and tours | Admissions decisions, advice on whether to apply or accept, visa and immigration advice |
| Telecom, utilities, energy | Billing questions from approved material, outage updates, meter readings, complaint logging | Disconnection decisions, debt and payment arrangements |
| Travel and hospitality | Booking changes within rules, status updates, approved information | Entry requirements, visas, legal rights advice |
Banking, Lending and Payments
Financial firms face rules on outsourcing, conduct, complaints, vulnerable customers, record-keeping and the line between giving information and giving advice. A partner can typically take first-line enquiries (opening hours, how to use online banking, where a payment is, how to make a complaint), collect documents for an application against a checklist, and record complaints for your complaints team to handle. Credit decisions, affordability judgements, product recommendations and complaint outcomes stay with authorised staff.
Where card payments are taken by phone, industry guidance on protecting telephone-based payment card data sets out ways to keep card numbers out of recordings and out of agents' reach, such as masking the keypad tones so the agent never hears or sees the digits. Ask any partner exactly how card data is handled, and prefer methods in which agents never see the full number.
Insurance
Typical themes: clear and fair information, fair claims handling, vulnerable customers, record-keeping and complaints. A partner can handle policy questions answered from approved documents, collect claim information against a checklist, chase documents and book appointments. Coverage decisions, claims decisions, pricing and advice on whether a product suits someone stay with authorised staff.
Health Administration
Typical themes: privacy of health information, minimum necessary use, patient safety and no clinical advice. In the United States, health privacy rules require service providers that handle patient information to sign a business associate agreement, and the Department of Health and Human Services publishes guidance. In the UK and EU, health data is special category data under data protection law with stricter conditions. A partner can book and change appointments, send reminders, collect forms, answer administrative questions (location, opening hours, what to bring) and route clinical questions to qualified staff. It must not discuss symptoms, diagnosis, treatment or medication, and agents should have access only to what each task needs.
Education and Admissions
Typical themes: student data, fair treatment of applicants, accuracy of information and safeguarding. A partner can answer questions about deadlines, documents and process, chase missing documents and book campus tours or calls. It must not advise on whether a student should apply, accept or choose a course, give visa or immigration advice, or make admissions decisions. Those stay with admissions staff and qualified advisers.
Telecom, Utilities and Energy
Typical themes: clear pricing information, fair complaints handling, support for people who are vulnerable or in difficulty, and, for telecom, rules about marketing calls. A partner can handle billing questions from approved material, meter readings, outage updates, appointment booking and complaint logging. Disconnection decisions, debt arrangements and agreements about payment plans stay with authorised staff under your policy.
Travel and Hospitality
Typical themes: accurate information, refunds and cancellation rights, consumer protection and data. A partner can handle booking changes within your rules, status updates and information from approved sources. Entry requirements, visas and legal rights are specialist areas: agents should point customers to official sources and your own staff rather than give advice.
Safeguards That Make Outsourced Support Safe
Whatever the sector, the same set of safeguards turns "we hope the partner gets it right" into "we can show how it is controlled".
1. Written Scripts and Approved Content
- Agents answer from approved content, not from memory or guesses.
- Every script has an owner, a version and a review date, and old versions are withdrawn.
- Compliance signs off changes before they reach agents.
- Agents know what they must never say: the boundary of information versus advice, and prohibited promises (such as predicting outcomes or guaranteeing a decision).
- Where a customer asks for something outside the script, the instruction is simple: say what you can do, offer to pass the question to a person who can help, and use the escalation route.
2. the Information-Versus-Advice Line
The line between explaining and recommending is one of the most important in regulated support. A short rule that works well: agents may explain how something works and what the options are, as written in approved material. They may not say which option a customer should choose, whether the customer is eligible, or what will happen in their case. Give agents examples of each side and test them in training.
3. Identity and Authority Checks
Before discussing a customer's account, agents need to be sure who they are talking to and whether that person is allowed to ask. Write the exact steps and make them hard to skip: which questions, how many must be right, what to do when someone fails, how to deal with a third party acting for the customer (family member, carer, legal representative). Build the steps into the tool where possible, so that the system will not show account details until they are done.
4. Complaints: Recognise, Record, Route
A partner's most important role in complaints is to recognise them, record them completely and route them on time. Teach agents what counts as a complaint under your definition, how to acknowledge it, what to log and how to pass it on. The investigation, the decision and the final response stay with your complaints team. Track how fast complaints reach you, and sample calls to see whether any were missed.
5. Vulnerable Customers
Agents need to recognise signs, respond with care and know when to hand over. This is not about diagnosing anyone. It is about noticing and responding.
| Signs an agent may notice | What the agent does | Escalate when |
|---|---|---|
| Confusion, repeated questions, difficulty following | Slows down, uses plain words, offers to repeat or send in writing | The customer cannot understand important information |
| Mentions of illness, bereavement, job loss, separation | Responds with care, avoids pressing, notes it as sensitive | The matter touches payments, claims or deadlines |
| Distress, anger or fear | Stays calm, acknowledges, offers a call-back with a specialist | The customer says they are at risk or cannot cope |
| Someone speaking for the customer | Follows the authority check, does not assume | Authority is unclear or the customer seems pressured |
Give agents a short, plain procedure, and let them make a note and escalate without needing to be sure. Do not ask agents to collect more sensitive information than needed, and make sure the notes are handled as sensitive data.
6. Call Recording, Notes and Records
Many regimes require firms to keep records of customer interactions for a set time. Agree who records, where recordings are stored, who can listen, how long they are kept and how they are deleted. For payments, check that card details do not reach recordings. For health or other sensitive data, restrict access to recordings. Make sure recordings and notes can be produced quickly if the regulator or a customer asks.
7. Data Minimisation and Access
Give agents access to the minimum data they need to do each task. Hide or mask what they do not need (for example, show the last four digits of an account number rather than all of it). Ban copying data into other tools. Log access and review it. Our guide to protecting customer data when you outsource support goes through the controls in detail.
8. Training and Competence
Agents need training, tested and recorded, in: your products and processes, the information-versus-advice line, complaints, vulnerable customers, data protection, financial crime awareness where relevant, and escalation. Refresh regularly and after any incident. Keep records of who was trained on what and when. Where regulation requires particular competence for certain tasks, keep those tasks with people who hold it.
9. Quality Assurance and Monitoring
Use a higher sample rate than in an unregulated programme, at least at first, and design the scorecard to include compliance points as critical failures. Review conversations about complaints, vulnerable customers and any statements about product features with extra care. Both sides score the same conversations in calibration sessions. See customer support metrics that matter for how to build a fair scorecard.
10. Incident Management
Agree what counts as an incident (a data breach, a wrong statement, a missed complaint, an outage), who is told, how quickly and what is delivered afterwards (a written report with cause and fix). Practice it once before you need it. In several regimes, firms must report certain incidents to the regulator or to affected people within set timescales, so the partner's notice to you must be fast enough for you to meet those duties.
11. Fraud and Social Engineering Awareness
Support teams are a favourite target for people trying to take over accounts or extract data. Agents should know the common signs: callers who push for urgency, who cannot answer identity questions but want a change anyway, who ask to change contact details or payment details right after a failed check, or who call about many accounts. The rule is simple and must be easy to follow: if identity checks are not passed, no account information is given and no change is made, however convincing or distressed the caller sounds. Give agents a no-blame way to report suspicious contacts. The UK government's cyber security agency and the US cyber security agency publish plain guidance on social engineering that is useful training material.
12. Requests About Personal Data
Customers may ask to see, correct or delete the data you hold about them, or to object to its use. Data protection laws in many countries give them rights and set timescales for a response. Agents must recognise these requests, even when the customer does not use legal words, record them completely and route them to the right team at once. As with complaints, the partner recognises, records and routes. Your own team decides and responds.
13. Sales and Marketing Contacts
Where a partner makes or takes sales-related contacts, regulated sectors add rules on consent, do-not-call lists, pressure, claims about products and suitability. Use consent-led, script-led outreach, record consent, honour opt-outs immediately and keep selling separate from advice. Agents must not suggest that a product suits a particular person unless a suitably authorised person has made that judgement. See what sales support teams do for how we approach it.
14. Automation and AI Assistance
Tools that suggest replies or summarise conversations can help agents, but in regulated work they raise their own questions. Suggested replies must come from, or be checked against, approved content. A human should check anything that goes to a customer where accuracy matters. Summaries should be checked before they are saved as the record. Systems that generate text should not be allowed to give advice or make promises. Ask any partner which tools they use, what data goes into them, where it is processed and how outputs are checked, and record the answers in your due diligence.
A Training Curriculum For Regulated Support
| Module | What it covers | How it is assessed | Refresh |
|---|---|---|---|
| Products and processes | How your products work, what customers ask | Quiz and practice cases | At each product change |
| Information versus advice | The line, with examples on both sides | Scenario test, scored on the real scorecard | Every six months and after incidents |
| Complaints | Definition, recognising, recording, routing and timing | Practice calls and logs | Every six months |
| Vulnerable customers | Signs, responses, escalation | Role-play and observed contacts | Every six months |
| Data protection and security | Access rules, clear desk, reporting incidents, requests about data | Test with a pass mark | Every year, plus at joining |
| Fraud and social engineering | Common tricks, identity checks, reporting | Scenario test | Every year |
| Escalation and handover notes | When to escalate and what to write | Sampled notes | Ongoing sampling |
Whatever the content, measure competence, not attendance: a short test, a practice case scored on the real scorecard and sampled live conversations. Record the results. Where a task needs a specific qualification, keep it with qualified people.
A Scorecard With Compliance Built in
A quality scorecard for regulated work should treat some failures as automatic. Agree the scorecard before go-live and calibrate it with both teams.
| Area | Example treatment |
|---|---|
| Accuracy and completeness | Weighted score |
| Process followed | Weighted score, with identity check steps as a must-pass |
| Tone and care | Weighted score, including how vulnerable customers were handled |
| Complaint recognised and routed | Must-pass: a missed complaint fails the conversation |
| Information versus advice | Must-pass: advice given fails the conversation |
| Data handling | Must-pass: data shared with the wrong person fails the conversation |
| Misleading or false statement | Must-pass: any false statement fails the conversation |
Due Diligence: Checking a Partner Before You Rely on It
Regulators commonly expect to see that a firm checked a supplier before using it and checked again at intervals. Make a written record. A practical structure covers eight areas.
- Experience and capability. Has the partner handled similar work for firms in your sector? Can it explain the rules that affect your contacts in its own words, and show how it trains for them?
- People. How are agents recruited and checked (where lawful and appropriate)? What training and competence records exist? What is attrition, and how is knowledge kept when people leave?
- Controls. How are scripts managed? How is the information-versus-advice line enforced? How are complaints, vulnerable customers and incidents handled?
- Security and data. What can agents see? How is access controlled and reviewed? Where is data stored and processed? What independent assurance exists, with what scope and date?
- Financial and operational resilience. Is the partner stable enough to deliver for the contract term? What is the continuity plan and when was it last tested?
- Sub-contractors. Does the partner use others for any part of the work? Who, doing what, with what access?
- Culture and openness. How does the partner handle mistakes? Will it tell you quickly when something goes wrong?
- References. Can you speak to clients in similar sectors, including ones who have left?
Our guide on how to choose a support outsourcing partner has a bank of questions you can adapt, and a scorecard for comparing providers.
The Contract: Clauses Regulated Firms Usually Need
Have your lawyer and compliance team draft or review the contract. The following topics commonly need to be covered. This is a checklist, not legal advice.
| Clause | What to settle |
|---|---|
| Scope and standards | Services, scripts, service levels, quality and compliance standards |
| Audit and access | Your rights and, where required, your regulator's, to information and inspection |
| Sub-outsourcing | Your prior consent, flow-down of terms, and a list of sub-contractors |
| Data protection | Processing terms, location, security measures, deletion and return |
| Incident notice | Fast notice, content of the report, cooperation with you and regulators |
| Records | What is kept, where, for how long, who can access, how it is produced |
| Continuity | Tested plans, recovery times, fallback arrangements |
| People and training | Competence, training records, key-person provisions |
| Exit | Notice, return of data and knowledge, handover help, costs |
| Liability and insurance | Limits, cover and responsibilities if something goes wrong |
Oversight After You Sign
Controls on paper are not enough. Regulators generally expect continuing oversight proportionate to the risk. A sensible rhythm:
- Daily or weekly: volumes, complaints logged and routed, escalations, incidents, quality samples, critical failures.
- Monthly: formal service review with management information: quality, compliance sampling results, training status, access review, staffing.
- Quarterly: risk review: changes to scripts, rules, products; outcomes for vulnerable customers; incidents and lessons; continuity test results.
- Annually: full due diligence refresh, contract review, security and assurance review, and an exit plan test.
Keep minutes and action lists. In a regulated firm, a record that you looked, found something and fixed it is stronger evidence than a record that nothing was ever found.
Business Continuity and Exit
Two questions every regulated firm should be able to answer: what happens if the partner cannot deliver tomorrow? And how do we leave if we must?
- Continuity: the partner has a tested plan for site loss, system failure, staff shortage and pandemic-type disruption. You know how long recovery takes and what you will do meanwhile.
- A fallback: a way to take critical contact types back, for example your own staff trained for the top contact types, or a second provider for overflow.
- Exit plan: written steps, timings and costs for returning data, scripts, recordings and knowledge, and for continuing service during the handover.
- Test it: at least a desktop test of the exit plan, and an actual test of fallback for critical contacts.
A Worked Example: a Consumer Lender
| Contact type | Who handles it | Main controls |
|---|---|---|
| Balance and payment queries | Partner | Approved script, system-led identity check, sampling |
| Document chasing for applications | Partner | Checklist, no comment on the outcome |
| Change of contact details | Partner | Identity steps built into the tool |
| Hardship requests | Partner recognises, records and routes. Lender's team handles | Vulnerable-customer prompt, routing in a set time |
| Complaints | Partner recognises, records and routes. Lender's team decides | Definition and log, timeliness reporting |
| Eligibility questions | Lender's authorised team | Partner offers a call-back and passes the question on |
What makes this work in practice:
- Approved scripts for each contact type, owned and versioned by compliance.
- Identity checks built into the system so that account details are hidden until steps are complete.
- A recognise-record-route procedure for complaints and hardship, tested with practice cases.
- Vulnerable-customer prompts and a one-click escalation.
- Higher sampling at first, with compliance critical failures built into the scorecard.
- A supervised pilot on the simplest contact types, followed by a phased scale-up using the gates in our 90-day support transition plan.
- Monthly service reviews and quarterly risk reviews minuted by the lender.
Try It: Is Your Regulated Outsourcing Ready?
Tick what is true today. The result is a prompt for a conversation with compliance and your adviser, not a compliance assessment.
Where the Team Sits: Location and Data Transfers
Where agents work matters in regulated sectors for three reasons. Data: some laws restrict transfers of personal data to other countries, or require safeguards such as approved contract terms. Access for oversight: your regulator may expect to be able to obtain information and, where required, to inspect, wherever the work is done. Language and context: agents need to communicate clearly in your customers' language and understand the rules that apply to them. None of this rules out any location. It means that location is a question for your compliance team and your adviser early in the process, not after signing. Our guide to protecting customer data when you outsource support goes through cross-border questions.
What to Tell Your Regulator
Whether you must notify, or seek approval from, your regulator before outsourcing support depends on the rules that apply to you and on how important the outsourced activity is. Some regimes require notice for outsourcing of critical or important functions. Others do not. Ask your compliance team early. If notice is needed, plan the timing, because regulators may ask questions. Even where it is not required, keep a clear internal record of the decision, the risk assessment and the due diligence, so that you can explain it if asked.
Myths and Facts
| Myth | Closer to the facts |
|---|---|
| "If we outsource it, the supplier is liable." | You usually remain responsible to customers and regulators. A contract can shape who bears costs, but not who is accountable to the regulator. |
| "A certificate means we are covered." | A certificate shows an audited management system for a defined scope at a point in time. It is one piece of evidence next to your own checks. |
| "Recording everything is always safer." | Recordings are a record, and also a risk. Capture what you must, keep sensitive data out where possible and control access. |
| "Scripts make agents robotic." | Good scripts set boundaries and give agents confident, plain wording. Agents still adapt tone and listen. |
| "Only sales calls are risky." | Service calls can involve complaints, vulnerable customers, personal data and fraud attempts. |
| "Once the pilot is approved, we can relax." | Oversight must continue. Regulators expect ongoing monitoring in proportion to risk. |
A Phased Approach For Regulated Firms
A regulated start follows the same shape as the plan in our 90-day support transition plan, with four additions:
- Compliance sign-off before day one: risk grid, scripts, contract, due diligence record.
- Higher review rates and compliance critical failures from the first live contact.
- Compliance in the gate reviews, with the power to hold volume.
- A named regulatory contact on each side, and a tested incident route.
Start with the lowest-risk contact types, prove the controls work, and only then widen scope.
Common Mistakes
- Assuming the partner takes the responsibility. It does not, in most regimes.
- Outsourcing before mapping contact types to risk. Start with the grid.
- Vague scripts. Agents fill gaps with guesses.
- No clear information-versus-advice rule. Train it with examples and test it.
- Missed complaints. Agents hear dissatisfaction and do not log it.
- Weak identity checks. Build them into the system.
- Treating vulnerable-customer handling as an afterthought. Train and prompt it.
- Over-broad access. Give each person the minimum.
- No audit or exit rights in the contract.
- Stopping oversight after the pilot. Keep the rhythm going, and refresh due diligence yearly.
Putting It All Together
Customer support in regulated industries can be outsourced safely when you design the work around the principle that accountability stays with you.
- You remain responsible, so choose carefully, contract clearly, oversee actively and be able to leave.
- Prepare, check, decide: a partner can prepare and check under your scripts, while authorised staff decide and advise.
- Use a risk grid to place each contact type, with compliance involved, and write down why.
- Build the safeguards: approved scripts, an information-versus-advice rule, identity checks, complaint recognition, vulnerable-customer procedures, call recording, data minimisation, training, higher sampling and incident management.
- Check the partner with evidence across people, controls, security, resilience, sub-contractors and references.
- Cover the key clauses in the contract, including audit rights, sub-outsourcing, incident notice, continuity and exit.
- Oversee on a rhythm, from daily checks to an annual refresh.
- Pilot first, then scale in gates.
- Take advice from your own lawyers and compliance team. We prepare and check. You decide.
We run customer support and sales support for businesses, so we write from the day-to-day work. This guide is general information, not legal, financial, medical or compliance advice. Rules differ by country and change, so check what applies to you with your own advisers. We list our sources at the end. If you spot something out of date, write to info@connecgen.com.


