Less Interview Back-And-Forth
Ask what interviews you have this week, whose scorecard is still owed, or who showed up to last week's onsite — answered from the interview record. It never books, reschedules, or cancels.
Why Interview Schedules Cost More Than They Should
The mechanics of scheduling interviews — booking the room, sending the invite — are largely solved. The friction is in everything around the interview: knowing what's coming, what happened, who still owes a scorecard. Interview Hub Agent surfaces that without a portal login.
Interviewers Walk Into Meetings Cold
Engineer-on-rotation has three interviews this week. They don't remember the candidates, the roles, or what the prior round covered. Calendar invite says "interview"; the candidate's name says nothing without context. Result: generic interviews, generic signal.
Scorecards Go Missing For Days
The interview finishes. The interviewer means to write the scorecard "later today." Three days pass. The pipeline stalls because the recruiter is chasing scorecards through DMs instead of getting them through the system. Nobody wants to be the chaser.
Recruiters Can't See The Week At A Glance
"What's the interview load looking like? Who's overloaded? Whose pipeline is at risk because a scorecard is overdue?" — the ATS has the data; pulling it requires a custom dashboard the team doesn't open between standups.
Post-Interview "Did They Show Up?" Is A Manual Check
Cancellations, no-shows, reschedules — these signal candidate issues (or scheduling-team issues) that need follow-up. Without a no-show + cancellation view per recruiter, the signals get lost in the volume.
Hiring Managers Don't Know Where Each Candidate Is In The Loop
"Did Priya clear the panel? Are we offering? Who still owes a scorecard?" — the hiring manager pings the recruiter for status three times a week per candidate. A loop with four candidates and five interviewers turns into a dozen status-check Slacks before the Friday debrief, eating the recruiter's afternoon every week.
Interviewer Load Goes Lopsided And Nobody Notices Until Burnout
One senior engineer ends up on 11 panels in a month while two peers do three each. The load imbalance is invisible without a per-interviewer rollup, so the over-asked interviewers start declining requests right when pipeline is heaviest — and the team finds out the hard way at the next sprint retro.
Interview Hub Agent At A Glance
AI Interview Hub
Upcoming, past, detail, summary — the interview week in chat.
Inside Interview Hub Agent — The Actual Capabilities
Every block below maps to a real tool against the Interview Hub app. It surfaces interviews and scorecard status, and can add an open interview slot after a confirmation, but never books, reschedules, or cancels. Schedule changes happen in the app or via Recruiting Agent's gated scheduling tool.
Upcoming Interviews — Walk In Prepared
"What interviews do I have this week?" — the agent returns the canonical list, with candidate, schedule, format, and panel composition where the record has it. Default lookahead is 14 days; up to 60 days when the user asks for "this quarter."
list_upcoming_interviews— interviews the user sits on, scheduled or oversees, each saying the user's part in it, with candidate and schedule (default 14 days ahead, max 60).- Scoped to the user — interviewers see their own interviews; recruiters see the slate they own.
- Panel context surfaced — who else is on the loop, when each interview is, what format.
- A read-only lookup — the agent shows the schedule; booking changes happen in the app.
Full Interview Detail — Candidate, Round, Panel, And Scorecards
For any interview by ID or candidate name, the agent returns the record — candidate, round, participants, time, format, current status, and whether each scorecard has been submitted. Useful both for prep ("who's on the panel?") and for ops ("did everyone submit?").
get_interview_details— full detail for one interview by ID, including candidate, round, participants, status, and scorecard state.- Scorecard state surfaced — submitted vs pending per interviewer, not just an aggregate.
- A read-only lookup — scorecards are written in the app; the agent surfaces whether each one landed.
Past Interviews And Outcomes
"What interviews did I do last month? Which ones were no-shows?" — the agent returns completed interviews with outcome and scorecard status, filterable by status (completed, cancelled, no_show). Default lookback is 30 days; up to 180 days, or a named period like "last quarter".
list_past_interviews— past interviews with outcome and scorecard status (default 30 days back, max 180, or a from/to date range).- Status filter — filter by completed, cancelled, or no_show to surface the specific signal you're tracking.
- Cancellations + no-shows queryable — the leading-indicator signal recruiters need to follow up on.
- A read-only lookup — historical lookups don't change history.
Weekly Throughput — Volume And Scorecards Owed
One call gives the recruiter the week at a glance — counts by status, what's upcoming, the scorecards you still owe, and the drafts still waiting on you or the candidate. The scorecards-owed number is the one most worth watching.
get_interview_schedule_summary— counts by status, upcoming this week, and the scorecards you still owe.- Scorecards owed surfaced — every scorecard you still owe, however old.
- Throughput visible at a glance — upcoming, completed and cancelled counts, plus drafts awaiting the candidate, in one response.
- Audit-ready output — every read logs the requesting user and which tool ran.
Who Is Waiting, When People Can Interview, Whose Turn It Is
"Who is waiting for their next round? When can Rachel and Sam both interview next week? Whose turn is it in the phone screen pool?" — read from the To Schedule list, real calendars and the interviewer pools, each limited to the people those pages admit.
list_candidates_to_schedule— who is waiting and for which round, with a link to To Schedule, where Send link is pressed.find_open_interview_times— when named people are free, from calendars, leave, shifts and interviews, and whose calendar it couldn't read.list_interviewer_pools— who is in each pool, who is still observing, and whose turn is next.
Outcomes Teams Can Measure
Interview Hub Agent compresses the time interviewers spend re-orienting before interviews and recruiters spend chasing scorecards after them. Compare against your pre-agent baseline.
- Time to scorecard after an interview — median hours from the interview's end to its scorecard, vs the pre-agent baseline.
- Overdue scorecard rate — share of interviews whose scorecards are still owed after 48 hours, a leading indicator of pipeline drift.
- Interviewer prep — "what's coming up?" queries — interviews per interviewer per week where the agent surfaced context before the meeting.
- Cancellation + no-show visibility — share of cancellations/no-shows the recruiter saw and followed up on within 24 hours.
- Weekly throughput awareness — share of recruiters who can answer "what's our interview load this week?" without opening the ATS.
No Bookings From Chat · Scheduling Stays In The App
Interview Hub Agent surfaces and reports, and it has two actions, each behind a confirmation: adding an open interview slot to your availability, and preparing pasted interview questions for review before import. It never books, reschedules, or cancels. Schedule writes happen either in the Interview Hub app or via Recruiting Agent's gated schedule_interview tool, where confirmation is explicit.
- Two actions, both confirmed — adding an open interview slot (your own; a manager or Interview Hub admin can add one for another interviewer) and preparing interview questions for import each ask for confirmation first. No bookings, no reschedules, no cancellations.
- Scoped to the user — interviewers see their own interviews; recruiters see their own slate; no cross-team end-runs.
- Scorecards are written in the app — the agent surfaces which are owed and submitted; the scorecard itself lives where the interviewer wrote it.
- Audit trail on every retrieval — every read logs the requesting user and which tool ran.
WHAT TEAMS TRY INSTEAD
The four alternatives — and why none of them show the scorecards owed or who is waiting for a round
When a recruiter needs to chase a scorecard or a hiring manager needs loop status, they reach for one of these four. None of them combine upcoming, past, and scorecards-owed visibility across all three audiences (interviewer, recruiter, hiring manager) in one chat surface.
Pasting calendar entries into ChatGPT, Claude, or Copilot
General-purpose AI guessing context from a calendar block
- Interview Hub Agent reads the live interview — candidate, role, panel, scorecard status — not a one-line calendar title
- Scorecards owed visible at a glance instead of DM-chasing five interviewers
- Every tool call logs the requesting user and which tool ran
GoodTime AI, Calendly AI, Modern Hire AI
Vendor-trapped scheduling AI focused on the booking, not the loop
- Reads interviews with the Recruiting candidate record and the interviewer's availability — vendor AI sees only the bookings it made
- Interviewers, recruiters, and hiring managers share one chat surface without per-seat licenses across a separate scheduling app
- Survives a scheduling-vendor migration; the agent's tools repoint at the new source
Custom recruiting dashboard
A TA-ops team's six-month build, then forever maintenance
- Shipped already — TA ops doesn't have to plumb the To Schedule list, scorecard tracking, or per-role views
- No tool reschedules or cancels — no risk of the chatbot accepting "reschedule this interview" and breaking the booking
- Inherits new tools as the platform evolves
The manual fallback — "Slack the recruiter for status"
The default when AI tools fall short
- Interviewers walk into interviews warm — context one chat away, not Slack-DM the recruiter
- Scorecards owed surface per person instead of a Friday afternoon of chasing
- No-shows and cancellations visible weekly, not in a sprint retrospective
PLATFORM ADVANTAGE
Interview Hub Agent inherits everything the platform already runs
A custom recruiting dashboard has to plumb each of these. Interview Hub Agent gets them for free.
Cross-app data plane
Reads interviews with the Recruiting candidate record, interviewer availability and each person's role — one chat surface, not three.
Role-scoped reads
Interviewers see their own interviews; recruiters see their slate; hiring managers see their loops. The agent inherits the recruiting role model server-side.
Audit trail
Every tool call, lookups included, logs the requesting user and which tool ran — useful when candidate-experience or DE&I audit asks come around.
Ask in your working language
Global recruiting teams query loop status in their working language. Ask AI replies in the language each person asks in.
Frontline-ready prep
Interviewers prep on a phone the morning of the interview — same mobile app, no separate ATS or scheduling tool to launch.
Provider-agnostic model tiering
The platform assigns each agent one model tier suited to its work — set for the agent, not picked per question.
INDUSTRY FIT
Industries where interview-scheduling AI moves the most weight
Interview Hub Agent shines wherever interview volume is high, panels are large, or missing scorecards slow the loop.
Technology
Engineering loops with five-interviewer panels close faster because missing scorecards surface per interviewer, per loop, in chat.
Financial Services
Multi-round interview loops for analysts and traders track to outcome — recruiters surface stalled loops without DM chasing.
Professional Services
Partner-track loops, client-facing panels, and case-interview rounds run with scorecards-owed visibility across geographies.
Healthcare
Clinician hiring with multi-stakeholder panels (department head, peer, ops) closes faster because scorecard status is visible the day-of.
Retail / Hospitality
High-volume seasonal hiring loops surface no-show patterns per recruiter and per location — interventions happen before peak hiring.
Public Sector
Multi-round screening and security-clearance loops are tracked to outcome. AI requests go to the platform's configured model providers.
WHY MANGOAPPS WINS
An embedded interview agent beats GoodTime AI, a horizontal chatbot, or a DIY dashboard on every axis
The argument recruiters, hiring managers, interviewers, and IT all share — and the one a single-vendor scheduling AI structurally cannot answer.
Cheaper than the alternatives
No per-recruiter GoodTime license, no per-seat ChatGPT license, no six-month dashboard build — and coordinator afternoons stop going to scorecard chasing.
More secure
No booking, rescheduling, or cancelling from chat, and its two actions ask for confirmation first. Role-scoped reads. Every tool call logged. AI requests go to the platform's configured model providers, like every MangoApps agent.
Easier to deploy
Part of the Interview Hub app. Once the app is licensed and enabled, turn the agent on and the scorecards owed surface the same day.
Easier to use
One chat surface for upcoming, past, detail, and weekly throughput — no separate ATS dashboard, no per-loop spreadsheet.
Easier to manage
Who can see what, the scorecard deadline and the agent's own on/off switch are set under Interview Hub's Settings. One set of roles and permissions.
Easier to extend
New tools ship as agent capabilities — no DIY dashboard port.
AI is actually better
A scheduling-tool copilot can list bookings. Only Interview Hub Agent can also see the candidate's round, the panel's scorecard status, and the scorecards still owed — and answer all three in one chat thread.
At our head office within HR, marketing, and finance, we use ChatGPT quite a bit, and MangoApps AI Helper is a useful tool for us. As I go around to the stores, I’ve been showing them how the AI Intranet Helper can find things and answer plain language questions about our resources, and they’re quite excited about that.
Alison van Zijl
Head of Human Resources
Full House
Customer Success
MangoApps Customers
Organizations that trust MangoApps to run every workflow across their workforce.
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Frequently Asked Questions About Interview Hub Agent
It reads the interview workflow — list_upcoming_interviews (default 14 days ahead, max 60), get_interview_details for one interview by ID or candidate, list_past_interviews (default 30 days back, max 180, filterable by status), get_interview_schedule_summary for weekly throughput and the scorecards owed, list_candidates_to_schedule for who is waiting for a round, find_open_interview_times for when named people can interview, and list_interviewer_pools for who is in each pool and whose turn is next. Two more act, each after you confirm: one adds an open interview slot to an interviewer's availability, and one prepares pasted interview questions for review before they are imported into the question bank.
No. Interview Hub Agent has no tool that books, reschedules, or cancels an interview. Scheduling writes happen either directly in the Interview Hub app, or via Recruiting Agent's gated schedule_interview tool, which requires explicit confirmation. What this agent can do is add an open slot to your availability, after you confirm.
get_interview_schedule_summary returns how many scorecards are owed and on which interviews. get_interview_details on a single interview surfaces each interviewer's scorecard state (submitted or not yet). The agent never submits a scorecard itself — interviewers write it in the app.
Interviewers, recruiters, and hiring managers. The tools are scoped to the user — every interviewer sees their own slate, every recruiter sees the jobs they recruit for. The agent doesn't end-run around role-based visibility.
Time to scorecard after an interview, overdue scorecard rate (> 48 hours), interviewer prep query volume, cancellation/no-show visibility, and weekly-throughput awareness. Compare against your pre-agent baseline.
Let's Talk
Every team. Every employee. Every workflow. One AI platform — built for the frontline. Since 2008, trusted by 2 million+ users with an NPS of 78.
Why Choose Us?
- Frontline AI: Governed AI for every employee and workflow.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Prefer to explore first? Ask AI about Interview Hub AI Agent →