HR payroll issue escalation playbooks

When something breaks in payroll or HR — a garnishment not applied, a new hire missing from a pay run, a state tax ID rejected — the HR team has to figure out which department at ADP even handles that type of issue, then navigate the phone tree, then potentially re-escalate if the first person doesn't know the answer. Users describe exactly this: 'you have to go through so many different departments and people to get it resolved, which takes forever' and 'it's confusing as to who you deal with for each specific issue.'

This gap exists because ADP's internal department structure is opaque to clients by design — or at least by neglect. The vendor has no incentive to publish a routing map that would make it obvious how fragmented their support org is. And the HR manager who burns 90 minutes navigating phone trees is a user, not a buyer, so the CHRO who renewed the contract never fully accounts for this lost time.

What's missing is a structured, community-maintained map of exactly which ADP department handles which type of issue, what information to have ready before calling, what escalation language actually works, and what the realistic resolution timeline is for each issue type. Not generic advice — specific playbooks built from real HR practitioners who've solved these exact problems before.

This is a business and not a one-time resource because ADP's internal structure changes, new issue types emerge (new state leave laws, new ACA reporting rules), and new HR managers are constantly starting fresh without the institutional knowledge their predecessor had. The community that generates the playbooks is also the audience that pays for access — a structure that improves with scale rather than decaying.

What to build

Build a searchable, community-contributed knowledge base where HR practitioners document step-by-step ADP escalation paths for specific issue types — including which department to call, what account info to have ready, what escalation phrases move things faster, and how long resolution actually took — with a moderation layer that flags outdated entries when ADP's structure changes.

Where to start

Seed the first 30 playbooks by interviewing HR practitioners in ADP user communities on LinkedIn and Reddit who have already publicly complained about support navigation — they've already articulated the problem and often have the exact routing knowledge needed, making them natural first contributors.

The hard part

Cold start is brutal — the product is worthless with ten entries and genuinely useful with five hundred, so the founding team has to either manually seed the knowledge base from interviews or find a community of ADP practitioners willing to contribute before the product has any proven value.

How it makes money

Free for community contributors who add verified playbooks; $29/month per individual or $149/month per HR team for read-only access — the asymmetry rewards contribution and creates a sustainable incentive without paywalling the people who make the content valuable.