Slack-Based Employee Referral Collection and Follow-Up
A Slack-native referral pipeline that collects employee referrals from forms, messages, and conversations — then routes them to recruiters with full context, tracks them in a table, and pushes qualified candidates into your ATS
Click and drag to move around the canvas and pinch to zoom.
Overview
Employee referrals are your best hiring channel — if your process can keep up
Most recruiting teams know that referrals produce better hires, faster. But the process of collecting, tracking, and following up on referrals is often scattered across Slack DMs, emails, spreadsheets, and your ATS — with no single system tying it all together. Referrers submit names and never hear back. Recruiters lose track of who referred whom. Great candidates slip through the cracks.
This template puts a complete referral pipeline inside Slack, where your team already works. It collects referrals from multiple entry points, uses AI to match candidates to open roles, deduplicates submissions, and delivers curated daily digests straight to the right recruiter. Recruiters close the loop with a single emoji reaction, and referrers get instant updates — all without anyone leaving Slack.
Before this template
- Referrals come in through scattered Slack DMs, emails, and ATS submissions with no central tracking
- Recruiters manually piece together who referred whom and for which role
- Follow-ups fall through the cracks — referrers never hear what happened
- Duplicate referrals waste recruiter time and create confusion
- Employees stop referring because the process feels like a black hole
After this template
- Every referral — whether from a Slack form, a message push, or a direct ATS submission — flows into one system automatically
- AI matches each referral to the most likely open role in your ATS
- Daily digests land in each recruiter's Slack with curated threads for every new referral
- Recruiters react with an emoji to advance, request info, or decline — triggering instant DM follow-ups to referrers
- A central tracker captures every referral with full context: candidate details, role match, recruiter assignment, and status
How it works
The system handles referrals from three different entry points, funneling them all into one unified pipeline:
1. Slack form submissions
When an employee fills out a referral form in Slack, the first Zap fires. It looks up the referrer in Slack, creates a record in the Referrals Workflow Tracker table, then uses a Code step to pull all open roles from your ATS. An AI step matches the referral to the most likely role, and the Zap enriches the record with recruiter assignments, candidate profiles, and job details. Branching paths handle whether the candidate already exists in your ATS, needs a new profile, or has already been referred by someone else.
2. Message pushes from Slack
If someone mentions a referral in a Slack channel without using the form, a teammate can push the message into the referral workflow. AI extracts the candidate name, email, role, and context from the Slack message and thread, then creates a structured referral entry — no form required.
3. Direct ATS referrals
When a referral is submitted directly in your ATS, a webhook catches the event. An agent confirms the candidate and role details, pulls recruiter assignments from the hiring team, and logs everything to the tracker. This ensures referrals made outside Slack still land in the same unified pipeline.
4. Daily recruiter digests
On a set schedule, the Referral Digest Batching Agent reads the tracker for the past 24 hours of referrals, filters out duplicates, and posts curated Slack threads for each recruiter — grouped by their assigned referrals. Each referral gets its own threaded message with full candidate context, so recruiters can act on them individually.
5. Emoji-driven follow-ups
Recruiters react to referral posts with custom emoji to take action. A strong fit reaction sends a DM to the referrer letting them know the candidate will move to screening. A need more info reaction asks the referrer for additional context. A not a strong fit reaction lets the referrer down gently. Every reaction triggers the right response automatically — no drafting, no copying, no forgetting.
What's included
- 4 Zapshandling Slack form submissions, message pushes, direct ATS referrals, and keyword-triggered workflow invitations
- 3 AI Agentsfor recruiter emoji reactions, daily digest batching, and direct referral confirmation
- 1 Zapier Table(Referrals Workflow Tracker) with 25 fields capturing every detail from candidate info to recruiter acknowledgment
- 1 Canvasbringing the full workflow together visually so your team can see how it all connects
Who this is for
- Recruiting teamswho want to reduce manual referral tracking and ensure every submission gets proper follow-up
- HR operationslooking to build a scalable, repeatable referral process without custom tooling
- People teamsat companies where Slack is the primary workspace and referrals come in through informal channels
Frequently asked questions
What apps do I need connected to use this template?
You'll need Slack, an ATS (the template is built for Ashby but can be adapted), Google Sheets (for the referral form responses), and optionally an AI provider like OpenAI. Some AI steps use the plan-included model, so not all require a separate API key.
Can I use this with an ATS other than Ashby?
The template is built with Ashby integrations, but you can swap the ATS steps for your preferred system (Greenhouse, Lever, Workday, etc.). The core logic — collecting referrals from Slack, deduplicating, batching digests, and emoji-driven follow-ups — works with any ATS.
How do the emoji reactions work?
Once the Recruiter Slack Reaction Notifier agent is configured, recruiters react to referral posts with custom emoji: one for strong fit, one for need more info, and one for not a strong fit. Each reaction triggers an automatic DM to the referrer with the appropriate response.
How often are referral digests sent?
By default, the batching agent runs on a weekly schedule (Tuesday through Friday). You can adjust the schedule trigger to run daily or on different days to match your team's workflow.
What happens if someone refers a candidate who has already been referred?
The system checks for duplicates. If the candidate already has a referral credit in your ATS, it creates a note on their profile acknowledging the new referral while keeping the original credit intact. The tracker records both submissions so nothing is lost.
Do I need to set up custom Slack emoji for this to work?
Yes, you will need to create three custom emoji in your Slack workspace for the reaction-based follow-ups. The agent instructions reference specific emoji names, which you can customize to fit your team's naming conventions.
What is the difference between the three referral entry points?
Slack form submissions capture structured referral data through a Slack workflow form. Message pushes let someone push an informal Slack message into the referral pipeline using AI to extract the details. Direct ATS referrals catch referrals submitted directly in your applicant tracking system via webhook.
Can I customize the messages sent to referrers?
Yes. The response messages are defined in the Recruiter Slack Reaction Notifier agent instructions. You can edit the tone, content, and structure of each follow-up message to match your company voice and referral policies.
How does the AI role-matching work?
When a referral comes in, a Code step pulls all open roles from your ATS. An AI step then compares the referral details against the list of open positions and returns the most likely match using the exact job title from your ATS.