The moment an HR manager submits a ticket and hears nothing for four days — while payroll is broken and employees are asking questions — is when they realize there is no reliable way to know if anything is actually happening on their case. They can't escalate intelligently because they don't know who owns it, what department it landed in, or whether the rep who touched it last is even still at the company.

This gap persists because the incumbent has no incentive to surface visibility that reveals their own slow response times. Transparency about ticket aging would be damaging to them competitively, so the support portal stays opaque by design. The HR manager, who is the user, is almost never the economic buyer — the CFO or CHRO who signed the contract rarely hears about these daily frustrations loudly enough to escalate them to the vendor.

What users describe is specific: tickets closed before they can review responses, conflicting answers from different departments, and no way to know which team handles which type of issue. There's no unified thread that shows the full history of a case, who touched it, and what was said — so every new rep starts from zero, and the HR team spends time re-explaining the same context they already provided.

This is a recurring business need because every ADP client has support interactions constantly — payroll runs every two weeks, compliance questions come up monthly, and rep turnover means the context problem never goes away. An HR team that loses an hour every time they re-brief a new rep is losing that hour on a predictable, recurring schedule.

What to build

Build a web app that ingests ADP support case data via email parsing and screen-capture-based logging, then shows HR managers a single timeline per case with every rep who touched it, every response sent, and how many days each status has been held — with automated nudges drafted for cases that go stale past a threshold the HR team sets.

Where to start

Start with companies that have experienced rep turnover in the last 12 months — they have the most acute re-briefing pain and the freshest memory of losing case context, making them easiest to convert without a long sales cycle.

The hard part

ADP doesn't expose a public API for support case data, so ingestion depends on email parsing or manual logging — which creates a fragile data pipeline that breaks whenever ADP changes their email format, and makes the product feel clunky compared to what a native integration would deliver.

How it makes money

Monthly subscription per company, not per seat — HR teams are small but the pain is company-wide, so a flat $199–$499/month fits the budget and removes friction for teams of two or three people sharing the tool.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Core HR.

More ideas in Core HR