KoltrixFrom Trial to Sales Call: Emails for Product-Qualified Leads
When trial usage says someone is ready to talk, the email that hands them from automation to a human matters. How to write it without sounding creepy.
On this page(8 sections)
Some trial users will never talk to a salesperson, and shouldn't have to. Others are quietly doing exactly what your best customers did in their first week, and a well-timed email from a real person is what turns that usage into a contract. The hard part is the handoff: moving someone from automated onboarding to a human conversation without it feeling like you were watching over their shoulder.
What makes a lead "product-qualified"
A product-qualified lead (PQL) is a trial user or free account whose behavior in the product suggests they're a good fit and likely to buy. Unlike a marketing lead, who downloaded something, a PQL has already done real work in your product.
Good PQL signals are specific to your product, but they tend to fall into a few groups:
| Signal type | Examples |
|---|---|
| Depth | Completed the core workflow more than once; connected a real data source |
| Breadth | Invited teammates; more than one person active in the account |
| Fit | Company size or domain matches your ideal customer; uses the integration your best accounts use |
| Intent | Visited the pricing page more than once; hit a plan limit; read the security page |
Pick two or three signals from different rows. A single signal on its own, like a pricing page visit, is too noisy. A combination, such as three active users plus a hit on a plan limit, is much more meaningful.
Write the definition down and agree on it with whoever does sales. Even if that's just you, a written definition stops you from emailing everyone who logs in twice.
When to hand off
Timing matters as much as the signal. Reach out:
- Soon after the signal fires, ideally within a business day. The person is actively evaluating now.
- Before the trial ends, not on the last day. Last-day outreach feels like a sales tactic because it usually is one.
- After automated onboarding has done its job. If the user hasn't finished setup, a setup email helps more than a sales email.
Once someone gets a personal email, pause the automated marketing-style emails for that account. Nothing undermines a thoughtful personal note like a generic "Have you tried our reports feature?" arriving the next morning.
Writing the first personal email
This is where most PQL programs go wrong. The temptation is to show that you know what the user has been doing: "I saw you created 14 projects and invited 3 colleagues yesterday afternoon." That reads as surveillance, even if every word is true and the data was collected under your privacy policy.
The better approach: use the data to decide what to write, but don't recite it.
A version that feels creepy
Hi Alex, I noticed you've created 14 projects since Tuesday, visited our pricing page three times and invited Jordan and Sam. Looks like you're ready for the Team plan! Can we hop on a call this week?
A version that feels helpful
Subject: Questions about rolling this out to your team?
Hi Alex,
I'm one of the founders here. Teams that start using the product together usually have a few questions around permissions and billing before they decide, so I wanted to offer a direct line.
If it's useful, I'm happy to do a 20-minute call to walk through how other teams set things up. Or just reply here with any questions. I read these myself.
If you're all set, no need to reply.
The second email is clearly prompted by team adoption, which is the signal, but it frames the outreach around what teams in that situation need rather than what you observed. It offers two ways to engage, one of which needs no meeting. And it makes ignoring it perfectly acceptable.
Rules for the email
- Send it from a real person, with a real name and a reply address that person reads.
- Plain text, no banners or buttons. It should look like it was typed.
- One ask, and make the low-effort option (reply with a question) as valid as the call.
- Mention the general situation, not the specific clicks.
- Keep it under 120 words.
When they reply
Most replies will be one of three things:
- A question. Answer it fully in the email. Don't use the question as a bargaining chip for a call. A good written answer builds more trust than a meeting they didn't ask for.
- Yes to a call. Send a scheduling link or two times, and confirm what you'll cover.
- "We're fine, thanks." Thank them, and mean it. They're probably going to buy on their own, which is the best outcome.
When they say no, or say nothing
No reply after one follow-up means stop. Send one brief follow-up three or four days later, on the same thread, and then let the account return to normal onboarding. Mark the account in whatever you use to track leads so nobody emails them again for the same signal next week.
An explicit no deserves a gracious reply and nothing more:
Thanks for letting me know, Alex. If anything comes up later, just reply to this thread.
Measuring whether the handoff works
Compare trial-to-paid conversion for PQLs who received outreach against similar PQLs who didn't. You'll need a holdout group of some accounts that meet the definition but don't get the email. Without it, you can't tell whether outreach caused conversions or just coincided with accounts that would have converted anyway.
Also track:
- Reply rate to the first personal email
- How many replies were questions versus meeting requests
- Time from signal to outreach
- Conversion rate of accounts that replied versus those that didn't
A handoff checklist
- PQL definition written, with two or three signals from different categories
- Outreach within one business day of the signal, and before the trial's last days
- Automated promotional emails paused for accounts that get personal outreach
- Email from a named person, plain text, under 120 words, one ask
- Observed behavior used to pick the message, not recited in it
- One follow-up maximum, then back to normal onboarding
- Holdout group in place to measure impact
Key takeaways
- A PQL is defined by a combination of usage, fit and intent signals, written down in advance.
- Reach out soon after the signal and well before the trial ends, from a real person.
- Use what you know to choose the message, but don't show your work. Specific click data reads as surveillance.
- A helpful written answer is a better outcome than a reluctant meeting, and a clear no is a fine result.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
