Customer Check-In Email Templates

"How has [feature] been working for the [workflow] you mentioned during onboarding?" is the kind of question that gets a real answer. Compare that to "How's everything going?" which is too open-ended to produce anything useful.

A good check-in asks one focused question about how the customer is progressing with the product, references a particular aspect of their setup or use case, and leaves room for them to raise anything they haven't mentioned yet. The specificity shows you remember their situation.

The 30-day check-in is about activation: did the customer get started, did they complete the key setup steps, are they hitting any early blockers? This is the highest-value check-in because problems caught at 30 days are far easier to fix than problems discovered at renewal time.

The 90-day check-in shifts to outcomes: has the customer started seeing results from the product, what has surprised them (positively or negatively), and are there additional use cases they haven't explored? By 90 days, a customer who is actively engaged will have stories to tell. A customer who is quiet at 90 days is often an early churn indicator worth investigating before the renewal conversation starts.

The 60-day check-in sits between the two: activation issues should be resolved by this point, but outcomes are still emerging. This is the right moment to ask whether the customer has moved beyond the initial use case, whether they've shared the product with additional team members, and whether anything has slowed them down. A customer who was fully activated at 30 days but hasn't expanded at 60 is worth a conversation before the habit solidifies around only the features they already know.

Casual and particular performs better than formal for check-in emails. "Quick check-in: how's [Product] going for [workflow]?" references their context directly. "30 days in: [Company Name]" is simple and creates a milestone anchor.

Avoid overused subject lines like "Checking in" or "Touching base." Both give the customer no reason to open the email over the other things in their inbox. A subject line that references a milestone or use case tells the customer the check-in was written for them.

When the check-in generates a real reply, respond the same day. A customer who surfaces a genuine problem or a genuine win deserves a response that does something with it: a next step, a flagged resource, or a call set up. A check-in that returns a detailed reply and gets a two-line acknowledgment creates the opposite impression of what you were trying to build.

Following up on something the customer mentioned during onboarding or their last interaction is the fastest way to show you've been paying attention. "Last time we talked, you mentioned wanting to tackle [thing]. Has that happened yet?" gives them a thread to pull and makes the check-in feel like the continuation of a relationship.

One is about the customer's experience. The other is about the contract. Mixing the two tells the customer that the check-in was never really about how they're doing, and they'll notice.

Keep check-ins focused on outcomes and relationship until the renewal window is approaching. At that point, a natural bridge exists: "Given what you've been building with [Product] this year, I wanted to start the conversation about what next year looks like." That framing respects the check-in history while opening the renewal topic.