Skill

cx-demand-driver-attribution

Use to attribute contact volume spikes to product releases, campaigns, billing events and operational changes — with a shared calendar, difference-in-differences thinking and explicit limits on causal claims. Trigger for "what caused the volume spike", demand driver attribution, release drove ticket

Claim this listing

Connect your GitHub to prove you own or maintain this listing. We verify repo access automatically — most publishers are confirmed in seconds.

1Connect GitHub
2Submit your claim
3Auto-verified, or reviewed within 48h