← The Service Station ~ dish 06 of 10 · the service station

Proactive Check-In Generation

Some customers sit silent for months. Then they churn. A proactive check-in in week four of their journey could have caught the drift. The station knows where customers sit in their lifecycle. It drafts the outreach.

The job

A customer onboards. Two weeks in, they have questions. Four weeks in, they should be activated but nobody checked. Thirty days after their first contract renewal date, they’re in a silent review cycle. You lose them to competitor research instead of competitor action. A proactive check-in sent to the right person at the right moment is the difference between “customer drifted away” and “customer got unstuck and stayed.”

Proactive check-in generation reads your customer journey map (where do customers sit at day 7, day 30, day 60, contract renewal minus 60, contract renewal minus 14) and drafts the right outreach for each moment. The message is personalized by their actual progress (what they’ve used, what they haven’t, what questions they asked). The tone is grounded in where they are (are they struggling or flying).

Plated well: a new customer on day 30 gets an email that says “I see you’ve set up three workflows but haven’t used the reporting feature. That’s where most teams see the biggest ROI. Want to hop on a fifteen-minute call and I’ll walk you through how it works for your use case.” Feels like someone knows them.

The recipe

All seven ingredients still apply. The leverage on this dish is Context (Ingredient #2). The proactive check-in is only as good as the account data piped into it. You need customer journey stage plus actual account activity.

Training sets the house voice for proactive outreach (it should sound like an account manager who genuinely cares, not a marketing automation sequence). Examples show the station what check-ins look like at different lifecycle moments (onboarding versus renewal versus post-incident). Context is load-bearing because the station needs to know where the customer is in their journey plus what they’ve actually done (features used, support tickets, how long since last login). Output Over Process means the destination is clear: send something that lands as personal attention, not a broadcast. Guardrails are critical: never proactively reach out to customers who have explicitly said “do not contact.” Don’t send onboarding nudges to customers who are churning. The Four D’s here: you’re DECIDING which moments matter, and the account manager DIALS with the drafted message. The station isn’t replacing the decision or the delivery.

How to build it

  1. Map your customer lifecycle moments. Write down five to seven moments when a check-in would matter. Day 7 onboarding (early friction catch). Day 30 activation (are they set up). Day 60 expanded use (which features are sleeping). Contract renewal minus 60 (are they thinking about it). Post-incident (are they confident we fixed it). Churn risk flag (are they at risk). Pick the moments that fit your business.

  2. Define what account data feeds each moment. For day-30 check-in, you need: days since signup, features set up, support tickets filed, last login, setup completeness. For renewal minus 60, you need: current plan, days until renewal, expansion signals, dormancy signals. For post-incident, you need: incident type, resolution date, confidence level. Feed the station the actual data fields it needs to personalize.

  3. Create one check-in example for each moment. Write a day-30 check-in you’re proud of. Write a renewal-minus-60 check-in. Write a post-incident check-in. These are the templates the station learns from. Make them personal (name specific features they used, reference their setup, acknowledge their situation). Not broadcast.

  4. Set the dispatch rules. Which customers get which check-ins. Never proactively reach out to someone in their onboarding if they’ve filed three support tickets and gone silent (they’re struggling, not ready for a nudge). Never send renewal check-ins to customers who are already in a churn conversation with an account manager (let that relationship own it). Write two rules that protect the outreach from landing at the wrong moment.

  5. Set the account manager review checkpoint. Station drafts the check-in. Account manager reviews before send. They can edit, personalize, or skip if the account context has changed since the draft was written.

  6. Track response rate and conversion. Did the check-in prompt a reply. Did the reply move the relationship forward. If check-ins are getting a 20% reply rate and 50% of those replies lead to expanded use or renewed confidence, it’s working.

What breaks it

  • Stale account data. The station drafts a day-30 check-in for a customer who actually signed up ninety days ago. Or it references a feature they never activated. The personalization is off. The customer feels seen as a number, not a person. Feed the station fresh data every time or the check-in lands generic.

  • Same message to everyone. The station learned from three check-in examples and now sends the same structure to every customer at that lifecycle moment. Three examples isn’t enough to learn variation. You need five to seven examples across your best check-ins. Show range. Show how you adapt tone and content to different customer situations.

  • No dispatch guardrails. The station schedules a check-in for a customer in a churn conversation with the account manager. Or it sends an activation nudge to someone who’s in quiet-quit mode (they’re not coming back to check email, they’ve mentally moved on). Guardrails save you from the weird moments.

  • Account manager doesn’t review. By week three, the account manager is trusting the drafts and auto-sending. By month two, they’ve drifted. A check-in lands at exactly the wrong moment and the customer feels harassed instead of helped. The account manager has to taste every one to stay sharp. It’s 60 seconds of review. Don’t skip it.

When it’s working

By week two, check-ins are drafting for the lifecycle moments you defined. By week four, customers are replying “thanks for checking in, I had a question about X.” By week six, you can measure churn reduction against customers who received proactive check-ins (they should churn less). By month two, the account manager is editing 20% of drafts because they know the customer’s context better than the data. That editing is where the recipe sharpens.

Measure it: did customers who received a day-30 check-in activate faster than those who didn’t. Did renewal conversations open more smoothly when the account manager had sent a minus-60 nudge. If yes, keep running. If no, sharpen the moment or the message.

Monday Move

Pick one lifecycle moment (day 30 or renewal minus 60). Pull five customers at that moment. Have the station draft check-ins for all five. Then the account manager drafts their own for the same five. Compare. Does the station’s personalization feel real or does it feel formula. Where is the gap. That gap is your build work.

Dish 6 of 10 on the Service Station. Build-note leverage: Context (Ingredient #2).