Skip to content
Tulina
Book a demo
← Processes

Re-engage quiet accounts

Quiet paying accounts get one relevant note each, grounded in what they said last, with the outreach date stamped back so nobody's emailed twice.

Book a demo
Folk→Gmail
Starts
Weekly schedule
Steps
7
Checks and gates
2
A person decides
1

Trigger · Schedule

Weekly schedule

Once a week, the run checks which paying accounts have gone quiet for longer than your own threshold.

Claude runs the rest autonomously

  1. 1

    AI lists the quiet paying accounts.

    Folk

    Folk

    You get the paying accounts above your revenue floor, not churned, and quiet for longer than your own threshold.

  2. 2

    AI names one contact per account.

    Folk

    Folk

    Each account gets one person to write to — its stated main contact, or the most senior person on file with an email.

  3. only when a contact with an email exists
  4. 3

    AI finds one real detail to mention.

    Folk

    Folk

    Each account's past notes give one concrete detail worth mentioning, and none is invented when there isn't a good one.

  5. 4

    AI drafts a short, specific note.

    Each account gets a short note that names the real gap since the last touch and weaves in that one detail.

  6. Review the list. A person steps in here.handover

    The full list goes out for a look first, and anything not ready is held back.

  7. only when approved to send
  8. 6

    AI sends each approved note.

    Gmail

    Gmail

    Each approved note goes out from the account owner's mailbox with the team copied.

  9. 7

    AI logs each account, stamps the date.

    Folk

    Folk

    Every account lands on one logged row, and each one actually emailed carries today's date so the next run never contacts anyone twice.

A quiet paying account is easy to miss and expensive to lose. Someone has to notice the silence, remember what the account was last working on, and write something that does not read like a template, assuming anyone runs the list at all. More often it does not happen until the account is already gone.

The account's own history already holds the hook a good re-engagement email needs. The work is reading it before writing, and stamping the date back so the same account never gets touched twice by two different runs. Both are steps an AI agent with CRM and email access can take for every inactive customer on the list.

What you get

Quiet, paying accounts each get one relevant note rather than a blast, and the date it went out is stamped back so the next run knows who's already been touched.

Which inactive customers the run picks up

Once a week, Folk returns the paying accounts that pass three filters at once: above your own revenue floor, not already churned, and quiet for longer than your own threshold, such as no logged interaction in three months or more. The three filters go into one query, because this is a list that gets re-run and should stay cheap.

Each account then gets one person to write to. The account's stated main point of contact comes first. Without one, the run picks the most senior person on file with an email, founder or leadership where possible, and prefers someone the account has actually dealt with over a name that is merely listed. Contacts from unrelated lists, such as a recruiting list that happens to share the account, are skipped, and so is anyone with no email address on file. No address is guessed.

What makes a re-engagement email specific

A generic "just checking in" email tells the account it is a line item. So before a word is drafted, the run reads what the CRM already knows: past notes, the account's own description and status fields, anything showing what they were working on or blocked by. It searches by company name and by contact name, tries a few topical terms such as onboarding, a specific feature or a renewal date, and reads the most recent notes first.

From that it takes exactly one concrete detail, something the account actually said or did. When the notes are empty or too generic to give one, the note falls back to a plain template. A fabricated detail that sounds specific reads worse than a generic email.

The draft itself is short and warm. It names the real gap since the last interaction, weaves in that one detail, carries a two-word subject line that reads as a note rather than a campaign, and offers a short call with a couple of concrete times.

Review, send, and stamp the date

The full list, with each contact, email and drafted note, goes to a person before anything is sent. This is outbound to paying customers, and it earns that look. Approved notes go out through Gmail with the team copied, so a reply does not land in one inbox nobody else can see.

Every account then gets one logged row: the fields that qualified it, the contact used, the detail referenced and the outcome. Each account actually emailed carries today's date, fetched when the run happens rather than hardcoded, and anyone held back keeps a blank date. That date is what makes this safely repeatable. Without it, a second run has no way to know who was already reached, and a quiet account either gets emailed twice in the same month or falls through because someone assumed a previous run covered it.

The prompt

The real prompt behind the steps above, detailed enough that an agent with the same tools can run it as written. The Run buttons copy the full version, which also carries the steps for connecting those tools.

# Re-engage accounts that have gone quiet

You have read/write access to your CRM and email. Run this against
your paying accounts.


