Cassidy

What Cassidy helps a team automate

Cassidy is a platform for business agents and multi-step AI workflows grounded in company knowledge. It connects documents and other sources with agents that answer questions or perform tasks through configured tools. It suits an operations, sales or client-delivery team whose work repeatedly combines internal information with a defined process.

The official documentation organizes the platform around Agents, Workflows, Knowledge Base and Meetings. An agent provides an interactive role; a workflow defines a process; the knowledge base supplies context. These parts can work together without treating every task as an unrestricted conversation.

Knowledge, workflow logic and review

Cassidy's knowledge features include connected sources, team collections, citations and permissions. Answer Hubs hold curated question-and-answer material. Document verification lets teammates request review or flag outdated content, giving an owner a way to maintain the information behind an automation.

The workflow builder combines actions such as searching knowledge, generating content and updating connected records. Processes can start manually, on a schedule or from an event. Conditional logic directs different cases through different paths, and approval steps can pause execution for review before the next action.

Source citations help a reviewer inspect the material used in an answer. They do not establish that the selected policy applies to every case. A permission-aware collection also needs an appropriate sharing setup: decide which sources each agent and user should be able to access before deploying it broadly.

Example: prepare a proposal response

A consulting team could connect its approved service descriptions and reusable proposal answers, then organize them into a collection for response drafting. Remove obsolete offerings and identify the owner who can approve changes. Begin with a short request containing a few requirements whose answers are already documented.

Build a workflow that identifies the requirements, retrieves relevant material and drafts responses. Add a review step before the output is sent or recorded as an approved answer. Check whether each citation supports the actual promise being made, including qualifications about scope, timing and dependencies.

For a requirement missing from the source collection, route it to the responsible colleague instead of letting a plausible draft become a commitment. Try a revised requirement and an outdated source to see which review needs the process exposes. Once the draft is accepted, preserve the approved version and update the underlying answer collection where appropriate.

Access, synchronization and operating limits

Cassidy's current access page distinguishes a Starter entry route from a custom Business plan. Compare seats, credits, knowledge storage, integrations, deployment and review controls for the proposed account. Confirm trial and billing terms rather than assuming that a start-free button includes every production feature.

Synchronization frequency varies by plan. A change in a connected source should not be assumed to be immediately available to every agent. Credits also govern work performed by agents and workflows, so repeated steps and revisions need capacity planning.

Test the retrieval and action boundaries with representative cases before broad deployment. Check failed steps, restricted sources and the reviewer's ability to stop an incorrect result. Cassidy provides controls for these processes; the team still owns the source quality, authorization and decisions made from the output.