Scenarios
Five real setups, the exact settings to use, and what lands in HubSpot as a result.
Pick the one closest to how your team works. Each scenario gives the full combination — you can copy it as-is.
1. First launch, playing it safe
You just connected HubSpot and want to see what Sillage writes before opening the tap.
| Setting | Value |
|---|---|
| Contact Push | On new intent only |
| Contact Creation Mode | Create and update contacts |
| Create missing companies & associate | Off |
| Never touch customer contacts | On |
| Contact sync | Launch |
What happens. Nothing moves until a signal fires. The next time one of your agents detects a buying signal on a lead, that person appears in HubSpot with their intent score, the signal that fired, and the date. Your customers are untouched. No companies are created, so your account records stay exactly as your team built them.
How to check it worked. Open a contact Sillage just pushed and look for the Sillage Properties group on the record.
2. Reps work the whole buying committee in HubSpot
You want every persona-matched contact of a target account visible in HubSpot, and intent used to prioritise inside it.
| Setting | Value |
|---|---|
| Contact Push | Full mapped roster |
| Only create contacts with an email | On |
| Contact Creation Mode | Create and update (locked automatically) |
| Create missing companies & associate | On |
| Never touch customer contacts | On |
| Contact sync | Launch |
What happens. As soon as an account finishes mapping, every contact matching your persona is pushed. Missing companies are created and the contacts associated to them. Contacts without an email yet are held back and pushed on a later cycle once the email is found. Intent data then lands on those records over time as signals get detected.
This is the highest-volume setup. Check your HubSpot contact limit before launching it on a large target account list.
3. Your CRM stays closed — enrich only what you already know
Your portal is curated. Sillage should add intelligence to existing records, never new ones.
| Setting | Value |
|---|---|
| Contact Push | On new intent only |
| Contact Creation Mode | Update existing contacts only |
| Create missing companies & associate | Off |
| Never touch customer contacts | On |
| Contact sync | Launch |
What happens. Contacts your portal already has get their intent score, signals and status kept up to date. A prospect showing intent who is not yet in HubSpot is skipped — nothing is created for them, and the signal only lives in Sillage.
That trade-off is the whole point of this setup, but it is also the most common surprise. If someone on your team decides a skipped lead deserves a record, they can push it manually from the Sillage leads table — a deliberate human action always creates the contact.
4. Protect accounts owned by Customer Success
Some contacts belong to CS, not sales. Automated writes on them cause noise.
| Setting | Value |
|---|---|
| Never touch customer contacts | On |
What happens. Any contact whose HubSpot lifecycle stage is Customer is skipped entirely — not updated, not re-created, not re-associated. It works the same whether Sillage already knows the contact or discovers it while searching your portal.
If your team relies on custom lifecycle stages beyond Customer, this setting will not recognise them. In that case, keep an eye on those records or use the pause switch during sensitive periods.
5. Pause during a CRM migration or audit
Something is happening in HubSpot and you want automation to stop touching it.
| Setting | Value |
|---|---|
| Contact sync | Pause |
What happens. Both triggers stop immediately — no intent pushes, no roster pushes. Everything already written stays in place. Sillage keeps detecting signals the whole time; they simply stay in Sillage.
You can still push a specific lead by hand from the leads table if someone genuinely needs it in the CRM. When the migration is over, press Launch sync and the automation picks back up.
What runs when — the two triggers
Whatever you choose, only these two things ever cause an automated write.
An account finishes mapping
Sillage has resolved the company and found the contacts matching your persona.
→ Pushes contacts only if Contact Push is set to Full mapped roster.
An agent detects a signal
A hiring signal, a job change, a post, a funding round — whatever your agents watch for.
→ Pushes the contact concerned, and updates its intent score, signal count, last signal and signal types. This runs in both push modes.
Everything else — a rep pushing a lead from the table, changing a lead's status, editing it from the Chrome extension — is a manual action, and manual actions always go through, even while the sync is paused.