Put a credit union's manager, IT lead and board risk officer in a room to discuss conversational AI, and each will mean something different by "the platform". The manager means the thing members talk to. The IT lead means the system it runs on. The risk officer means the company that's accountable when it goes wrong. All three are right, and that's why evaluations stall: they're three decisions being treated as one.
Credit unions should evaluate conversational AI as three separate decisions: the AI platform that understands and answers members, the implementation partner that integrates and runs it, and the network layer that carries the calls. The best result comes from judging each on its own criteria, then checking that one party is clearly accountable for the whole service.
The AI platform is the software that understands what a member says or types, works out what they want, and responds. It might sit inside a contact centre platform, come from a standalone vendor, or run in the voice network.
The implementation partner connects the AI to core banking, designs the call flows and handoffs, supplies the evidence a regulated credit union needs, and supports it after launch.
The network layer carries the calls. For phone-based AI, it decides availability and audio quality, and whether the AI can sit in the call path without the credit union changing its phone system.
Sometimes one company covers all three. Often it doesn't. Either way, each needs judging on its own terms. DigitalWell's earlier guide to choosing conversational AI for Irish financial services compares the main deployment models; this article focuses on how to evaluate each layer.
Judge it on what members experience. Four tests matter most.
Test these with real member scenarios written in your members' own words.
Judge the partner on what happens around the AI. This is where much of the effort and risk sits.
DigitalWell's Credit Unions page sets out the supplier documentation it provides: corporate and data-location statements, security posture, SLA and KPI performance, incident logs, proven access for auditors and the Central Bank, and joint continuity testing.
Judge it on availability and position. If the AI answers the phones, the network decides whether members can reach it.
Ask for the provider's uptime history on the network your calls will use. Ask whether calls can be rerouted to another branch or team if a site goes down. And ask whether the AI runs inside the network, or whether calls have to be sent out to another provider's cloud and back.
Martin Browne, CTO and CX Chief Technologist at DigitalWell, describes DigitalWell's approach:
"It's our system running on our network, our voice network."
Martin Browne, CTO and CX Chief Technologist, DigitalWell
DigitalWell's AI Voice Network runs AI Voice Agents inside its own licensed carrier network, which carries over 100 million minutes of voice traffic. Because the AI sits where the calls already travel, it works with the credit union's existing phone system, and every call is transcribed, summarised and logged. DigitalWell's article on what resilience should mean when a credit union puts AI on the phones covers failure points and fallbacks.
The test of a good arrangement is that every part of the service has a named owner. The table shows a typical split, and where gaps appear when the three layers come from different companies.
|
Responsibility |
AI platform vendor |
Implementation partner |
Network provider |
Gap to watch for |
|---|---|---|---|---|
|
Understanding and responses |
Owns |
Configures and tunes |
None |
Nobody tunes the AI after launch |
|
Core banking integration |
Provides APIs |
Builds and maintains |
None |
Integration breaks after a core banking upgrade |
|
Handoff to staff |
Supports |
Designs |
Routes the call |
Context lost between systems |
|
Call availability |
None |
Monitors |
Owns |
Calls fail and each party points elsewhere |
|
Recording and audit trail |
May store |
Configures retention |
May record |
Records split across suppliers |
|
Regulatory evidence |
Supplies its part |
Compiles |
Supplies its part |
No single pack for the board |
|
Incident response |
For the AI |
Coordinates |
For the network |
No single incident clock |
Where one provider covers the partner and network roles, as DigitalWell does for its AI Voice Network, most of the gaps in the right-hand column close. The credit union still needs to check who owns the AI model, where data is processed, and how the exit would work.
Run a pilot on one or two call types, then score it on member and operational outcomes. Agree the measures before the pilot starts.
A pilot that scores well on all seven is a stronger case for the board than any demo.
No, but fewer parties make accountability simpler. Where they're separate, map who owns each responsibility and write it into the contracts.
Often the partner. Integration, handoff design and regulatory evidence decide whether the AI works in practice.
Yes, if you're already on a platform with built-in AI. Check it covers your phone volume and that the partner can integrate it with core banking.
Not yet. Credit unions are exempt from DORA until 17 January 2028. Section 76J and the Central Bank's outsourcing and operational resilience guidance apply now.
Long enough to cover normal weeks and at least one busy period, such as a month-end. Several weeks is typical.
Evaluating conversational AI for your credit union? Talk to DigitalWell's credit union team about a pilot scored on your own member calls.