The problem this solves
The welcome email has the highest open rate a subscriber will ever give you and usually says the least. It is written once, for everyone, and it introduces the company in general terms because nothing is known about the reader. But something is knowable: the email domain resolves to a company with an industry and a size, and the name often resolves to a role. A welcome that says 'here is how teams in logistics use this' reads as written for the reader, and it was.
The Personalization Agent enriches each new subscriber in the week, chooses the use case that fits their industry and role from the ones you provide, and drafts a welcome email that mentions both. The drafts are staged in Klaviyo as flow emails for review rather than sent, so the first automated message a subscriber receives has been read by a person, and the pattern can be tuned before it runs at scale.
How the mission runs
- Pull the week's new subscribers. The Personalization Agent reads Klaviyo for profiles created in the last seven days, separating corporate domains from personal ones and noting which subscribers gave a name.
- Enrich company and role. Corporate domains are resolved to companies with industry and headcount through the enrichment waterfall, and people search adds the role where a name exists. Personal-domain subscribers with no resolvable company receive the general welcome and are marked as such.
- Choose the use case. From the use cases you provide - one per industry or role - the agent picks the one that fits each subscriber and records the choice, defaulting to the most general when the fit is uncertain.
- Draft the welcome email. Each email is written in your voice, mentions the subscriber's industry naturally, describes the chosen use case in two or three sentences, and closes with the same call to action as your standard welcome, so the flow stays consistent.
- Stage in Klaviyo for review. The drafts are staged as flow emails in Klaviyo attached to the welcome flow, unsent, with the industry, role and use case as profile properties, and a summary lists the subscribers, their resolved companies and the use case chosen for each.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
Welcome emails staged in Klaviyo for each new subscriber this week whose company could be resolved, each mentioning the subscriber's industry and one relevant use case in your voice, unsent and ready for review, with industry, role and use case stored as profile properties. Subscribers who could not be resolved are listed and receive the standard welcome.
Make it yours
- Add a second email in the flow that references the subscriber's likely stack when technographics show a relevant tool.
- Run it daily instead of weekly so the personalized welcome arrives within a day of signup.
- Stage the same flow in ActiveCampaign or Omnisend instead of Klaviyo.
- Route subscribers at ICP-fit companies to sales with the enrichment playbook at the same time.
Frequently asked questions
Will the personalized welcome replace the standard one?
Only after you review and enable it. The standard welcome keeps running for unresolved subscribers, and the personalized version is staged alongside it until you switch it on.
How many use cases should I provide?
One per industry or role you sell to is enough; the agent maps subscribers to the closest and tells you which industries had no matching use case so you can add one.
Is the enrichment visible to the subscriber?
Only through a relevant sentence about their industry; the email never states the company's headcount or anything that would feel like a lookup.