nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moved churn with response routing — here's our setup

bea_ng_784ad

Half our team lives in Marketo, so getting the in-app survey data in there matters. How clean has that been for you?

Find more posts tagged with

Comments

carl_reyes_f1e05

Worth checking your CES window. Ours was skewed until we narrowed it.

maya_soto_173d0

Curious what cadence you landed on. We over-asked and the health score tanked.

yuki_pace_9ddb7

Same setup here. In our case it came down to response routing being too broad.

hana_reyes_7cf07

We hit this too. Scoping session replay to our SMB tier first made it manageable.

sam_dunn_a4b8e

Honestly journey alerts didn't move response rate for us. Slack did more.

carl_quinn_1976f

Spent a week on this. The fix was tying the in-app survey to the account owner field.

carl_pace_098c2

+1. The Segment step is where ours kept breaking.

bea_boyd_01cb1

Have you tried routing it through Microsoft Teams? Fixed the renewal rate gap for us.