Do users need to memorize slash commands to use Operations?

No. Teams can run Operations fully with plain language. Slash commands are optional shortcuts for people who want faster repeat actions. Both approaches execute through the same Pilot tools, schema resolution, and permission checks, so behavior remains consistent.

Can Operations handle follow-up requests in the same thread?

Yes. Threads preserve context across turns, so users can refine filters, ask clarifying questions, and apply updates without restarting. Pilot can reference earlier results and record cards, which reduces repetitive prompts and keeps an auditable action history in one place.

How does Operations know which fields to use?

Pilot reads the workspace schema before acting, including custom objects and configured fields. Requests are interpreted against your model, not a generic template. That allows teams to keep business-specific naming while using the same chat workflow for day-to-day operations.

What prevents unauthorized updates in chat?

Permission profiles control object and field access for each member. Operations enforces those profiles at execution time, so users can only search or modify records allowed by their role. Sensitive fields remain hidden when profile settings restrict visibility.

Pilot runs your workspace

Run day-to-day CRM work from one chat thread. Pilot can create, search, update, and link records using plain language or slash commands, while staying aligned with your workspace schema and permission profile on every turn.

40s

Median record update

Typical chat turn to saved CRM data

3×

Less form hopping

Compared with tab-and-field workflows

100%

Schema-aware turns

Pilot reads your Setup model each request

Work where the thread lives

One Operations surface for create, search, update, and link.

Operations is where teams execute work, not where they draft requirements. A thread keeps context from first request to final update, so users can ask follow-ups, refine filters, and confirm edits without bouncing between forms, tabs, or disconnected tools.

Pilot supports natural language and slash commands side by side. Teams that prefer structure use commands like /create, /find, and /view, while teammates who prefer conversation can ask directly. Both paths run against the same workspace model and permission boundaries.

Run parallel threads from the sidebar, compose Gmail follow-ups with AI drafts from record cards, and enrich French companies from SIREN without leaving Operations.

One thread, full execution
Each conversation preserves context, record references, and follow-up intent so tasks continue without restating details.
Natural language plus slash commands
Use plain language for flexibility or command shortcuts for speed, with the same underlying Pilot actions.
Schema-aware and permission-aware
Pilot resolves object and field names from your workspace and enforces profile access before every operation.

Throughput

Chat-first execution for repetitive work

Stay in one thread from search to update to link.

Complete sequences without opening record forms
See confirmations inline in the same conversation
Reduce time spent translating intent into UI clicks

Input modes

Slash commands for speed, plain language for coverage

Use commands for repeat tasks and plain language for flexible requests.

Run /create and /find for predictable speed
Ask naturally when workflow does not fit templates
Keep one execution path across both interaction styles

Context

Context that survives multi-turn tasks

Multi-turn requests stay connected so Pilot reuses prior results and references.

Refine filters without restarting queries
Update subsets based on earlier result cards
Keep auditable action history in one thread

Your model

Built around your objects and fields

Pilot resolves your configured objects and fields instead of fixed templates.

Support custom entities beyond default CRM objects
Keep business-specific terminology in daily execution
Run create and update flows against real schema names

Access

Permission checks on every turn

Pilot enforces profile access before every search, update, and link action.

Hide restricted fields from unauthorized roles
Allow broad adoption without custom prompt guardrails
Apply policy by profile assignment, not manual policing

Threads & email

Multithread sidebar, Gmail compose, and registry lookup

Parallel threads, email, and French Registry enrichment extend Operations beyond record CRUD.

Open multiple Operations threads from the sidebar for separate workstreams
Compose Gmail follow-ups with AI drafts from record context
Search SIREN or company name and apply registry fields — with approval gates in Operations, or confirm overwrite in Standard views

Questions

Short answers before you request access.

Do users need to memorize slash commands to use Operations?: No. Teams can run Operations fully with plain language. Slash commands are optional shortcuts for people who want faster repeat actions. Both approaches execute through the same Pilot tools, schema resolution, and permission checks, so behavior remains consistent.
Can Operations handle follow-up requests in the same thread?: Yes. Threads preserve context across turns, so users can refine filters, ask clarifying questions, and apply updates without restarting. Pilot can reference earlier results and record cards, which reduces repetitive prompts and keeps an auditable action history in one place.
How does Operations know which fields to use?: Pilot reads the workspace schema before acting, including custom objects and configured fields. Requests are interpreted against your model, not a generic template. That allows teams to keep business-specific naming while using the same chat workflow for day-to-day operations.
What prevents unauthorized updates in chat?: Permission profiles control object and field access for each member. Operations enforces those profiles at execution time, so users can only search or modify records allowed by their role. Sensitive fields remain hidden when profile settings restrict visibility.