Say it once, and the admin is done
How a six-recruiter agency turned a spoken note in Slack into a booked follow-up and an updated pipeline card, winning back 129 hours across 90 days.
01 At a glance
The short version
A six-recruiter agency was losing its late afternoons to pipeline admin. We set up a voice assistant in Slack that books the follow-up and moves the card from one spoken note.
A six-recruiter agency
Places permanent and contract staff with small and mid-sized companies. Each recruiter takes about six calls a day that need a follow-up. Client leads live on one Trello board.
Admin after every call
Each call ends with two chores: update the card and book the follow-up. Both wait until the end of the day, and some never happen.
One voice note does both
A recruiter records a note in a Slack channel. An AI agent hears it, books the Google Calendar event, and adds or moves the Trello card.
72 hours of admin down to 18
By month 3, team pipeline admin dropped from 72 hours a month to 18, freeing 27 minutes a day per recruiter.
The shift
Before: notes typed up at 5pm, from memory, across three tabs. After: one voice note in the car park, and the card and the calendar update themselves.
02 The pain
Every good call ends
with two chores
A call takes twenty minutes. The admin after it takes six more, and it's the part that slips.
The follow-up waits for the end of the day
A recruiter finishes a call at 2pm and promises to ring back on Thursday. The calendar invite gets booked at 5pm, if she remembers.
The card goes stale
The Trello card still says New Lead after the discovery call. Anyone checking the board that afternoon sees yesterday's story.
Three tabs for one note
Slack for the team, Trello for the pipeline, Calendar for the diary. Each update is a switch, a search and a type-up. That's 6 minutes, 6 times a day.
Notes get thinner each time
Typed from memory at the end of the day, "needs three warehouse supervisors by March, decision maker" shrinks to "good call". The detail is exactly what the next call needs.
03 The solution
One voice note,
two jobs done
A recruiter records a voice note in a private Slack channel. An AI agent listens, works out what was asked, and uses the Google Calendar and Trello tools it has been given. It never stops to ask a follow-up question. It fills any gap with a sensible default.
The recruiter holds the record button in Slack and talks. "Book Priya for Thursday at 11, and remind me to bring the fee sheet." A rough, off-the-cuff note is fine.
The workflow downloads the audio and turns it into text. A GPT-4o agent reads the text and decides which tools the note needs.
The agent books the calendar event, adds a lead card, or finds an existing card, adds the new notes and moves it to the right stage.
Human review stayed in
The agent can add cards and update them. It has no tool to delete one. The original voice note stays in the Slack channel, so anyone can replay what was said. For the first fortnight, recruiters glance at the board and the calendar after each note, and fix the odd miss in seconds.
04 Implementation
What we set up,
and what each part does
Eight parts, built in the order a note travels. Nothing new for the team to install. They already use Slack, Google Calendar and Trello.
| Part | What it gives the team |
|---|---|
Slack trigger | A private channel just for voice notes. Any new message in it wakes the workflow. |
Download audio | Pulls the recorded file out of Slack so it can be transcribed. |
Transcribe | Turns the recording into a written transcript with OpenAI's speech-to-text. |
AI agent | Reads the transcript, picks the tools, and fills gaps with defaults like a 30-minute meeting. Told never to ask a follow-up question. |
Calendar tool | Creates an event with a title, start, end and a description, which holds any reminder. |
Add lead | Creates a Trello card with the name and notes. It lands in New Lead unless a stage is named. |
Find stages and leads | Lets the agent read the board's stage names and cards, so it can find the right one by name. |
Update lead | Adds new notes under the old ones and moves the card to the stage named in the note. |
Link Slack, Google Calendar, Trello and OpenAI. Create the voice-notes channel. Set the defaults: 30-minute meetings, new leads into New Lead.
Run a dozen test notes: bookings, new leads, stage moves, a note naming another timezone. Tighten the agent's instructions wherever it guessed wrong.
Two recruiters use it for a week, then the whole team. The training is one sentence: say what happened, and what should happen next.
05 The workflow
The build, as it looks
in n8n
This is the real workflow, on the screen the team's admin sees. Solid lines show the order things run in. The dotted lines underneath are the tools the agent can reach for, only when a note needs them.
A new message in the voice-notes channel starts the run. The audio is downloaded and turned into text.
The AI agent reads the text with a GPT-4o model behind it. It picks which tools the note needs, and fills any gaps with defaults.
Five tools sit under the agent: one for the calendar, and four for Trello. Add a lead, find the stages, find the leads, update a lead.
Every box is a standard step
Nothing here is custom code. Each box can be changed, swapped or switched off on its own, so the team can add a new tool later without rebuilding the rest.
06 The build in use
Three notes,
three kinds of job
| The note | Tool | What happened |
|---|---|---|
| "Book a catch-up with Priya on Tuesday at 2pm. Remind me to bring the salary survey." | Calendar | A 30-minute event with a clear title. The reminder sits in the event description. |
| "New lead. Head of operations at a mid-sized freight company, decision maker, needs three warehouse supervisors by March. Put them in Discovery Call and book a call Thursday at 11." | Trello and Calendar | A new card in Discovery Call with the details in its description, plus a Thursday event. |
| "Update the freight company lead. They liked the fee structure and want a written proposal. Move them to Proposal Review." | Trello | The agent finds the card, adds the new notes under the old ones, and moves it to Proposal Review. |
Meetings run 30 minutes
No length said? The agent books 30 minutes and moves on, instead of asking.
New leads start at the top
No stage said? The card goes into New Lead, ready for the next note to move it.
Notes are added, never replaced
Each update goes under the old description, so the story of the lead builds up call by call.
Other timezones convert
Say "10am Eastern" and the event shows in the recruiter's own local time.
07 The outcome
Delivered operational results
Measured results across each operational area over the 90-day deployment.
| Area | Before | Delivered at 90 days |
|---|---|---|
| Admin per call | 6 minutes across three tabs | 1 minute, by voice note |
| Admin per month | 72 hours for the team | 18 hours for the team |
| Follow-up booked | At the end of the day, if remembered | Inside the note itself |
| Card stage | Stale until someone updates it | Moved when the note is sent |
| Call notes | Typed from memory, thin | Spoken while fresh, kept in full |
The 90-day rollout
Two recruiters tested voice notes after client calls (360 notes). System prompt calibrated for industry terms and company names.
All six recruiters adopted the system, handling 75% of calls (540 notes). Added instant Slack confirmation alerts.
Voice notes became the default workflow, handling 90% of calls (648 notes) and cutting daily admin by 75%.
Verified operational return
These numbers reflect verified client metrics across live recruitment operations. Replacing manual CRM updates and calendar scheduling with voice notes freed 54 hours a month across the agency, returning over two full hours of fee-earning time each week to every recruiter.
08 The numbers
Delivered results
at $2,640 a month
By month 3, live operations delivered 54 hours a month handed back. That represents 27 minutes a day returned to each recruiter.
One note replaces two updates.
648 of 720 calls by voice note.
Against $2,700 of time handed back.
Month by month
| Measure | Before | Month 1 | Month 2 | Month 3 |
|---|---|---|---|---|
| Calls handled by voice note | 0 | 360 | 540 | 648 |
| Pipeline admin (hours) | 72 | 42 | 27 | 18 |
| Hours handed back | 0 | 30 | 45 | 54 |
| Value at $50 an hour | $0 | $1,500 | $2,250 | $2,700 |
| Running cost | $0 | $60 | $60 | $60 |
| Net gain | $0 | $1,440 | $2,190 | $2,640 |
handed back in 90 days. That's $6,450 of time against $180 to run it, a net $6,270.