Solutions Financial services
Resolve member issues on the call. Sensitive ones, handed to people.
Members talk to Bidirection on your online banking and get it resolved: statements, autopay problems, fees and funds availability, by your published policies. Fraud, disputes and anything that needs a decision go to your team with the whole story.
Illustrative call on Wexmoor Credit Union, a made-up credit union.
The issues that fill your contact centre.
From routine requests to problems that need care, L1 and L2. Here’s how each one ends.
- L1“How do I download last year’s statements?”Resolved on the callStatements › 2025 › Download
- L1“What’s the fee for an outgoing wire?”Answered on the callFrom your published fee schedule
- L1“When will my deposit be available?”Answered on the callFrom your funds availability policy
- L2“My autopay didn’t go through this month.”Fixed on the callAutopay pointed at a closed account. Moved to Checking ••6021 together under Payments.
- L2“My card was declined at the store.”Done in your systemsCard system: locked after three wrong PINs, unlocked once the member was verifiedSwitching on for calls, journey by journey.
- L2“There’s a charge I don’t recognize.”Handed off with the whole storyReason: possible fraud, sent straight to your team. Step reached: charge date noted.
- L2“I want to dispute a charge.”Handed off with the whole storyReason: disputes need a decision. Step reached: dispute form found.
Typical issues. How each one ends depends on your content and the workflows you approve.
What your members and team gain.
Routine requests, resolved on the page.
Statements, autopay problems and address changes are resolved with your approved steps, so members finish them in one go.
Sensitive details stay with the member.
Passwords, card numbers and codes are masked on the member’s device and never sent.
Fraud reaches people.
Questions about fraud, and anything that needs a decision, become a ticket with the reason and the step reached.
Answers that match your disclosures.
Answers come from your published fee schedules and policies. If they don’t cover it, it says so instead of guessing.
Fits the way your team works.
Three steps, from your public pages to help inside online banking.
- 01
Start from your public pages
Paste one link. It reads your fee schedules, policies and help pages. Callers only hear what you mark public.
- 02
Turn procedures into approved workflows
Statements, autopay and address changes become steps your team reviews and approves before members hear them.
- 03
Send sensitive cases to people
Fraud, disputes and anything needing a decision reach your team with the reason, the step reached and a note.
Careful with what matters.
It reads the structure of the page, never pixels, other tabs or other apps. You decide what it never sees.
Read more on the Trust page- Card numbers stay in the browser
- Password, card and code fields are masked on the member’s device and never sent, whatever your rules say.
- Pages it skips
- List pages it should never read, like transfers or account settings.
- Rules in plain sentences
- Write rules like “Don’t discuss loan rates; offer a hand-off” and see which were checked on each call.
- Masked transcripts
- Card numbers, emails, phone numbers and codes are masked; you keep transcripts for 1 to 365 days.
35% fewer CX tickets
Routine questions end on the call, so your team’s time goes to the members who need a person.