Follow up a cancellation while it’s fresh.

Your backend sends Behavly the event, a Trigger Campaign writes to the person from what they did, and every reply is filed by what it says.

Start for free

One cancellation, one conversation.

Cancellation follow-up in Behavly is a Trigger Campaign. Your backend sends an event like subscription_cancelled with the person’s email and details such as the plan, and the campaign takes them in the moment it arrives. Each email is written from what they did, and every reply is filed in the Unibox by what it says.

From your backend, at once.

Each time someone cancels, your backend sends the event with their email and its details, like the plan. Every active Trigger Campaign that starts on it takes them in the moment it arrives.

Each reply with what they did.

Every reply lands in the Unibox with the sender’s history on your site attached, filed under the status it fits: Follow up for a question, Suppress for a no.

A draft waits for you.

When they ask something, a suggested answer is written from the thread and their history and waits in the Unibox for you to check. Behavly does not auto-reply, and a draft is never sent without you pressing send.

Try it without code.

Every trigger’s page has Send a test event. It sends the event for the address you enter, exactly as your server would, and the last events show what each one did.

From a cancellation to a conversation.

Make a trigger.
Give it a Name, like Subscription cancelled. The Key follows it (subscription_cancelled): it is what your code sends. Under Payload, list the details each event carries, like the plan.
Send the event from your server.
Create an API key with Send events only access, keep it on your server, and send each event to send_event with the person’s email and its details.
The plan goes into the email.
Each payload field can go into the emails as a merge tag, like {{event.plan|your plan}}, where the words after the | are what it says when the event carried no value.
Each reply is filed by what it says.
Behavly reads every reply to a campaign email and gives it the status it fits: High-intent when they are interested, Follow up for a question, Suppress for a no or an unsubscribe. A status you set yourself is never replaced.
If they cancel again later.
If it happens again is Once per person by default. Again after a break lets someone go through the path again 7, 30 or 90 days after leaving.

The rules around every cancellation.

If it happens again: Once per person by default. Again after a break lets someone go round again 7, 30 or 90 days after leaving.
When they write to you: A reply ends the path by default, and their other campaigns wait 3 days. Out-of-office replies don’t count.
Reply drafts: On by default: when they are interested or ask something, a suggested answer waits in the Unibox for you to check and send.
Goal: Name the action that brings them back, like resubscribed. Each person who reaches it is credited to the last email they got.
Send events only: A key with this access sends events and nothing else, so if it ever leaks it cannot read your contacts or change anything.
Sending window: An event that arrives at night starts the path, and the first email waits for the window you set.

Questions about cancellation emails.

Does Behavly know when someone cancels?

Only if your product tells it: your backend sends an event when someone cancels, with their email, and a Trigger Campaign starts on it. Events from before the campaign was active don’t count.

Will Behavly answer their reply on its own?

No. Behavly does not auto-reply. A suggested answer can wait in the Unibox, and a draft is never sent without you pressing send.

What if they come back?

Name the Goal as the action that brings them back, like resubscribed. Reaching it is counted, and with They reach the goal on under Leave when, it ends their path.

Meet the Behavly Agent.

It reads what each user does in your product and writes their follow-ups. Free to start, no credit card.