What you’re actually installing.
Invisibles is five agentic building blocks — Prompts, Skills, Data Context Mappings, Agents, and Audit — reachable from every channel your team already uses and wired into the business data and systems your engineers already run.
Prompts.
A Prompt is one governed unit, a thing your team calls on to get work done. You author a Prompt by talking to the assistant, or by editing the structured view, or by writing the raw source. All three are the same Prompt.
Skills.
A Skill is a Prompt wired as a callable tool — your automation and integration layer. Where a Prompt reads data and returns an answer, a Skill does: invokes code under the hood to pull from external databases, create or update Salesforce records, post messages to Slack, pre-fill forms, or trigger the next step in a workflow. Decorated with OpenAPI specs so agentic LLMs can invoke them directly through function calling.
Data Context Mappings.
The bridge between your business data and what a Prompt sees. Each mapping pins specific fields from a connector to a Prompt’s inputs. No ad-hoc scraping, no silent leaks.
Agents.
Bundles of Prompts, Skills, and Channels. One Agent answers the same way — and takes the same actions — no matter where it’s called from: Slack, voice, MCP, REST.
Audit.
Every run writes to an immutable log. Six-year retention by default. Your security team exports the CSV and closes the ticket.
Three channels, one agent.
Pick how your team already works. Invisibles shows up there, answers the same way, writes the same audit trail.
Web voice.
WebRTC in the browser, Deepgram for speech to text, Polly or Azure Speech for the reply. Sub-second round trips, works in any modern browser, no install required.
MCP.
A Model Context Protocol server, ready for Claude Desktop and any other MCP client. Your Prompts and Skills appear as callable tools, governed by the same masking and audit layer.
REST.
A signed REST endpoint for each Prompt and Skill. Drop it into the app your engineers already shipped. Payloads are JSON, auth is HMAC, logs match the portal.
Microsoft Copilot.
Expose Invisibles Agents as Copilot plugins inside Teams and Office. Same Prompts, same data layer, same audit.
· coming soonMobile.
Native iOS and Android clients. Push-to-talk voice, inbox, full audit history.
· coming soonBot-first authoring.
Three tiers, one object. You talk to the assistant to sketch a Prompt, edit the structured view to refine it, or open the raw source when you want precision. Same Prompt, same governance.
Amount, CloseDate, and LastModifiedDate from salesforce.opportunity. Want it on voice and MCP?stuck-deals. Want to try it?stuck-deals
Three tiers, one object. You pick the surface that fits your comfort.
50 Prompts and Skills, already in the box.
A sample of five of them, below. Prompts read and return. Skills write, create, update, and integrate. The full library lives in the portal.
Questions we get.
What is the difference between a Prompt and a Skill?
A Prompt is a governed unit that reads data and returns an answer — text, JSON, or structured output. A Skill is a Prompt wired as a callable tool with an OpenAPI specification: it invokes code under the hood to create or update records in Salesforce, pull from external databases, post to Slack or Teams, pre-fill forms in Outlook, or trigger the next step in a workflow. All Skills are Prompts; not all Prompts are Skills.
Can an Agent call into our existing internal APIs?
Yes. Any internal REST endpoint you expose to the Invisibles deployment (inside your VPC or VNet) can be wrapped as a Skill. The Skill is registered with an OpenAPI spec, auth is handled inside your cloud, and the call appears in the same audit log as every other Agent action.
How do I author a Prompt or a Skill without knowing code?
Authoring is bot-first. You describe what you want in plain English; the assistant drafts the Prompt or Skill, pins the right Data Context Mapping, and suggests the channels. You can review the structured view to tweak fields, or open the raw source when you need precision. A RevOps lead who has never opened a JSON file can ship a real Prompt in about half an hour.
Which channels can Invisibles expose Agents through?
Web voice (WebRTC + Deepgram + Polly or Azure Speech), MCP server (ready for Claude Desktop and any MCP client), signed REST API for your own apps, Slack, and Microsoft Teams. Microsoft Copilot plugins and native iOS/Android mobile clients are shipping next.
What happens when my Salesforce schema changes?
Data Context Mappings are pinned by field name and type. When a field is renamed or removed, the portal flags impacted Prompts and Skills. You rebind the mapping in one click; nothing updates silently. The audit log records the rebinding with the user who made the change.
Does Invisibles support non-Salesforce systems of record?
Yes. Salesforce is the default connector because most customers start there, but any system with an API or database endpoint inside your cloud can become a Data Context. Microsoft Dynamics 365, Workday, HubSpot, SAP, custom databases — all work. You manage the connectors inside your own IAM.
Ready to install it in your own cloud?
Deploy in about an hour. Free for 14 days. If you’d rather see it with a human first, book 30 minutes and we’ll show you through.