Skip to main content

​
FAQ

Answers to the questions that span more than one feature. For questions about a specific integration or channel, see that page’s own FAQ.

​
Billing & usage

The unit Cobalt meters usage in. One credit covers one end-user turn — an employee asks, the agent works and answers. Building, configuring, and testing in Preview never cost credits; only real employee conversations on a live channel do. See Billing & usage.
Yes — every new tenant starts with 100 free credits and no card required. See Sign up & start free.
Agents pause and employees get a brief “temporarily unavailable” reply until you top up. Any top-up reactivates the tenant immediately. Turn on auto-renew to avoid pausing at all — Cobalt warns before the balance runs out and retries a failed renewal over several days.

​
Identity & access

Not necessarily. On channels where they’re already authenticated (Slack, Teams, an embedded widget in an app they’re logged into) they’re identified automatically — no second sign-in. A public web widget can run anonymously. Whether an agent can act as a user depends on how strongly that identity is verified — see End-user identity.
Admins build and run agents in the console; their access is governed by roles and, optionally, SSO. End users are the employees who talk to the agents; they’re managed as end-user identity and provisioned via SCIM. They never touch the console.
Yes — the same account can belong to several tenants and switch between them. Each tenant has its own agents, billing, and data. See Working across tenants.

​
Channels

The web widget (including SharePoint Online), Slack, and Microsoft Teams. Email and SMS are coming. See the channels overview.
The web widget is the richest surface — inline citations, source cards, media, voice, forms, feedback. Slack and Teams render what their platforms allow (for example, images inline but not interactive walkthroughs); Slack and Teams bots are direct-message only. Where a channel can’t render something, the agent degrades gracefully rather than dropping content — citations become a “Sources” list, for instance.
No — a spoken turn is metered exactly like a typed one (one credit). See Voice.

​
Integrations

It’s built and usable, but not yet verified against a live vendor instance. Activating one asks you to acknowledge that first. Try it in Preview before relying on it. See the Integration catalog.
If it speaks the Model Context Protocol, connect it with the MCP Server integration. Otherwise, the catalog grows regularly — check the console, or ask us.
No. Read tools run as the asking user, so the agent only sees what that person can already see. Indexed content is permission-checked against the source at query time. Privileged actions run under admin-configured policy and are audited.

​
Platform

Not today. Cobalt is administered through the console; the machine-to-machine surfaces a customer touches are SCIM for user provisioning and the inbound webhooks the channel platforms (Slack, Teams) call. There is no public REST API or outbound event webhook to build against yet.
Not yet — Cobalt consumes MCP servers as integrations, but doesn’t expose an agent as an MCP server for external hosts to call.
Each tenant is isolated — its agents, conversations, identities, and billing are its own, and credentials and secrets are encrypted at rest. For specifics on data handling, security, and compliance, talk to us.