Decide what the agent may use as business truth.
Sync public content, add approved text, and keep live facts in authenticated tools.
One operating system, three fixed agents
Built to answer.
Designed to finish the work.
Voomate keeps customer conversations, business knowledge, live tools, approvals, and logs inside one controlled runtime. The channel can change without changing the brain.
The complete product
One role for every part of the customer journey.
Choose an agent to see its surface, shared context, connection path, and operating controls.
Web Agent
Chat and voice, embedded.
A framework-independent chat and voice widget that keeps the conversation on the business website and uses approved tools when the customer needs a real action.
- Answer from approved knowledge
- Check live business information
- Run permitted website actions
Customer Knowledge Tool Safe result
Customer signalWebControlled outcome
- Surface
- Website chat and website voice
- Context
- Business knowledge and current conversation
- Connection
- Web Agent ↔ Integration Agent
- Delivery
- One Shadow DOM script embed
The secure execution harness
What happens after a customer presses send.
Every step has a clear responsibility. The model can request work, but it never receives business credentials or unrestricted system access.
- Resolve
Resolve the business
The request’s scoped key resolves to tenant context on the backend. The browser never supplies or receives the tenant ID.
- Understand
Understand the request
The agent keeps the conversation context and determines whether the customer needs an answer, live information, or an action.
- Ground
Retrieve approved knowledge
Business-specific facts come from tenant-scoped knowledge. Untrusted retrieved text remains reference data, never system instructions.
- Gate
Select an allowed tool
When current data or an action is required, the runtime exposes only the typed tools enabled for that business.
- Validate
Validate and execute
The controlled execution layer checks the input and permissions, then calls the business system server-side with scoped credentials.
- Filter
Filter the result
Only explicitly public-safe fields can enter the customer response. Internal notes, credentials, and private commercial fields stay out.
- Respond
Respond and log
The customer gets the useful result in the same thread while the decision, tool call, latency, and outcome are written to Logs.
Simple connections, no workflow maze
Two connection paths are enough.
The Web Agent and Voice Calling Agent can each connect to the Integration Agent. That is how conversation channels gain business capabilities without turning setup into a node canvas.
Web Agentchat + site voiceIntegration Agenttools + systemsVoice Calling Agentinbound + outbound
Operate with evidence
Knowledge, permissions, approvals, and logs stay visible.
Enable only the capabilities the business needs.
Tools are tenant-scoped and validated before execution.
Pause sensitive work before it becomes irreversible.
Money-touching or high-risk actions can enter a review queue.
Trace what the system decided and why.
Conversation, retrieval, tool, latency, and usage events remain inspectable.