Receive spoken input
Make voice an interaction path into an application's defined task and context.

Trunnion Voice is a shared voice input and output layer, currently in development. It is being built to bring spoken interaction into Trunnion product experiences.
See the work in context
An illustrative workspace for product & application teams. Explore the work and the decision behind it.
A spoken request becomes a proposed action. Confirm the interpretation before it changes anything.
Correct ambiguous input and confirm the intended action.
Review the material behind the proposed action.
Confirm scope, permissions and consequences.
Approve, revise or decline through the defined workflow.
A spoken interface changes how a person interacts with software; it should not obscure who is speaking, what information is being used or what action is being proposed. Those questions belong in the product workflow.
Built by Trunnion AI, a wholly owned Duskbridge company. This page presents the direction of a product in development; it does not promise release timing or available features.

Make voice an interaction path into an application's defined task and context.
Support spoken output as part of a product experience, with release-specific behavior.
Evaluate identity, participant expectations, data handling and review requirements for each use case.
An illustrative sequence, not a product screenshot or a guarantee of released behavior.
Identify the product task and approved interaction conditions.
Process authorized spoken input within the release scope.
Connect the request to the application's intended workflow.
Keep action authority distinct from conversational fluency.
Start with the workflow you need to improve. Then confirm what the proposed release can actually do.
Trunnion Voice is building. Supported languages, latency and availability have not been established by this page.
Its role in the portfolio is a shared input and output layer for product experiences. Specific packaging and deployment should be confirmed directly.
Yes. Describe the interaction and environment without sending recordings or sensitive personal information through the public form.
Portfolio relationships do not establish an included integration or entitlement.
Start with a non-sensitive overview. Product fit, release scope and next steps belong in a direct conversation.