How Accelerate works

A customer asks for an update, and the answer depends on a conversation, a proposal and a promise made in a meeting. Accelerate keeps that context connected so a person or AI assistant can understand the request and prepare the next useful action.

Command Center is the workspace your team uses to see and operate that shared foundation. Builders can add capabilities around the same records and services, so a custom workflow can keep the customer context, permissions and history already in place.

Follow one piece of work

Start with the roofing inquiry recipe. Form builder collects a request, an operator reviews it, and the accepted response becomes part of the pipeline. The team can open the customer context, assign the next action and use Pipeline follow-up to find opportunities needing attention.

When the opportunity is won, Client onboarding can prepare an assigned checklist from it. After review and execution, the tasks are available in Work with their source attached. Creating the checklist starts delivery; the team updates its tasks as the work happens.

This is the value of composition: each feature does a specific job while the related records carry context between steps.

Understand the shared foundation

Layer	What it contributes	Example
See	Information from supported connections, forms and imports	A customer inquiry or a calendar event
Remember	Linked records, source context and activity history	The conversation and tasks attached to a customer
Notice	Findings that help the team choose what to review	An overdue commitment or stale opportunity
Act	Supported operations with permission checks and recorded results	A reviewed task plan or email proposal
Learn	Explicit guidance and eligible policy changes people review	An approved reusable correction

These layers describe how the platform fits together. Their availability depends on the features, connections and execution configured for your workspace. Use Setup to check the requirements for the particular workflow you want to run.

Choose the right building block

A core feature provides shared business functionality, such as customer records, conversations, tasks or approvals. A module controls whether a supported area is enabled in a workspace.

A connector provides access to an external system. A plugin combines records and operations into business behavior, such as a report, onboarding checklist or Collections workspace. The plugin library explains the bundled examples and their setup.

A custom App can introduce its own records, process and interface while reusing the shared foundation. A builder implements that extension through the source repository today. General-purpose App creation inside Command Center is planned; the App guide explains the current path.

Use AI with the available context

Ask AI a specific question about a record or time period, then inspect the sources it returns. Its registered tools determine what it can read and what changes it can propose. A missing connection or unavailable source limits the answer, so use the source record to resolve gaps before acting.

For a supported change, inspect the exact target, content and consequences in the proposal. The action’s policy determines the required decision. After execution, check its recorded result and the source screen. Approvals explains review and autonomy; action results explains completed, failed and uncertain work.

External assistants can use MCP to reach supported workspace tools. They retain the same access boundaries and cannot approve their own staged proposals.

Build a workflow around your business

Start with the industry recipes to see useful combinations of current capabilities. Use settings when they cover the change. When you need a new record type, external system or operation, follow Build an extension and name the source of truth, permissions and result to verify.

The platform provides shared services so the extension can focus on the business-specific work. Keep each record’s lifecycle in one owning service, and use the same service from the interface, AI tools and integrations.

What to check

Verify connected sources and permissions before using real records. The fictional demo is useful for learning the interface and simulated workflows; it does not verify a live provider connection.

Read the saved action result before retrying work. An approved request may still fail during execution, and an uncertain provider response needs reconciliation before another send. Keep drafts, approvals, completed changes and customer outcomes distinct when explaining what happened.

For a first exploration, use your first workflow. For a connected installation, use Self-hosting. For a code change, use your first developer change.