## 1. List the quiet paying accounts

- Filter your paying accounts to the ones that fit: above your own
  revenue floor, not already churned, and quiet for longer than your
  own threshold (e.g. no logged interaction in 3+ months).
- Combine all three filters in one query rather than fetching
  everything and filtering client-side — this is a list you'll re-run
  regularly, so keep it cheap.

## 2. Name one contact per account

- Prefer the account's stated main point of contact where one is set.
- Otherwise, pull the people linked to the account and pick the most
  senior one with an email on file — founder or leadership preferred,
  and prefer someone the account has actually interacted with before
  over a name that's merely listed.
- Skip contacts from clearly unrelated categories (e.g. a recruiting
  or sourcing list that happens to share the account), and skip anyone
  with no email at all rather than guessing one.

## 3. Find one real detail before drafting anything

- Before writing a single word, pull what the CRM already knows about
  this account: past notes, its own description and status fields,
  anything indicating what they were working on or blocked by.
- Search by both the company name and the contact's name, and try a
  few topical terms relevant to your product (onboarding, a specific
  feature, a renewal date) — read the most recent notes first.
- Pull out exactly one concrete, specific detail per account worth
  referencing — something they actually said or did, not a generic
  compliment. **If the notes are empty or too generic to yield a real
  detail, fall back to a plain template rather than inventing one.**
  A fabricated detail is worse than a generic email.

## 4. Draft a short, specific note

- Short, warm, and specific. Reference how long it's actually been
  since the last interaction and weave in the one real detail from
  step 3 so it reads as "we noticed," not "we're checking a box."
- A two-word subject line reads as a real note, not a campaign.
- Offer a short call and ask for a couple of concrete times — a
  specific ask converts better than an open-ended "let's catch up."

## 5. Review the list, then send each approved note

- Deliver the full list — contact, email, and the drafted note — for
  a human look before anything goes out. This is outbound to paying
  customers; it earns a review pass.
- Send with whoever on the team should have visibility CC'd, so a
  reply doesn't land in one inbox nobody else can see.

## 6. Log each account, stamp the date

- Write one row per account: the segment fields that qualified them,
  the contact used, the detail referenced, and the outcome.
- Stamp today's actual date on every account you emailed — fetched at
  run time, not hardcoded — so the next run knows who's already been
  touched and nobody gets contacted twice. Leave the date blank for
  anyone held back from sending.

## Output

Report: how many accounts matched the segment, how many were emailed,
how many were held back and why, and how many drafts used a real
context detail vs. the plain fallback.

Why run it with Tulina

A prompt helps one person. A process moves a team.

Pasted into a chat, the prompt above works once, for whoever pasted it. In Tulina, "Re-engage quiet accounts" becomes a process the team shares, that keeps its history, runs on its own, and stays inside the same security perimeter as the tools it calls.

  • The whole team works on the same one

    PersonalTeamOrganisation

    A process lives where it belongs: yours, your team's or the whole organisation's. Whoever runs it can improve it, and everyone starts from the best version instead of explaining the job again.

  • Every edit is a version

    v1v2v3

    Each change is a new version with the previous one kept, so a bad edit is undone by restoring an earlier one. Every run records the version it followed, and what a run teaches goes back into the process.

  • It runs without you

    schedulewebhookon demand

    A hosted agent runs the process on Tulina's own infrastructure, on a schedule or when an event arrives, and keeps going when you close the chat. Nothing to host. Every run is tracked to its outcome.

  • Inside the same security perimeter

    vaultrolesrun log

    Credentials stay in the vault, never in the prompt. Roles decide who may run what, every call is logged, and a step a person has to approve waits for that person.

Questions about customer re-engagement emails

Yes — an agent with CRM and email access can pull one real detail from an account's own history and write a short, specific note instead of a generic check-in, for every account that's gone quiet.

By grounding every note in something the account actually said or did — and honestly falling back to a plain template when the notes have nothing usable, rather than inventing a detail that sounds specific but isn't.

No — every drafted note goes to a human for review first, since this is outbound to paying customers and earns a second look before anything sends.

By stamping the actual send date back onto the account at run time — the next run checks that field, so nobody already reached gets touched again.

Also on Folk

Other processes that run mainly on Folk. The tools they share with this one are lit.

See Tulina in a 30-minute demo.

Book a demo