Recruiting commission-only sales reps is a volume game with a terrible hit rate. Lots of people apply. Far fewer answer a text, fewer still show up for a field interview, and a handful will actually knock doors. For years I ran it the way most owners do: ads, a spreadsheet, and a lot of phone calls to people who were never going to work out.
Version one: the no-code chain
The first automation was a chain: Meta recruiting ads fed a Make.com scenario that texted each applicant through Twilio, logged them in a sheet, and sent a Calendly link. It was a real improvement — applicants heard back in seconds instead of days.
It also had limits we didn’t see until later. It couldn’t hold a conversation. It didn’t know what an applicant had already answered. And when we finally audited delivery receipts, we found a large batch of messages it had logged as sent that were never delivered.
Version two: one app, one record
We rebuilt it as a single web app with its own database. The important design choices:
- Two intake paths. Meta’s webhook for speed, plus a poller every five minutes, because webhooks occasionally fail and a missed applicant is invisible.
- Ask only what’s missing. The assistant reads the application first, then asks only for the requirements it didn’t cover.
- Evidence, not scores. Five requirements, each rated Confirmed, Needs discussion or Unknown, with the applicant’s words saved.
- Booking integrity. Two interview slots are offered, and the database locks a slot the moment someone takes it.
- Owner-only hiring. The AI can’t mark anyone hired. Trainers record feedback; the owner approves.
- Ramp after the hire. New reps get a daily check-in, pace against a goal, milestone tiers, and their manager gets a Monday digest.
What happened when real applicants arrived
We imported real applications that had been sitting in the old process and reviewed every conversation. That review changed the system:
- Answer once per burst. People send three short texts in a row. Replying to each one made the assistant feel robotic.
- “ok” is an answer. The first version re-asked questions when replies were short.
- Inbound texts were being dropped. A messaging-service setting was silently discarding replies. We only found it by comparing what applicants said they sent with what we received.
- A bounce isn’t a contact. Bounced outreach had been counted as “contacted”, which made the funnel look better than it was.
The gates nobody tells you about
The software was the fast part. Two approvals were not:
- Meta app review for messaging permissions. Until it clears, the app can’t message applicants through Messenger, and form-only applicants can’t be messaged there at all.
- Carrier SMS registration (A2P 10DLC). US business texting requires it, and approval can take weeks.
If you’re building something similar, start both on day one.
What I’d tell another owner
Automate the first reply and the screening questions. Keep the interview and the hire decision human. And audit delivery — not sends — before you trust any number your funnel tells you.
