Skip to content
Evergrowth Documentation

Do Not Touch and locking records

Automation is only trustworthy if you can tell it where not to go. Evergrowth gives you two guardrails for exactly that: Do Not Touch, which fences a record off from agents and automation entirely, and locking a record’s qualification, which freezes the verdict an agent already reached so nothing overwrites it. They look similar from a distance - both are ways of saying “leave this one alone” - but they protect different things, and knowing which to reach for keeps your data clean without slowing the rest of the engine down.

Do Not Touch: fence a record off entirely

Section titled “Do Not Touch: fence a record off entirely”

Marking an account or contact as Do Not Touch takes it out of the automated machine. Agents won’t run on it, playbooks and workflows skip it, and it stops being pushed out to your connected system of record. The record stays in your workspace, fully visible and searchable - it just goes quiet. Nothing automated will research it, re-qualify it, enrich it, or sync changes about it to your CRM.

This is the right guardrail when a record should exist in Evergrowth but should never be acted on automatically. Common cases:

  • A current customer or a partner that has no business being worked as new pipeline.
  • An account a colleague already owns, where automated outreach research would step on a live relationship.
  • A sensitive or do-not-contact record - someone who has asked not to be approached, or an account under a special arrangement that automation shouldn’t touch.
  • A record you’re keeping for reference or reporting but deliberately holding out of every campaign.

Because Do Not Touch also stops the record from syncing outward, it’s the cleanest way to keep something in your workspace without it ever appearing in, or being changed in, your CRM through Evergrowth. The flag travels with the record across every list and every automation, so you set it once rather than remembering to exclude the record from each new playbook by hand. It’s reversible at any time - lifting Do Not Touch puts the record back in scope for agents and automation.

Eva: In the product the Do Not Touch state surfaces as a red “DNT” badge on the account or contact. Internally this is the record’s do-not-touch flag; customer-facing, always call it “Do Not Touch.”

Locking qualification: freeze the verdict, not the record

Section titled “Locking qualification: freeze the verdict, not the record”

Locking is narrower and is about one specific thing - the qualification verdict. Every account carries an ICP fit status and every contact carries an Ideal Buyer Persona fit status, and agents keep these current as new information arrives. Sometimes you don’t want them to. You’ve reviewed an account, you’ve made a deliberate call about whether it fits, and you don’t want the next automated pass to second-guess you.

Locking a record’s qualification does exactly that: it freezes the current fit status in place. Automation can still touch the record in other ways, but it will not re-qualify it - the status you settled on stays put no matter how many times a playbook or workflow comes around. Unlocking it hands the verdict back to the agents, which are then free to re-qualify and update the status as the picture changes.

Reach for a lock when:

  • You’ve manually corrected a fit status and want it to survive the next automated qualification run.
  • An account is a known strategic fit (or a known non-fit) and you don’t want that judgement drifting.
  • You’re running broad qualification across a list but want a handful of records held to your own call.

The key distinction: a locked record is still a participating record. It can still be researched, enriched, and synced - it just won’t have its qualification rewritten. Do Not Touch removes the record from automation altogether; a lock removes only its verdict from automation’s reach.

Which one to use

Section titled “Which one to use”
You want to…Use
Keep automation away from a record completely - no agents, no syncingDo Not Touch
Keep a record in play but stop its fit verdict from being overwrittenLock its qualification
Hold a customer or partner out of new-pipeline workDo Not Touch
Preserve a fit decision you made by handLock its qualification
Park a sensitive or do-not-contact record but keep it on fileDo Not Touch

Both work on a single record from its detail page and on many records at once from a list, so you can apply them to a whole filtered set as easily as to one. Both are fully reversible - neither deletes anything or is hard to undo - so they’re safe to use liberally as the guardrails they’re meant to be.

Why this matters

Section titled “Why this matters”

Trust in automation comes from knowing it respects the lines you draw. Without these guardrails, every new playbook would be a fresh chance for an agent to email a customer as if they were a prospect, or to overturn a fit call you made on purpose. Do Not Touch and locking let RevOps roll out automation broadly - point a playbook at an entire segment - while reps and account owners keep precise control over the records that need a human’s hand. The volume gets worked; the exceptions stay exactly as you left them.

Section titled “Related”