Skip to main content
All integrations
CommunicationOn the roadmap

Slack and Expert Hire

Send shortlist alerts, candidate review nudges, and hiring workflow updates into recruiter channels.

Bring candidate movement into the channels where recruiters and hiring managers already collaborate.

Nothing on this page describes shipped behaviour. It describes the mapping we are building to.

Slack connected to the Expert Hire workflow
A practical path from Expert Hire to Slack.
Workflow coverage

What the Slack connector is being built to do.

These are the workflows this connector is scoped around. They describe the target, not shipped behaviour. Until it lands, the same outcomes are reachable through the MCP connector and the built-in pipeline board.

01

Post shortlist alerts when candidates pass screening thresholds.

02

Notify owners when reportcards need review or overrides.

03

Share daily summaries for open roles, stalled candidates, and drive progress.

Whatever the connector moves, the evaluation does not change. Every stage is one of five modes: resume screening, AI interview, human-led interview, AI prompt assessment or coding test. All of them score onto one rubric, and every score traces back to the transcript, the live code, the skills you weighted and the JD you set up.

Planned field mapping

What moves, and which way.

Communication connections are one-way by design. Expert Hire posts what changed; the decision stays in the product where the evidence lives.

This is the mapping we are building the Slack connector to. It is a plan, not a description of live behaviour.

  • Shortlist event

    Out of Expert Hire

    A message when a candidate crosses a threshold your workflow defines, into the channel that owns the role.

  • Reportcard summary

    Out of Expert Hire

    Score, verdict line and a link back to the full report, so triage can happen without opening a second tool.

  • Review request

    Out of Expert Hire

    A nudge naming the owner when a round is waiting on a human reviewer rather than on the system.

  • Digest

    Out of Expert Hire

    A scheduled summary of open roles, stalled candidates and rounds still awaiting review.

What you are looking at: the built-in pipeline board every plan gets, with live counts on each stage column, source tags on each card and search by name or email. The later stages appear once the frame is wide enough for them. This is the side of the mapping Expert Hire owns. Sample data.

The board is the fallback, not the consolation prize.

Nothing on this page has to ship before you can hire. The pipeline board above is included on every plan, it is where candidates land whether they arrive by upload, referral or an assistant over MCP, and it is where reportcards attach. A connector changes where the record lives, not whether you can run a round.

Agencies get the same thing per client. One workspace runs many client companies, each with its own roles, pipeline and rubric, and data never pools across clients.

Auth, keys and plan access

How the connection is secured, and what it costs to open.

Every integration on the platform authenticates through the same surface, whether it is a packaged connector or something your team builds. Here is that surface, and the plan tier this particular one sits behind.

OAuth on the MCP server.

The remote MCP server that exposes Mia to AI assistants is OAuth-protected. Financial actions, team-admin changes and destructive operations are excluded by design.

Audit trail on every action.

Role-based access control, audit logs, encryption in transit and at rest, and single-tenant separation with no shared candidate pool. Export any time.

Plan gating

No plan gate has been published for this category. The built-in pipeline board and the reportcards that come out of every round are included on every plan.

Using Expert Hire as your own ATS is included on every plan, including the free trial. Team members are unlimited on every tier, so nothing here is priced per seat.

The MCP server is live at mcp.experthire.cloud and connects over OAuth.

Rollout plan when it ships

Four steps, in this order.

This is how a Slack rollout would run once the connector lands. Design partners who register interest get walked through it first.

  1. 1Choose channels
  2. 2Set alert rules
  3. 3Define owner mentions
  4. 4Review notification volume
FAQ

Slack questions, answered.

Ship state, field mapping, plan gating and what to do in the meantime.

Still not sure it fits your stack? Tell us what you run and we will answer honestly.

Slack is not live yet. You can still start today.

Register interest and we will tell you honestly where this connector sits. In the meantime the built-in pipeline board is on every plan, and the MCP server and the MCP connector already reach most of what this one would do.

30-day free trial with 75 Hire Credits. Card required, nothing charged for 30 days.