Point Spiich at a specific record
Type @ in the chat composer to insert a real CRM person, company or deal. Spiich then works on that exact record instead of guessing from a name, and cites what it touched.
Before you start
- A connected CRM (Attio, HubSpot or Pipedrive) that has finished its first sync.
Names are ambiguous. Two contacts called Jane, three deals with the same company in the title, a company whose legal name is nothing like the one you say out loud. An @ mention removes the guesswork by putting the actual record into your message.
Mention a record
Type @ and part of a name
In the composer, type
@followed by at least one character. Spiich searches your CRM live as you type, matching on name and email address, and on deal title for deals.Pick the record
Results are balanced across record types, so a search does not fill up with contacts and hide the deal you wanted. Up to 15 suggestions are shown. Choose one and it becomes a chip in your message.
Finish the sentence
Write what you actually want, for example
@Acme Corp what have we agreed so far and what should I do next?Press Enter.Read the answer and its citations
Record names inside the answer are clickable links back to the record Spiich used, so you can check its work in one click.
You can mention People, Organizations and Deals on any connected CRM, plus Leads and Tickets on HubSpot, where those objects exist. Mention more than one record in a single message when the request spans them, for example a person and the deal they sit on.
What changes in the answer
A mention is not a formatting nicety. It changes what Spiich does before it answers.
| Without a mention | With a mention |
|---|---|
| Searches your CRM by name and picks what looks closest | Works on that exact record instead of the closest name match |
| May ask you which record you meant | Starts work immediately |
| Answers from whatever it found | Works from the exact record you named and cites it in the answer |
| Writes to the record it inferred | Writes to the record you named |
That last row is the one that matters. When you ask for a CRM update without a mention, Spiich has to resolve the target itself, and if the update would overwrite a field that already has a value it stops and asks you to confirm. Mentioning the record and being explicit about the change lets it go ahead without the extra round trip. See What Spiich will and will not do on its own.
Good ways to use it
@Acme Corp I have a call in an hour. What did we agree last time, who is involved, and what are the open risks?
Move the close date on @Acme Renewal 2026 to 30 June and log a note that legal asked for a security review.
Add Tom Berg, VP Engineering, tom@northwind.example, as a contact at @Northwind and link him to @Northwind Expansion.
Limits
- The mention list shows at most 15 suggestions and needs at least one character after the
@. - It searches the CRM your workspace has connected. Records that have not synced yet do not appear.
- Leads and Tickets exist only on HubSpot. On Attio and Pipedrive those object types do not exist at all.
- Object types your admin has not enabled for the agent will not show up. Check
Settings > Object Types, which appears once a CRM is connected. - Spiich can only see what your CRM permissions expose. If a list or record is hidden from your CRM account, Spiich tells you rather than guessing.
If something goes wrong
- Typing `@` returns no records. Either you typed nothing after the
@, the first CRM sync has not finished, or the name does not match anything. Try the email address instead, or paste the record's CRM URL into the composer. - The right record exists in the CRM but never appears. Its object type may not be enabled for the agent. An admin can check
Settings > Object Types. See Control CRM access. - Spiich answers about deals and ignores your Leads or Tickets. Those objects are HubSpot only, and each one has to be enabled for the agent before Spiich can read or write it.
- Spiich stops and asks which records you meant. You asked for something across several records, or a change that would overwrite a filled field. Reply naming the records, or mention them and send again.