Panel Nudge

The problem in detail

Recruiters report that the bulk of their day disappears into repetitive coordination admin, and chasing hiring managers for interview feedback and status updates is one of the worst offenders. Today it is done by hand: scanning the applicant tracking system for missing scorecards, hand-updating spreadsheets, sending Slack nudges, then nudging again days later. Candidates go cold while the recruiter plays debt collector, and the constant low-value chasing is a named cause of recruiter burnout and attrition.

Proposed product

A Slack app connected to the recruiter's applicant tracking system (Greenhouse, Lever or Ashby to start) that watches for interviews with no submitted feedback. It direct-messages the interviewer a few hours after the interview with the candidate name, role, and a short scorecard form they can fill in without leaving Slack, writing the result straight back into the ATS. It re-nudges on a schedule the recruiter sets, escalates to the hiring manager after a chosen number of days, and posts the recruiter a single morning digest of who is blocking which candidate — replacing both the chasing and the status spreadsheet.

Why now

This is a long-standing coordination problem rather than a newly opened window — and the evidence actively narrows it: Greenhouse already ships configurable scorecard reminders that can route via Slack, Ashby advertises configurable interviewer reminders over Slack and email, and an iPaaS vendor sells a ready-made Greenhouse-to-Slack 'missing scorecard' recipe. What remains genuinely open is that hundreds of live staffing-agency coordinator listings still name feedback collection and keeping ATS records current as paid human duties, which suggests the native reminders are not finishing the job.

Smallest useful version

A Slack app for one ATS that does three things only: detect overdue interview feedback, nudge the interviewer in Slack with a one-click scorecard, and send the recruiter a daily 'who's blocking who' summary. If recruiters stop sending manual chase messages within two weeks of install, and median time-to-feedback drops, the idea holds.

Potential ways to charge

• Free digest — £0: the daily 'who's blocking who' summary for one recruiter, read-only, to earn the paid nudging step (free tier typical for comparable Slack tools)
• Per recruiter — £25 per recruiter per month: automated nudges, in-Slack scorecard submission and escalation ladder (typical for comparable per-seat recruiting tools; the evidence contains no pricing)
• Team — £300 per month flat for up to 15 recruiters: multiple ATS pipelines, configurable escalation to hiring managers, SLA reporting on time-to-feedback (typical for comparable tools)
• Agency plan — £900 per month: multi-client workspaces, per-client digests and admin controls for staffing agencies that currently staff coordinators for this work (anchored to the cost of the entry-level coordinator roles observed in job listings, not to any price in the evidence)

Routes to early customers

• Staffing and recruiting agencies currently advertising recruiting coordinator roles with 'feedback collection' in the duties — the listings themselves name the buyer and the manual work
• The Greenhouse and Ashby partner/integration marketplaces, plus the Slack app directory, where recruiting teams already shop for add-ons
• Recruiting operations specialists — the people who configure the ATS and already own reminder settings — approached directly on LinkedIn
• Users of the iPaaS 'missing scorecard' Slack recipe, who have self-identified the problem and built a partial fix they may prefer to buy outright

Main risks

• Two of the three launch ATSs already send scorecard reminders into Slack natively, so the product must be bought for the in-Slack submission form, escalation ladder and digest alone — a much thinner wedge than 'we nudge for you'.
• No review, support thread or search-volume evidence was found of recruiters saying native reminders are inadequate; demand for a separate paid app is unevidenced.
• The riskiest behavioural assumption stands untested: interviewers may mute the bot exactly as they ignore a human chase, in which case nothing improves and churn is immediate.
• A generic automation vendor already sells a partial substitute cheaply, capping willingness to pay.
• Per-ATS partner approval and Slack app review add distribution friction before any revenue, even though the API write paths appear available.

Questions to test first

• Ask ten recruiters using Greenhouse or Ashby whether their native scorecard reminders are switched on, and if so why they still chase manually — this is the single cheapest way to test whether a wedge exists at all.
• Run a two-week manual concierge: a human watches one team's ATS and sends the nudges and digest by hand, measuring reply rate to a bot-style message versus the recruiter's own message.
• Instrument the response-rate question directly: in one pilot, alternate automated DMs and recruiter-sent DMs for the same overdue scorecards and compare submission within 24 hours.
• Price-probe the digest alone: offer the read-only 'who's blocking who' summary and see whether anyone asks to pay for nudging on top.
• Check the Greenhouse and Ashby partner approval requirements and timelines before writing integration code.

