PostHog / meta

This is a place to discuss non-product issues in public.
MIT License
18 stars 4 forks source link

Messaging: Teams Trial #254

Closed joethreepwood closed 2 weeks ago

joethreepwood commented 2 weeks ago

We're introducing a free 14 day trial for the Teams plan. People have to manually enable it via the billing page. When they do, we send an event and trigger an email. After 11 days, we trigger another email with another event. If they don't cancel, we trigger another event and a final email.

I want to generally avoid negative messaging here. It's generally more urgent and impactful, but positioning this as what you will lose if you cancel just feels 🤮. So, I'm proposing the following emails to keep it positive.

Day 1

Screenshot 2024-11-04 at 14 16 00

Day 11

Screenshot 2024-11-04 at 12 51 19

Day 14

Screenshot 2024-11-04 at 12 50 37

Flagging @zlwaterfield for approval on copy. If this looks good, all I need to know are the names of the events we trigger for each event -- then I configure and roll this out in Customer.io.

zlwaterfield commented 2 weeks ago

These look great- thank you @joethreepwood! The only thing is that for the third email, they will get charged immediately, so "Scenario 2" won't really work. Maybe just say reach out to us?

Events are under the transactional email event with templates:

These emails should be able to go in the existing billing campaign

joethreepwood commented 2 weeks ago

These look great- thank you @joethreepwood! The only thing is that for the third email, they will get charged immediately, so "Scenario 2" won't really work. Maybe just say reach out to us?

Gotcha. Changed that line to "No worries, just get in touch and we'll see what we can do. "

These emails should be able to go in the existing billing campaign

Great. That's all set up and live now. Though FYI we'll need a new method if we keep adding emails using this template method. Customer.io's campaign builder limits you to 20 variations on a path, which is what we're at now.

This is only going to be a short-term limitation. Longer term I want to move these to a new transactional API method (and/or the messaging product) but I haven't started scoping that out yet.