Unblu and Finnova: what an integrated conversation still needs to prove

The brief

Unblu announced on 6 October that its tools are a standard integrated component of Finnova’s Conversational Framework, available to Finnova licensee banks. The announcement covers communication functions including messaging, document exchange and calls. It does not establish that every eligible bank has deployed them or that a particular control has been independently tested. Read the company announcement.

Our procurement question is what survives after the conversation. Can an authorised reviewer identify the instruction, the person entitled to give it, the material considered and the approval to proceed? An integration can make channels available without answering those questions for a particular bank. Ask for a demonstration using a changed instruction, then inspect the resulting record rather than relying on the feature list.

The full record

The vendor describes availability across web and mobile banking, with chat, voice, video, co-browsing and other interaction tools. This is a company statement about an integration and its capabilities, not an independent assessment of adoption, security or customer outcomes. Source: Unblu’s 6 October release.

Our analysis: follow the instruction across channels

A procurement demonstration should begin with a defined task. Use a fictional client who sends a document, discusses it on a call and then changes an instruction in writing. Ask the demonstrator to show where the final instruction sits and how it is distinguished from the earlier discussion.

The useful evidence is the resulting case record. Can a reviewer find the relevant participant, authority, document version, approval and unresolved condition? If a call summary is created later, its origin and timing should be clear. A summary should not appear to be the client’s own wording unless that is what it is.

Test the handover and the exit

Move the fictional matter to another authorised colleague. Ask that person to explain what may be done next without consulting the original handler. Note where they must make assumptions, search a separate system or request missing material. These observations are more actionable than a general impression that an interface is convenient.

Then request an export suitable for an authorised review outside the live interface. Check whether attachments, message order, version information and the link to the final decision remain understandable. Agree what happens when access changes or the provider relationship ends. The appropriate retention period requires its own assessment; this article does not prescribe one.

Use a measurable acceptance question

Before the demonstration, define a pass condition for the particular workflow. For example: a reviewer correctly identifies the final authorised instruction and every unresolved condition from the exported record. Record the elapsed time and errors, but do not hide a wrong conclusion behind a fast completion time.

This is a proposed acceptance exercise, not a benchmark we have performed on Unblu, Finnova or Letro. The announcement matters because it makes a set of communication capabilities available within another banking framework. The purchasing decision still requires evidence about how those capabilities behave in the bank’s own process.

Read Unblu’s public 6 October 2026 announcement on 19 October as a briefing catch-up. Claims about availability and features are attributed to the vendor. We did not inspect a deployment, contract, certification or independent performance study. The demonstration questions are original editorial proposals, not measured product results.

1. Unblu: Finnova conversational-banking integration announcement, 6 October 2026