Posh AI

Take the models away and what remains is a management portal and a set of connectors. Every product is model work. Digital and voice assistants conduct authenticated banking conversations, and a reasoning engine generates responses from the institution's own website, documents and policies. The list continues with quality assurance that evaluates interactions, a training simulator, and outreach agents that conduct multi turn conversations across voice and messaging.

The voice product is explicitly built for the parts of conversation that defeat scripting. It handles interruptions and mid sentence changes, background noise and off topic remarks, without breaking or looping, and that capability exists only because of the models underneath it.

Four mechanisms combine and together they define and defend the boundary. Escalation is a first class behaviour rather than a fallback, described repeatedly, with the assistant handing to a call centre or in branch representative when it cannot resolve something and passing full context so the customer does not repeat themselves.

Responses are governed against the institution's approved procedures rather than generated freely, which constrains what the machine may say to what the bank has already sanctioned. Behaviour is observable, with independent research noting an emphasis on control and auditability and visibility into how the system is acting, and the company provides metrics on how conversations went and where they fell short. And quality assurance evaluates every interaction rather than a sample. The framing throughout is the machine as first line of defence with human interaction preserved where needed.

The published figures measure handling rather than correctness. Containment statistics such as half of calls and 60 percent of chats resolved tell an institution how much work the system absorbed, not how often it answered correctly. A wrong answer delivered confidently is contained by the same measure as a right one.

Real control infrastructure exists around it, with quality assurance evaluating every interaction and behavior visibility built into the platform, so an institution has the means to inspect quality even though no accuracy figure is published. No error rate or escalation precision is published, and there is no containment quality analysis or hallucination measurement.

The evidence is deep as well as wide. Eleven institutions are named publicly, spanning credit unions and community banks, alongside more than 100 deployments and over 200 live products. Outcomes are quantified per customer rather than in aggregate. One assistant handles over half of calls and 60 percent of chats, with a 93 percent fall in call abandonment. Another manages more than 25,000 calls a month and saves over $225,000 a year in third party costs.

A third saved 22,000 staff hours while quadrupling the speed of new employee onboarding, and a fourth saves more than $15,000 a month. A trade association partnership with a subsidy fund for smaller members provides independent institutional endorsement. The company has raised around $45 million, and a former credit union executive is on the board.

Two published statements raise the boundary question without answering it. The company describes learning from thousands of conversations in building its technology, and the newer outreach agent is described as evaluating its own performance after each interaction and identifying improvements for the next attempt, which the company calls a self learning system.

Neither says whether that learning is contained to the institution that generated it or pooled across the customer base, and the question matters here because the institutions concerned are community banks and credit unions competing directly for the same members in the same towns. Nothing addresses whether one institution's conversations improve an assistant serving its neighbour.

The payload is substantial, and no data protection agreement, retention schedule, subprocessor list or deletion commitment is published. It covers recorded and transcribed conversations between financial institutions and their customers. That includes authenticated sessions where a member logs in with a one time password to check balances and move money, so both the conversation content and the account activity inside it are held.

Voice recordings additionally carry biometric characteristics in many jurisdictions. Nothing published states how long transcripts persist, whether customers are told their call is processed by a machine, or how consent for recording is handled across state regimes.

Posh works inside authenticated banking sessions, where an assistant verifies a member by one time password and then executes balance inquiries and transfers. No attestation, certification, trust center or enumerated framework is public. In that setting, published assurance is not an optional artifact. It is the first thing an examiner will ask a supervised institution to produce about its vendor. Its absence is the most conspicuous gap in an otherwise very strong profile.

Compliance appears as an objective and never as an instrument. The platform is described as helping institutions stay compliant, the quality assurance product as reducing risk and ensuring compliance, and the company positions itself around responsible adoption of artificial intelligence, none of which identifies a rule.

The gap is specific for this function: a machine conducting authenticated banking conversations touches error resolution rights on electronic transfers, prohibitions on unfair or deceptive practices in customer communication, call recording consent that differs by state, and accessibility obligations. None is named.

Speech recognition variance is the issue that matters, and the consequence here is access to banking itself. Recognition accuracy varies with accent and dialect, and also with age, hearing difficulty and speech impairment. The phone channel is used disproportionately by older customers and by those least served by digital alternatives, so the population most likely to be misheard is the population most dependent on the channel.

The company engineers explicitly for acoustic robustness, handling background noise and disfluency. That is real work on part of the problem, but it is not demographic fairness. Escalation to a human materially limits the harm, since a customer who cannot be understood is routed rather than stranded. No accuracy figure is published per accent or per population.

The affected person has a working route out, even though no guarantee, indemnity or falsifiable accuracy commitment binds the vendor. A customer the assistant cannot help is escalated to a human representative with full context carried across, so the failure mode is a handover rather than a dead end. Authenticated actions run through one time password verification rather than on the assistant's own judgment about identity. What is missing sits behind that. No correction process is described for a customer given wrong information by the assistant, and nothing states whether a customer is told they were speaking to a machine.

The platform is described as proprietary and its reasoning engine is named as the company's own, which indicates in house development at the orchestration layer. What is not disclosed is what sits underneath it. Independent classification describes the platform as powered by large language model and natural language processing technology. No provider is named for generation, speech recognition or speech synthesis, each of which is a distinct external dependency for a voice product. No subprocessor list or hosting arrangement is published. For a vendor transmitting authenticated banking conversations, that chain is what an institution's third party risk review exists to examine.

The named integration set covers effectively the entire technology estate this segment runs on. Four core banking platforms are named, which between them account for most credit unions and community banks in the market. Alongside them sit four major contact center platforms, plus digital banking databases and telephony. The company states there is no vendor lock in, and the agent plugs into the existing phone system rather than replacing it.

Deployment speed is claimed against a stated competitive baseline: live in weeks, where other voice systems take six to twelve months. Banking specific implementation playbooks and a domestic deployment team support that claim.

Posh names no hosting provider or region selection, and publishes no residency commitment or private deployment option. Exposure is lower than for a multinational vendor because the customer base and the deployment team are both domestic, so cross border transfer is unlikely to arise in practice. That is an inference from footprint, though, rather than a commitment a buyer can hold. Nothing states where conversation recordings and transcripts rest or whether an institution can constrain it.

Posh publishes no pricing, packaging or basis of charge. One access structure does exist, though it is not the vendor's own pricing. A trade association partnership pairs the platform with a small institution assistance fund that subsidizes adoption for smaller credit unions, which addresses the affordability problem this segment actually has. That is a route in rather than a price, and nothing indicates whether charging runs per institution, per assistant, per conversation or per member.

Coverage is narrow by institution type, and deliberately so. The platform is described as built exclusively for banks and credit unions, concentrated on community institutions in one country. Within that boundary it is broad. It reaches customer facing digital and voice channels, employee facing knowledge, quality assurance and training, and proactive outreach, so a single institution can run the whole surface on one platform.

The company argues the focus is the advantage, reasoning that rivals spanning many industries cannot match depth in one, and the named integration set supports that. Still, this is one segment in one market.