Can I turn off the confirmation before bulk changes?

No, and that is deliberate. What you can do is remove the ambiguity: name the records, mention them with `@`, or point Spiich at a saved table so the scope is explicit. When the target is unambiguous and you asked for the change, it proceeds.

What happens if Spiich gets something wrong in my CRM?

Open the work log under `Worked for` to see exactly what it wrote and where, then correct it in the CRM or ask Spiich to fix it. Because your CRM stays the system of record, its own history and audit trail apply to changes Spiich made.

Do research sub-agents have the same access as the main assistant?

No. Sub-agents are read-only research helpers. They can search the web, enrich companies and query prospect databases. They cannot write to your CRM, touch files, or send anything, and they have no memory between tasks.

What Spiich will and will not do on its own

In Chat, Spiich carries out multi-step work end to end but confirms ambiguous CRM changes and leaves emails and meetings to you. Background agents are the permissioned exception for configured reports, Slack posts and CRM writes.

Everyone

An assistant you have to supervise at every step is not saving you anything. An assistant that acts without limits is not something you would put next to your pipeline. Spiich draws the line in a specific place, and this page states exactly where.

What it does without asking

Ask for something that takes eight steps and Spiich takes all eight. It searches your CRM, reads notes and past meetings, checks email and calendar if those tools are on, researches the web, drafts what you asked for, and writes the records and notes the job needs. It does not stop between steps for approval, and it does not hand you back a plan to execute yourself.

For broad research it can hand work to sub-agents that run in parallel and stream their progress into the chat. Those sub-agents are deliberately read-only: they search the web, enrich companies and query prospect databases, and they cannot touch files, send anything, or write to your CRM.

What it stops and asks about

Three situations pull it up short.

Overwriting a CRM field that already has a value. If you tell it explicitly to change a field, it changes it. If it would have to overwrite something you did not mention, it asks first.
Acting across more than one record. Before a batch it names or counts every record it is about to touch. Say "all of these" and it asks which list you mean rather than assuming the most recent one.
Deleting or overwriting a file in your workspace. It confirms before it destroys anything.

To skip the round trip, be specific. "Update the close date on the Acme renewal to 30 June" needs no confirmation. "Update the close dates" does. Using an @ mention is the fastest way to be unambiguous.

What it never does

Kind of work	Spiich	You
Research, drafting, CRM reads and writes	Runs it end to end	Read the result
Emails and messages	Creates the draft	Send it
Meetings	Prepares the brief	Schedule it

That is the boundary for anything you ask for in Chat. Background agents are the one exception, and only where you switch the permission on; see what an agent is allowed to do. When Spiich drafts an email it renders an editable card with To, Cc, Subject and Body. Your options are to copy it, or to open it prefilled in Gmail, Outlook web or your mail client. There is no send button, because Spiich does not have your outbox. Mail and calendar connections are read-only.

The same applies to meetings. Spiich prepares you for one, debriefs you afterwards, and writes what happened into the CRM. It does not accept invitations, put holds in anyone's calendar, or join a call on your behalf.

How to check its work

Click Worked for under any finished answer to expand the full log: every search, filter, write and file.
Click a record name in an answer to open that record and see the change in context.
Use the thumbs up and thumbs down under an answer to send feedback on quality.
Open the record's activity panel to see the note or task Spiich created sitting alongside everything else. See Record pages.

Where the limits come from

Spiich never becomes a second system of record. Your CRM is the source of truth for CRM fields, and Spiich writes into it rather than beside it. What it can see and change is bounded by three things, in this order:

Your CRM permissions. Spiich reads and writes as your workspace's connected CRM account. If a list or record is hidden from that account, Spiich cannot see it, and it says so instead of guessing.
Object types your admin enabled. An admin controls which objects the agent may touch in Settings > Object Types. See Control CRM access.
The tools switched on for the message. Web, email and calendar search are toggles in the composer. Off means Spiich does not look there at all.

Limits worth knowing

CRM writes go out in batches of at most 10 records per call, so a large job runs as several sequential passes rather than one.
Spiich will not claim it saw everything when it did not. If a query matches more than it fetched, it says so, and for very large result sets it asks you to narrow the scope.
Background agents are the one place Spiich acts without you present, and they run only where you set them up and only with the permissions granted. See Background agents overview and Agent permissions.
Creating a background agent from chat needs the permission to manage background agents. Without it, Spiich will not offer.

Frequently asked questions

Not from Chat. It drafts into an editable card and hands you a copy button or a link that opens the message prefilled in Gmail, Outlook web or your desktop client. The one exception is a background agent with Allow email sending switched on, which mails its own reports to the recipients you chose when you set it up.