AI Agents for Geneva Private Banks: a Compliant 2026 Playbook
Private banks in Geneva face strict rules, international clients and high reputational stakes. A practical playbook for AI agents in 2026: internal use cases first, answers grounded in approved documents, a narrow client-facing scope, the right vendor questions and a 12-month rollout.
- Author
- intoCHAT Team
- Published
- Last updated
- Reading time
- 9 min read

On this page
If you work at a private bank or wealth manager in Geneva and are thinking about AI agents in 2026, you are working in one of the most demanding settings there is: strict supervision, banking secrecy, clients from many countries, and a reputation that one wrong answer can damage. This playbook describes an approach that keeps the risk manageable: start narrow, ground every answer in approved content, and widen the scope only when the controls have proven themselves.
The regulatory frame, briefly
FINMA has not issued a dedicated AI law. Existing rules apply in a technology-neutral way, and the bank remains accountable for what its systems do. In its Guidance 08/2024 on governance and risk management when using AI, FINMA set out its expectations: clear responsibility, an inventory and risk classification of AI applications, data quality, testing and ongoing monitoring, documentation, explainability and independent review.
Three more layers apply:
- Outsourcing. When a third party provides the AI, FINMA's outsourcing rules (Circular 2018/3) and its rules on operational risks and resilience (Circular 2023/1) come into play.
- Banking secrecy. Article 47 of the Banking Act makes disclosing client information a criminal offence. Any client data that reaches a vendor or an AI provider needs a legal and contractual basis.
- Data protection. The revised FADP governs personal data, including transfers abroad.
This is not a setting for a free-form chatbot on client channels. The pattern below is.
An approach that works: internal first, grounded, narrow
- Start with internal use. The first agent serves relationship managers and back-office staff, not clients. It answers policy questions, finds documents, summarises notes and drafts texts that a person checks.
- Ground every answer in approved content. The agent answers from your policy library, approved research and published product information, and shows where an answer comes from. It summarises; it does not give opinions.
- Keep the task narrow. "Answer questions about our onboarding policy" works. "Help advisors" does not. The narrower the task, the easier it is to test and to sign off.
- Log what matters. Keep conversation transcripts as long as your retention rules require, and record who changed the agent's instructions, sources and integrations.
- Decide on data location. Document where conversations are stored and where the AI model processes them, and keep client-identifying data out of any setup where that isn't cleared.
- Require approval for consequential actions. The agent prepares, a person approves. That applies to outbound communication and anything that touches client records.
Three deployment patterns
1. Internal knowledge agent
A relationship manager asks: "What is our policy on accepting new clients resident in this country?" The agent finds the relevant policy, summarises it and links to the source document. Done well, it replaces slow searches through file shares and intranet pages.
2. Meeting preparation and summaries
Before a meeting, the agent assembles a brief from approved research and the bank's own systems. After the meeting, it drafts a structured summary that the advisor reviews, edits and saves. This pattern touches client data, so it usually runs on infrastructure the bank controls or that its outsourcing review has cleared.
3. Triage on the public website
A narrow client-facing agent answers operational questions: office hours, how to send documents, login help, public product information. Everything else goes to the right team with the conversation attached. The agent never gives investment advice, never discusses holdings and never makes statements that could be read as a recommendation. When in doubt, it hands over to a person.
What to ask AI vendors
A private bank's due-diligence questionnaire usually covers:
- Where conversation data is stored and where AI models process it, documented in the contract.
- A data processing agreement with a sub-processor list and audit rights.
- Single sign-on (SAML or OIDC) and role-based access to the admin area.
- An audit log, its scope and its retention period.
- Which AI models are used, where they are hosted, whether they train on your data and how long providers keep it.
- Abstention: the agent must be able to say "I don't know, let me connect you with an advisor".
- Approval workflows for actions that touch outbound communication or client records.
- Security certification such as ISO 27001 or SOC 2, or an equivalent assessment.
Multilingual by default
Geneva client bases are international. An agent has to work in French and English at least, often also in German, Italian, Spanish, Portuguese, Russian or Arabic, with the same tone and the same care in each. Test it in every language you serve, with real questions, before launch. A visible quality gap between languages is a brand risk of its own.
A 12-month rollout
- Months 1-2: use-case selection, vendor shortlist, legal review, outsourcing and banking secrecy assessment, entry in the AI inventory.
- Months 3-4: pilot of an internal knowledge agent in one business unit, with 5 to 15 users.
- Months 5-7: wider internal use; meeting preparation and summaries where cleared.
- Months 8-10: narrow triage agent on the public website, on operational topics only, with strict hand-off rules.
- Months 11-12: broader rollout, independent review, governance sign-off and, if material, a dialogue with FINMA.
What to avoid
- A general chatbot on the client-facing site that answers from model knowledge instead of approved content.
- "AI advisor" framing, even internally. The agent is a tool for advisors, not an advisor.
- Sending client-identifying data to providers that your outsourcing and banking secrecy review hasn't cleared, to save cost or time.
Where intoCHAT fits
intoCHAT fits a clearly defined part of this playbook: the public-website triage agent in pattern 3, and internal questions on non-confidential documents in pattern 1. For that scope it gives a bank useful controls.
- Answers from approved content only. The agent learns only from the pages, files and Q&A you add, and Q&A answers take priority. Built-in rules make it say what it can't confirm instead of inventing an answer, and guardrails such as "Never give investment advice or discuss holdings" apply to every reply.
- A clean hand-off. Visitors reach your team through live chat takeover in the shared inbox, hand-off by email or a ticket in your helpdesk. On Pro, routing sends conversations to the right team, and live translation lets an advisor reply in a client's language.
- Multilingual. The agent replies in the visitor's language, and the widget speaks French, German, Italian, English and Spanish.
- Internal use. The same agent can answer staff questions in Slack, from the same approved sources.
- Security controls. SAML single sign-on and custom roles on Enterprise, roles and access to selected agents from Starter, two-factor sign-in, and an audit log of account changes (90 days on Pro, 365 on Enterprise). Team approval before an action runs is on Pro. Limit the agent to your own domains.
- Data. The database is hosted in Switzerland, and a data processing agreement is available on request. You choose the AI model per agent, from OpenAI, Anthropic or Google.
Where it does not fit: intoCHAT holds no ISO 27001 or SOC 2 certification, its audit log keeps account changes for up to 365 days rather than for years, and its AI providers process messages in the United States. Keep client-identifying data and anything covered by banking secrecy out of it. For the scope above, contact sales to discuss your requirements, or see the banking chatbot for Switzerland page for an overview.
This article describes general practice and is not advice on regulatory interpretation. For binding FINMA, banking secrecy or FADP positions, consult your compliance team and external counsel.
Frequently asked questions
Does FINMA allow banks to use AI agents?
Yes. FINMA has not issued a dedicated AI law; existing rules apply in a technology-neutral way, and its Guidance 08/2024 sets out what it expects: governance and clear responsibility, an inventory and risk classification of AI applications, data quality, testing and monitoring, documentation, explainability and independent review. Outsourcing rules apply when a third party provides the AI, and banking secrecy and the revised FADP apply on top. This is general information, not regulatory advice.
Where should a private bank start with AI agents?
Most banks are better off starting internally, with a knowledge agent that answers relationship managers' questions from approved policy documents and links to the source. Meeting preparation and summaries that the advisor reviews before saving can come next. Client-facing use comes later and stays narrow.
Can a private bank use a chatbot on its public website?
Yes, with a narrow scope. A client-facing agent can answer operational questions such as office hours, how to send documents, login help and public product information, and route everything else to the right team. It should never give investment advice, discuss holdings or say anything that could be read as a recommendation, and it should not receive client-identifying information.
What do Swiss private banks typically require from AI vendors?
Due-diligence lists usually cover where data is stored and processed, a data processing agreement with a sub-processor list and audit rights, single sign-on with role-based access, an audit log with a defined retention, the AI models used and whether they train on data, abstention when the agent doesn't know, approval workflows for actions, and often ISO 27001 or SOC 2 certification.
Is intoCHAT suitable for a private bank?
For a defined part of the work, yes: a public-website agent that answers only from approved public content, says when it doesn't know and hands over to your team, and internal questions on non-confidential documents. It offers SAML single sign-on and custom roles on Enterprise, an audit log, team approval before actions on Pro, identity verification, a database hosted in Switzerland and a data processing agreement on request. It holds no ISO 27001 or SOC 2 certification and its AI providers process messages in the US, so it is not suited to client data covered by banking secrecy.


