The architecture behind the work.
People work through their live desks and communication channels. The AI Harness coordinates named workers and internal agents, using approved knowledge and controlled connections to your systems.
Corvair Knowledge Substrate supplies conversation memory and cited library search, with tenant boundaries.
CRM, products, orders and calendars. Read context and return permitted updates through reviewed connections.
Customer channels connect the conversation to this same context and control model. A new message, call or system event can advance the work without losing its owner or history.
Security follows every action.
Identity and limited access
Each worker has an identity and standing permissions. A broker issues short-lived access for an allowed step. People and assistants act within the current user’s company and permissions.
Protected credentials
Connection credentials belong in the secret store, outside worker instructions and conversation text. Stop controls revoke access and halt new work.
Company and tenant boundaries
Company-scoped records and separate knowledge tenants keep each client’s context distinct. Review deployment regions and model processing locations for your requirements.
A record you can follow
Record access, checks, requests, actions and outcomes. Set retention, export and deletion controls for conversations and recordings. Customer conversations are not used to train models.
Security review covers your configured environment, providers and controls. Certifications and data-location requirements need their own evidence.
Information flows in both directions.
Your CRM, operational systems and calendars stay part of the workflow. Agree which information workers can read and which updates they can make, with a clear record of the action.
Each connector has its own supported fields and actions. An integration review establishes the mapping, update direction and permissions for your systems.
Start with the systems you already run.
Choose one useful workflow.
Start with quote follow-up, an account campaign or another repeatable part of your sales day.
Connect and map the information.
Use a supported application connection, live system calls, signed events or files. Start with the files you already have. Map accounts, products and fields once, then review rejected rows and reuse approved rules.
Agree what can go back.
Choose the allowed updates and actions. Set which changes require a person and confirm what the system records.
Try the whole journey.
Start in assisted mode with a named supervisor, backup owners and small limits. Review the journey from incoming information to a decision and confirmed system update. Increase delegated work after reviewing the results.
Connected conversations, across channels.
Customer channels such as phone, email, web chat, text and WhatsApp share account context. Slack, Microsoft Teams and Google Chat connect your team to instructions, requests and decisions. A person can guide a worker, join a conversation or take over. The next channel starts with the relationship’s history, rather than a fresh conversation with no memory.
After-hours cover answers routine enquiries, takes messages and arranges callbacks under tighter limits. Automatic translation shows your team each message alongside its original, while the worker follows the customer’s language.
Configure the channels for your company and countries, including contact permissions, hours and stopping rules.
Explore an omnichannel use caseCore knowledge and memory technology.
Corvair Knowledge Substrate provides underlying technologies used by Corvair Virtual Worker. The platform uses conversation memory and library search with citations. Facts retain their source and date, so people and workers can see what the account context rests on. These are part of the Substrate’s broader knowledge technology; access remains governed for each person and agent.
See how Knowledge Substrate supports the platform, or read the existing Knowledge Substrate documentation for architecture, security, knowledge formats, API and MCP capabilities.
Your AI assistant can join the workflow.
The Model Context Protocol connects AI assistants and tools. Corvair Virtual Worker supports two complementary ways to use it.
Your assistant, working with you.
Read your account context, prepare work and bring decisions back to you. Access stays within your person, company and permissions.
Outside tools, available to workers.
Your administrator can offer reviewed tools from connected systems, with rules for who can use them and when a person must approve.
Human-only decisions stay with an authenticated person. Outside MCP tools that change or delete data do not run automatically, and external tools cannot bypass contact rules. Confirm the supported profile and tested connection for the assistant you use.
Bring the work into your team’s tools.
Employee chat
Connect Slack, Microsoft Teams or Google Chat to worker conversations, requests and notices. The company context and the employee’s permissions travel with the interaction.
Shared customer channels
Customer-initiated conversations in Slack Connect and Teams shared channels are bound to the account. Verify the sender and keep the conversation with the right worker and customer record.
Personal assistants and bots
Let an assistant prepare work through MCP or bring authorised notices to a person’s bot. It uses the person’s current access, without inheriting a worker’s credentials or approval authority.
Provider registration, credentials, permissions and channel setup are required. Confirm the connection in your environment before using it with customers.
Governance in both countries.
For cross-border contact, assess the calling company’s country and the receiving customer’s country together. Apply the stricter applicable rule, then add your company’s permissions and limits. Inbound calls also follow configured routing, disclosure and recording rules.
- Country coverage: use an approved, human-reviewed country profile. Outreach is blocked where no approved profile exists.
- Before contact: check the channel, purpose, contact basis, consent, opt-outs, local hours, holidays, frequency and relevant registries.
- During the conversation: apply AI disclosures and recording notices, respect the customer’s choice and hand off when a person is required.
- After the conversation: keep the checks, decisions and outcome with the record. Set access and retention for recordings and transcripts.
Confirm the applicable country profiles, supported channels and company obligations during setup. Profiles support your compliance process; country coverage is not a blanket guarantee of legal compliance.
Your people stay in control.
- Start with read access and add permissions for the work you choose.
- Preparing a message does not send it. Sending starts off and requires the relevant authority.
- Decisions reserved for a person return to the right authenticated human.
- A saved or queued action is not proof of delivery. Follow its recorded outcome.
Slack
Microsoft Teams
WhatsApp
Google Calendar
Google Meet
Zoom