SoundHound

Named connectors and named commerce partners, with the agent completing transactions rather than describing them. Amelia 7 ships an expanded library of third-party integrations and pre-built connectors letting agents retrieve enterprise application data via APIs and execute actions, and the solution pages add seamless integration with core banking systems for account inquiries, loan applications, transfers and card management, and Epic integration in healthcare.

The voice commerce work names the partners outright: drivers order takeout, reserve restaurants through OpenTable, pay for parking through Parkopedia, and reach calendar, email and messaging over MCP to book meetings. That reaches banking, healthcare records, commerce, payments and productivity, and paying for parking or placing an order is an authenticated action in an outside system. Agents consume MCP servers outward as tool calls, and hosting MCP and A2A agents inside the platform is the other direction.

Sourcesoundhound.com Amelia 7.0 release, CES 2026 announcement and solution pagesread 2026-09-06

Multi-agent orchestration across two execution modes. Agentic+ is a proprietary multi-process framework at the core of Amelia 7, letting businesses deploy fleets of goal-oriented agents and handling a complex query by orchestrating multiple agents each with specific functions to resolve it by text or voice without human intervention.

Its distinguishing property is the toggle: it moves between generative flows, where a probabilistic engine synthesizes from data, and deterministic rules-based flows that guarantee consistent results, which SoundHound describes as essential in financial, legal and other high-precision transactions. Workflows carry a human-in-the-loop mechanism as a defined step, and the framework orchestrates across models, deterministic flows and integrations together. Being able to place a deterministic path inside an agentic run, rather than choosing one architecture for the whole product, is a real orchestration capability rather than a positioning line.

Sourcesoundhound.com Amelia 7.0 blog and press releaseread 2026-09-06

An ingestion and retrieval layer the customer builds and maintains. SoundHound describes developing tailored answer libraries for an agent, either through a Q&A format that returns precise answers or by uploading files, websites and other knowledge sources to support model-generated answers, so agents respond dynamically to questions nobody scripted.

Amelia 7.1 names improved knowledge retrieval and fine-tuned matching algorithms among its accuracy gains and cites improved retrieval again among its latency gains, which only makes sense against a maintained index. The platform lets businesses define the specific knowledge and functions needed to execute a task, ships domain-specific content per industry, and serves the same knowledge base across web chat, SMS and voice. Ingest, index, match and retrieve make a maintained retrieval structure that persists and stays queryable.

Sourcesoundhound.com Amelia 7.0 blog and Amelia 7.1 releaseread 2026-09-06

A layered oversight stack with a human step inside the workflow rather than only at the exit. SoundHound documents layered guardrails, confidence checks, safe fallbacks and human escalation working together, states that agents are grounded in customer system data and never guess, and describes Agentic+ workflows as including a human-in-the-loop mechanism to ensure personal oversight when required, which places the approval step inside the run rather than as a failure path.

Around it the platform ships the operational surface that makes handoff work: escalation teams and queues are configured, human representatives handling escalated conversations are managed, canned response templates are prepared, and an Agent Console gives a companion AI that listens to live conversations and offers responses, offers or guidance to the person. The telecom material describes a smart human-in-the-loop that escalates seamlessly across the full spectrum from simple queries to complex multi-step resolutions.

Sourcesoundhound.com Amelia 7.0 blog, platform and telecom solution pagesread 2026-09-06

Amelia's own data processing agreement states that customers manage their own password complexity and SSO/SAML 2.0 requirements, which is identity integration through the buyer's provider, and adds documented practices for identifying and authenticating users accessing its systems.

Its compliance claims cover ISO/IEC 27001, SOC 2 Type II, PCI DSS 3.2.1 and the HIPAA Safeguard Rule, stated consistently across the platform, healthcare and IT service desk pages, with independent auditors reviewing HIPAA and GDPR compliance and a certifications page published on the Amelia domain. Healthcare deployments are positioned as HIPAA-compliant agents integrated with Epic.

Data moves over TLS 1.2 or higher and rests under AWS KMS with FIPS 140-2 validated modules, customer data is returned or destroyed on request, and no customer data is shared across clients.

Sourcesoundhound.com Amelia data processing agreement, platform and solution pagesread 2026-09-06

Execution histories are reachable, which is reconstruction rather than reporting. Amelia 7.1 names transparency as one of its four headline improvement areas and delivers it concretely, adding scripting tools to access AI agent execution histories and stating the purpose as giving enterprises deeper control, visibility and compliance in complex deployments.

An execution history is the record of what a specific agent did on a specific run, and making it programmatically reachable means it can be pulled into whatever system a compliance team already uses rather than only viewed in a dashboard. Around it sit the build interface's analytics tooling and an AI companion that answers questions while building.

The histories are described as execution records rather than reasoning explanations, so a buyer can reconstruct what the agent did and in what order without necessarily seeing why it chose one path over another. No retention period or export format is published.

Sourcesoundhound.com Amelia 7.1 release and Amelia 7.0 releaseread 2026-09-06

Session context is documented. Agents handle complex multi-turn interactions with context held across the exchange, Amelia 7.1 makes agents more context-aware through process-specific instructions and improved retrieval, and the platform maintains a conversation across phone, web, text and messaging so a single interaction can move channel without restarting. That is conversation state inside a session.

No memory layer with a stated scope and a stated lifetime is documented. Nothing says what an agent retains about a person between separate contacts, whether memory is scoped per user, per account or per workflow, how long it lives, or how an operator inspects or clears it. The answer libraries and uploaded knowledge sources are a corpus and the execution histories are a log, and neither is a memory layer.

