Recruiting · Available
Ashby for Claude, ChatGPT and Copilot
Because Ashby separates jobs, postings and openings, a vague question can get the wrong count. Recruiters, hiring managers and recruiting operations who ask Claude, ChatGPT or Copilot about Ashby get answers that name which one they mean: applications at each interview stage, overdue feedback, scheduled interviews, offers in approval. Moves and offers are prepared for confirmation. Ashby is turned on after a guided pilot run by your recruiting operations team.
- Status
- Available
- Setup
- Guided pilot with your team
- AI assistants
- Claude, ChatGPT, Copilot Studio
- Access
- By role, view only or with approvals
Ask in a sentence
What can your team ask Ashby?
Questions from recruiter, recruiting operations lead, hiring manager and others, answered from live Ashby data and only for the people allowed to see them.
Records it works with
- Jobs
- Openings
- Job postings
- Applications
- Interview plans
- Interview stages
- Feedback
- Offers
- Recruiter
“Which applications for the Staff Backend Engineer job are in the Technical Interview stage with feedback overdue?”
- Recruiting operations lead
“Which jobs are open but have no interview plan assigned yet?”
- Hiring manager
“How many openings on my team are still unfilled, and what is the target start date for each?”
- Head of talent
“What is the pass-through rate from recruiter screen to onsite for each engineering job this half?”
- Recruiting coordinator
“Which onsite interviews scheduled for Thursday still have an interviewer who has not accepted?”
- Finance partner
“Which offers in approval exceed the budgeted salary for their opening?”
Changes, governed
What the assistant can prepare in Ashby
The assistant never saves on its own. It prepares the change, the person checks the preview and confirms, and anything above your limits waits for an approver.
- 1 Prepare The assistant drafts the change from the request.
- 2 Preview and confirm The person sees exactly what will change.
- 3 Approve Above your limits, a second person decides.
- 4 Saved and logged Written to Ashby under a named person.
-
Move an application to the next interview stage
The job's recruiter or hiring manager confirms the stage change before it saves.
-
Create an opening against an existing job
New openings need finance and the department head to approve the headcount.
-
Draft an offer for an application
Offers follow your Ashby approval chain, and salaries above the opening budget need finance.
Example rules. During the pilot you set the limits, the approvers and which roles may prepare each change.
Why it needs care
Governance built for Ashby
Ashby joins recruiting data with detailed analytics, so candidate information is easy to slice many ways. Leaders can be limited to totals while recruiters see names. Stage moves and offers are previewed, and headcount or offers above budget need approval. Each analytics question about candidates is kept under the name of whoever ran it.
-
Sign-in by work email
Only people you invite, with a one-time code. No shared logins.
-
Roles per tool
Each role reaches only the Ashby records it needs.
-
View only, if you prefer
Admins can keep a connection to lookups with one switch.
-
A preview first
Every change is shown in full before anything is saved.
-
Approval rules
Above your limits, a second person approves the change.
-
One audit log
Every request tied to a named person, ready for review.
Setup
How Ashby gets connected
We connect Ashby for your team in a guided pilot, on the same gateway every app uses. No code on your side.
- 01
Agree the questions
We list the Ashby questions and changes your team needs, and who may use each.
- 02
Connect with your admin
Your Ashby administrator creates a dedicated integration user with only that access.
- 03
Test with your people
A small group tries it in Claude, ChatGPT or Copilot while we tune the tools.
- 04
Roll out with rules
Roles, approval limits and the audit log are in place before everyone joins.
Then people use it from the assistant they already have
Ashby questions
What is the difference between a job, a posting and an opening in Ashby?
In Ashby a job is the role, a posting is the advert that collects applications, and an opening is one seat of headcount. The assistant keeps these apart, so a question about open seats is never answered with posting counts.
Can it answer Ashby analytics questions?
Yes. Leaders can ask about pass-through rates, time in stage or source of hire using live Ashby data. Roles decide whether they see named candidates or only the totals for each job.
Can interviewers use it to submit feedback?
Interviewers can ask about their upcoming interviews and see which feedback they still owe. Writing and submitting feedback stays in Ashby, so the interviewer's own words are what the hiring team reads.
Does mcpbizapps keep a copy of our Ashby data?
No. When someone asks a question, mcpbizapps reads the answer live from Ashby through a dedicated integration user and returns it without storing it. The audit log records who asked, which tool ran and the result, with personal fields and free text removed.
Ashby is a trademark of its owner. mcpbizapps is not affiliated with Ashby; the name describes the connection only.
Related
Often connected alongside Ashby
Part of People and HR: Employee records, pay, hiring and training.
Start
Bring Ashby into your AI assistant
Tell us how your team uses Ashby, and we will plan a guided pilot around your own questions.
- We agree the tools and approval rules with you
- Your admin creates the integration user; no code
- Business data is read live and not stored
Thank you
We received your request and will reply by email to find a time.
Last updated