ChatGPT for financial services: an honest review (2026)

How I reviewed it

I am on the support side of things, so this is not a benchmark of reasoning scores. It is a working review of ChatGPT against the jobs a finance team actually hands it: internal research, drafting, and, the part I care about most, customer-facing support. I read OpenAI's own product, pricing and security pages, the named deployments at Morgan Stanley and Klarna, and what practitioners in banking, wealth and compliance say when nobody from sales is in the room. Where I quote someone, the link goes to the original.

One framing note before the verdict. "ChatGPT" is not one thing anymore. There is the consumer app, the no-training business tiers, and now a regulated-industry configuration. Most of the disappointment I see online comes from judging the whole family by the free app, so I have tried to be specific about which tier does what.

What ChatGPT is genuinely great at

Let me start with the wins, because they are real. If your job is to produce a research memo, a first-draft pitch, or a summary of a 40-page filing, ChatGPT is one of the best tools you can reach for. This is the half of the product that finance teams are quietly obsessed with, and the adoption numbers back it up.

The clearest proof point is Morgan Stanley, which built an internal advisor assistant on OpenAI's models. Adoption hit over 98% among advisor teams, document access jumped from 20% to 80%, and follow-ups that "used to take days now happen within hours," per Kaitlin Elliott, Head of Firmwide Generative AI Solutions. That is not a demo, it is a wealth manager putting the tool in daily use across the firm.

The newer piece is the Financial Services product, shaped with Morgan Stanley and Evercore, which layers built-in premium data on top: earnings transcripts, fundamentals and private-company data from Daloopa, PitchBook, LSEG News and Crunchbase, indexed and hosted by OpenAI. You can toggle exactly which sources are in play.

The feature I liked most on paper is the one that answers the biggest objection to AI in finance: sourcing. OpenAI built granular citations so "bankers can trace figures and claims back to their sources." In practice that means a number in a memo links straight back to the highlighted line in the transcript it came from.

If you want the full tour of features, tiers and pricing rather than the review verdict, our ChatGPT for financial services overview covers that ground. For this review, the short version is: as a research and drafting assistant, it is the sharp tool in the drawer.

Where it falls short

Now the part a review is actually for. Three limits kept coming up, and none of them are dealbreakers for research work, but all of them bite the moment you push toward regulated or customer-facing use.

The consumer tiers are a compliance problem

Finance is the industry most likely to have banned consumer ChatGPT outright, and practitioners talk about it as just a fact of the job.

"Yeah, I have received multiple emails saying GPT usage is strictly prohibited and they have blocked it on the work PCs lol."

Using GPT at work, r/FinancialCareers

The reason is not paranoia. On the free and Plus consumer tiers you do not get the enterprise data guarantees, and pasting a client name, a case reference or a statement into a personal account is itself a disclosure. A named security operator put the risk about as bluntly as it gets:

"Just worked w/ @CNN on a piece about why I wouldn't upload full financial docs (tax docs, statements, etc) to AI tools due to leakage & hacking risk. I don't recommend connecting bank accounts to AI tools. It becomes a 1 stop shop for attackers looking to drain your accounts."

Rachel Tobac (CEO, SocialProof Security), X

To be fair to OpenAI, this is exactly what the business tiers are built to fix, and I will give them proper credit in a moment. But the default thing most people mean by "ChatGPT," the app they already have open in a tab, is not the thing you want handling regulated data.

It hallucinates numbers, quietly

This is the one that worries me most for finance, because the failure is silent. ChatGPT is not usually wrong in a loud, obvious way. It is wrong in a confident, well-formatted way, and in a domain full of numbers that is dangerous. The sharpest description I found came from a practitioner who tried to wire it into a finance workflow:

"Tried integrating chatgpt into my finance job to see how far I can get. Mega jikes... millions of dollars of hallucinated mistakes. Worse you don't have the same tight feedback loop you've got in programming... You basically need to walk through everything it did to figure out what's real and what's hallucinations. Basically fails silently."

Havoc, Hacker News

That "no feedback loop" point is the whole thing. When you write code, a wrong answer usually hits a wall: a compile error, a failing unit test, something that says "this is broken" before it ships. A wrong number in a spreadsheet or a client email has no such wall. It just goes out.

The Financial Services product's citations genuinely help here, because a traceable figure is a checkable figure. But "checkable" still assumes a human checks it, which is fine for a banker reviewing their own memo and a real problem if you were hoping to point the model at customers unattended.

It is not built to run a support queue

