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; } } }

Webhook for journey alerts firing twice — dedupe advice?

omar_hale_ceafc

Quick one. Since we added a second product line, our CES has been all over the place. Is that a journey mapping config issue or are we reading it wrong?

Find more posts tagged with

Comments

sam_rourke_131a5

Have you tried routing it through Salesforce? Fixed the CSAT gap for us.

diego_dunn_66c67

Honestly auto-theming didn't move CSAT for us. Slack did more.

nadia_okafor_b5793

Spent a week on this. The fix was tying segments to the account owner field.

zoe_ng_c9a91

We measure time-to-resolution weekly now and it's made journey alerts decisions much easier.

zoe_voss_df56c

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

mira_ng_085e2

We hit this too. Scoping auto-theming to trial users first made it manageable.

liam_calvi_9ecb1

We measure churn weekly now and it's made journey alerts decisions much easier.