Sourcesoundhound.com Amelia 7.1 release and platform pagesread 2026-09-06

The customer can run it in their own cloud. Asked directly whether it would support hosting Amelia in a customer's cloud environment as an alternative to the SaaS model, SoundHound answers yes, that it offers hosting within a customer's private cloud and has customers doing this today.

Amelia 7.1 adds support for custom on-premise LLMs, so the inference layer can also sit inside the customer's estate, and the platform has been shown running the agentic stack entirely on the edge inside a vehicle with NVIDIA, alongside deployment embedded in TVs and smart devices. The default remains SoundHound-managed hosting on AWS with Amelia holding administrative control of its virtual servers, so the private-cloud option is a genuine alternative rather than the only mode. A buyer with a different requirement gets a different answer. No region selector or named residency jurisdiction is published for the SaaS mode, so the documented choice is one of environment rather than geography.

Sourcesoundhound.com financial services solution FAQ, Amelia 7.1 release, Amelia DPAread 2026-09-06

Packaged products and a preset library, adoptable without building. The product line is named and each member does its own job: Smart Answering handles inbound calls, Smart Ordering and Dynamic Drive-Thru automate restaurant ordering across channels, Employee Assist gives staff hands-free access to manuals and training, Autonomics automates IT operations, and Sales Assist supports retail floor staff during live conversations.

Each remains a whole product without the others. Beneath them sits a library of business-ready presets for building agents that fully automate familiar tasks such as password resets and reorders, plus domain-specific content per industry and canned response templates for human representatives. That is adoptable packaged assets at both product and component level.

Sourcesoundhound.com Amelia 7.0 blog, platform overview and solution pagesread 2026-09-06

Many arrival paths, voice included. A single agent configuration serves phone, web chat, SMS and messaging apps from the same knowledge base in more than a hundred languages, and the vendor's worked example runs one hotel agent across marketing, reservations and on-property concierge over all four.

Beyond the contact center the same platform reaches into vehicles, TVs and smart devices, so work arrives from an embedded assistant in a car as readily as from a web widget, each an independent inbound queue rather than another view of one surface.

No event catalog, schedule or webhook trigger is published, so work starts by arrival path rather than by event, and the agent answers inbound contacts rather than reaching out.

Sourcesoundhound.com Amelia 7.0 release, platform overview and CES 2026 announcementread 2026-09-06

The buyer chooses the model, and the vendor frames that as the point. SoundHound states that a key strategic advantage of the Amelia platform is its LLM-agnostic architecture, giving the customer flexibility to use the best model for the job, whether a public model, a private model, or a combination, expressly to prevent vendor lock-in.

Amelia 7.1 extends the choice to models the customer hosts themselves, adding support for custom on-premise LLMs, and where fine-tuning is pursued it runs through the LLM provider's own infrastructure with the configuration dedicated to the customer's account. LLM agnostic is named as a platform pillar in the 7.0 release and repeated in earnings commentary, and Agentic+ orchestrates across models rather than binding to one. The choice spans public, private and self-hosted models, and the solution FAQ makes clear the flexibility is the customer's rather than vendor-internal routing.

Sourcesoundhound.com financial services and telecom solution FAQs, Amelia 7.0 and 7.1 releasesread 2026-09-06

Two interop protocols and a scripting surface, with no addressing documented for either. Amelia 7 can host any agent optimized for MCP and A2A, so enterprises and OEMs run self-built agents, SoundHound's prebuilt agents, or agents from outside the SoundHound ecosystem together in one environment, and Amelia 7.1 adds scripting tools that reach agent execution histories. Agents also consume MCP servers outward for calendar, email and messaging. Nothing documents an outside caller driving this platform.

Consuming MCP servers is Amelia reaching out to other systems. Hosting third-party agents means Amelia runs somebody else's agent inside itself, which is a runtime capability rather than an interface onto Amelia. A2A works in both directions, but SoundHound documents no agent card for its own agents, no endpoint or auth scheme, and no API reference, SDK or developer portal.

Sourcesoundhound.com Amelia 7.0 and 7.1 releasesread 2026-09-06

No way to evaluate a change is documented. There is no evaluation harness, no scored test cases, no quality gate in a release path and no controlled post-deployment experiment on any page. Nothing describes previewing an agent against defined conversations before it goes live, versioning a configuration, rolling one back, or comparing a change against a control.

What the platform does offer sits either side of that gap: build-time analytics and an AI companion answering questions while building, which is authoring assistance, and execution histories reachable by scripting, which form the run record. Amelia 7.1 reports accuracy and latency improvements as vendor achievements rather than as a surface a customer can run.

Sourcesoundhound.com Amelia 7.0 and 7.1 releases and platform pagesread 2026-09-06

Nothing published shows Amelia operating a browser, desktop or remote computer.

Its agents reach outside systems through pre-built connectors, enterprise APIs and MCP servers, and their surfaces are voice, chat, SMS and messaging plus embedded assistants in vehicles, TVs and devices, all channels the agent speaks through rather than interfaces it operates.

Vision AI, shown at CES 2026, pairs a vehicle camera's real-time perception with the voice stack so the assistant can see and interpret the driver's surroundings; that is environmental perception of the physical world, not operation of a software interface.

Sourcesoundhound.com Amelia 7.0 release and CES 2026 announcementread 2026-09-06