Evidence and sources

The sources this assessment is based on. Evidence level: Indicative, counted from these sources as described in how ideas are assessed. Findings are what a source shows; anything the research only inferred is marked as an inference.

Research findings

• SupportsRobert Half job board listings for Recruiting/Recruiter Coordinator roles

  Shows: job-posting-evidence-of-manual-work

  Hundreds of live staffing-agency listings for recruiting coordinator roles describe the job in terms of coordinating interview scheduling across candidates, recruiters, hiring managers and panel participants, and explicitly list 'feedback collection' and keeping ATS records current as core duties. This is a non-community, observed signal that companies pay people (often entry-level, full-time) to perform exactly the chasing-and-tracking work Panel Nudge proposes to automate — the closest thing found to the 'paid to do it by hand' evidence requested.

• Supports · inferenceMetaview blog roundups of Greenhouse and Ashby integrations

  Shows: integration-ecosystem-feasibility

  Third-party tools already perform structured scorecard write-back into Greenhouse and Ashby with candidate-stage triggers and audit trails, which indicates the ATS APIs expose the write paths Panel Nudge needs (read interviews, detect missing feedback, submit scorecard). Buildability of the technical core looks reasonable; the harder parts are per-ATS partner approval and Slack app distribution.

• SupportsTray.ai Greenhouse + Slack connector marketing page

  Shows: vendor-framing-of-the-problem

  An automation vendor markets a Greenhouse-to-Slack recipe built specifically around missing scorecards, stating that missing scorecards are a common bottleneck and that a personalized Slack nudge fires when an interviewer has not submitted within a defined timeframe. Independent vendor demand-framing corroborates the problem; it also shows generic iPaaS tools already sell a partial substitute.

• Weakens the caseAshby Knowledge Base Slack page and Ashby product update on customizable interview reminders

  Shows: incumbent-native-feature

  Ashby's Slack integration sends recruiting notifications, approvals and conversational actions as DMs or channel messages, and a separate Ashby product update describes highly configurable interviewer/candidate reminders over Slack and email with custom intervals. A second of the three launch ATSs covers much of the proposed surface natively, which compresses the wedge.

• Weakens the caseGreenhouse Support documentation: 'Configure a scorecard reminder notification'

  Shows: incumbent-native-feature

  Greenhouse already ships configurable scorecard reminder notifications that can be toggled to send via Slack, managed by job admins on behalf of interviewers. The first ATS target therefore has a native version of the core nudge loop, so differentiation has to rest on the in-Slack scorecard submission form, escalation ladder and recruiter digest rather than on the reminder itself.

Where the problem was reported

Public posts in which people described this problem, grouped into one problem before research began.

• On average, how long do your job reqs take to get approved from the powers above? · r/recruiting · 7 October 2026
• Anyone using Claude in Chrome (or similar AI browser agents) on LinkedIn Recruiter? · r/recruiting · 3 October 2026
• Tips for cutting down time spent on admin work? · r/recruiting · 1 October 2026
• How Do you manage your time · r/recruiting · 27 September 2026
• Auto-outreach tools is the biggest lie in HR tech rn · r/recruiting · 21 September 2025
• just take a break · r/recruiting · 11 August 2025
• i feel without purpose · r/recruiting · 5 August 2025
• What’s the hardest part of recruiting for you lately? · r/recruiting · 31 July 2025
• How do you screen hundreds of resumes when you don’t have a full ATS? · r/recruiting · 3 May 2025

Looked for, not found

• No real product review, support-ticket thread, issue tracker entry or search-volume dataset was found showing recruiters complaining that existing ATS scorecard reminders fail or that they want a better nudge tool. A G2 query returned reviews of an unrelated product (Great Recruiters) rather than relevant complaints. So the key demand question — whether recruiters find native Greenhouse/Ashby reminders inadequate enough to buy a separate paid app — remains unevidenced.