Hospitality hiring happens at the worst possible time. You need somebody because you are already short, applications arrive in three different places, and the good candidates are gone within a week because another venue replied first.
The slow part is almost never the interview. It is the four days between an application landing and anybody reading it, and then the run of messages it takes to agree a time.
This guide builds a screening and scheduling setup for a cafe, restaurant or small hospitality business. Every applicant gets a reply the same day, the ones who can work the shifts you need get a booking link, and you spend your time interviewing rather than arranging interviews. Setup takes about two hours.
What you are building
One front door for applications, a structured summary of every applicant against criteria you wrote down in advance, an automatic invitation to book a trial or an interview for the ones who meet them, and a short respectful reply for the ones who do not. A person makes every hiring decision. The automation removes the waiting around it.
Tools: one application form, a spreadsheet, a scheduling tool with your real availability in it, an automation tool such as Zapier, Make or n8n, an AI assistant such as ChatGPT or Claude, and your email or SMS.
Step 1: write down what the job actually requires
Before anything is automated, put the requirements in two lists. The first is what somebody must have to do the job at all: the right to work, availability on the shifts you actually need covering, and a way of getting to the venue at the times you open and close. The second is what you would like: experience on a machine, a certificate, a language your customers speak.
Be honest that the first list is the whole screen. Everything on the second list is a conversation, not a filter.
Keep both lists in the same note as the prompts, and rewrite them for each role rather than reusing the ones from the last hire. The shifts you were short on in February are not the shifts you are short on now, and a stale requirement list quietly filters out the people you currently need.
Step 2: one application form, asking the right things
Applications arriving by email, by message, through a job board and on paper cannot be processed the same way. Put one link everywhere: in the window, on the job board, in the bio, and in the auto-reply on the address people email about jobs.
- Name and contact, and which of the two is the better way to reach them.
- Which shifts they can work, as tick boxes for the shifts you actually run rather than a free-text box about availability.
- When they could start.
- Whether they have the right to work where you are, confirmed as a yes or no.
- Two or three sentences on relevant experience, with an example of a busy service they have worked.
- Anything the role genuinely requires, such as a certificate. Keep this section short.
The shift tick boxes are the single most useful field on the form. They turn the most common reason an application goes nowhere into something a rule can check in a second.
Step 3: the summary prompt
What you want from the assistant is a consistent one-screen summary of each applicant against your own list, not a judgement about the person.
Here is one application for a role at a [cafe or restaurant, one line]. The shifts we need covered are [list them]. The requirements are [list the must-haves]. Produce a short structured summary with these fields and nothing else: name; best contact method; which shifts they can cover and whether that matches what we need, answered yes, partly or no; earliest start date; right to work confirmed, yes or no; relevant experience in two lines using their own wording; up to three things they said that are worth asking about at interview. Rules: report only what the application says. Where a field is blank write NOT ANSWERED. Do not score the candidate, do not rank them, do not recommend hiring or rejecting, and do not comment on anything beyond the fields listed.
Every summary comes out in the same shape, which is what makes reading twenty of them possible in ten minutes. The ban on scoring is not squeamishness. It keeps the decision, and the responsibility for it, with you.
Step 4: wire the replies and the booking
- Trigger on a new form response and append it to a sheet, so you always have the raw record.
- Send an acknowledgement within a minute saying the application arrived and when they will hear back. Name the day.
- Call the assistant with the summary prompt and write the summary into the sheet next to the application.
- Apply your own rule, not the model. If the shift match is no, or right to work is not confirmed, flag the row for a person to look at.
- Email yourself one digest a day with the summaries in it, each with two buttons: invite or decline.
- Invite sends the scheduling link for your trial or interview slots. Decline sends the short message you wrote in advance.
Put your genuine availability into the scheduling tool and let the candidate pick. The back and forth about times is most of the delay in hospitality hiring, and it is entirely avoidable.
Send the invitation by whichever channel they said they prefer. In this trade that is usually a text, and an email sitting unread for three days is how you lose somebody to the place down the road.
Keep the digest to one email at a fixed time rather than a notification per application. Reading them one at a time between services is how a good application ends up half read and never actioned.
Step 5: write the two messages you will send most
Write two short messages for a [cafe or restaurant] hiring for [role]. One: an invitation to book a trial shift or interview. Warm and plain, saying what will happen, how long it takes, what to wear and which door to come to, with one booking link. Two: a decline, under sixty words, respectful and final, thanking them for applying and saying we are not taking it further this time, with no false encouragement and no reason beyond that we had other applicants closer to what we need right now. Use the placeholders APPLICANT_NAME, ROLE, VENUE and BOOKING_LINK. No exclamation marks, no emoji. Give me an SMS version and an email version of each.
Send the decline. It is the message everybody skips, and in a trade where people move between venues and talk to each other constantly, being the place that always replies is worth more than it costs.
What changes
Applicants hear from you on the day they apply instead of the week after. The people who can cover the shifts you are short on get a booking link while they are still interested. And the pile of applications becomes twenty identical summaries you can read with a coffee rather than twenty different documents in four formats.
Hiring admin is one of the recurring jobs in Workflow 07: Run a Leaner Business, the AutomateFirst module about the operating rhythm and the small systems that keep a venue running without the owner standing in the middle of every step. This guide is one complete build from it, free. The playbook has seven workflows for one payment of $297, with a 30 day refund.
Workflow 07: Run a Leaner Business
Six more workflows, written exactly like this one
The AutomateFirst playbook covers seven repetitive jobs end to end, with the prompt library, PDF checklists and lifetime access. One payment of $297, no subscription.
Other guides