Here is where my job comes in. Even with the perfect tier and perfect data, ChatGPT on its own is a chat window, not a support agent. It does not sit inside Zendesk, Freshdesk or Salesforce reading your live queue. It does not take actions like tagging a ticket, looking up an order, or issuing a refund. And it has no per-ticket governance: no approval step you can hold on a risky reply, no dry run over your real ticket history before it touches a customer.

None of that is a knock on the model. It is a category thing. ChatGPT is a brilliant reasoning engine, and a reasoning engine is exactly the raw material a support teammate is built from. It is just not the finished teammate. That is the distinction that matters most if you are choosing what to actually deploy, and it is worth spelling out.

A chatbot is not a support teammate

The cleanest way I can put it: ChatGPT is the model, not the employee. It is infrastructure. What a regulated support desk needs is the layer that sits on top of the model and adds the parts the model was never meant to carry.

That layer is where the interesting work happens for support: sensitive data redacted on the way in, a simulation over your own past tickets so you can see how the agent behaves before a single customer is affected, a human approval step on anything risky, and the connections into your helpdesk so it can actually resolve, not just draft. Morgan Stanley did not just switch ChatGPT on either. They built an eval framework and ran daily regression tests before deploying, which is the enterprise version of exactly this idea.

The good news is you do not have to choose the model to get the governance. A support teammate can run on GPT, Claude or Gemini underneath and add the support-desk parts on top. That is the space a purpose-built AI for customer service teammate lives in, and it is the honest answer to "how do I use this for support without the risks above."

Give OpenAI its due on security

I do not want to leave the impression that OpenAI ignores the compliance problem, because on the enterprise tiers it clearly does not. By default it does not train on business data across ChatGPT Enterprise, Business and the API, with sharing as an explicit opt-in. There is AES-256 encryption at rest, TLS 1.2+ in transit, and SOC 2 Type 2, ISO 27001, GDPR and CCPA coverage per its business-data page.

Zero data retention was the decisive point for Morgan Stanley, whose David Wu noted the team's willingness to ensure zero data retention "has been really impactful." Workspace admins control retention, deleted conversations clear within 30 days, and eligible customers get data residency across regions plus a Compliance API for audit. This is a serious security posture. The caveat is simply that all of it lives on the tiers a finance team has to deliberately buy and configure, not the free app most people picture.

Pricing: what a finance buyer actually pays

Pricing tracks the tier ladder, and the exact business numbers render behind sales, so treat the seat prices as "confirm live." The one figure OpenAI states plainly is ChatGPT Pro at $200/month.

Two things to flag as a buyer. First, the no-training guarantees you actually need for finance start at Business, not Free or Plus, so the "free chatbot" mental model does not apply once compliance is in the room. Full ladder and the fine print sit in our ChatGPT pricing guide. Second, Enterprise billing is seats plus governed usage of the agent products, not a flat per-seat fee, so model your real usage rather than the sticker. If you are weighing the whole ChatGPT lineup, our ChatGPT overview walks through what each tier actually includes.

It is worth contrasting that with how a support tool prices, because the unit is different. For customer support specifically, a teammate like eesel charges per ticket handled rather than per seat, which means the cost tracks the work rather than your headcount. For a support org that is usually the more honest number.

The verdict

So, is ChatGPT good for financial services? For the analyst work, genuinely yes, and I would not talk anyone out of it. It is one of the best research and drafting tools available, the Financial Services product closes the sourcing gap that used to be its weakest point, and the enterprise tiers take compliance seriously. If your team writes memos, models scenarios and preps client materials, buy the right tier and go.

For customer-facing support, my verdict is narrower: use the model, but not the raw chatbot. The silent-hallucination risk, the lack of native helpdesk actions, and the missing per-ticket governance mean a general ChatGPT window is the wrong shape for a regulated support queue. You want the reasoning engine, wrapped in a teammate that was built for the desk. If you are comparing options for that specific job, our roundup of the best customer service AI and customer support automation tools is the place to start.

Try eesel for financial services support

If you landed here because you run support at a bank, a fintech or an insurer, here is the honest positioning. Keep ChatGPT for the research and modelling it is brilliant at. For the support queue, eesel is the AI teammate that plugs into your existing helpdesk, whether that is Zendesk, Freshdesk, Salesforce or Front, and starts working the tickets itself.

The part that matters for a regulated firm is what happens before it goes live. eesel simulates the agent on hundreds of your past tickets and scores its answers against what your team actually sent, so you see how it will behave before a customer is ever affected. PII is redacted at ingestion, the models never train on your data, and you can hold a human approval step on sensitive actions. Pricing is usage-based at $0.40 per ticket handled, with a $50 free trial and no per-seat fees. It is free to try, and you can point it at your own tickets in an afternoon.