How to use one-shot & few-shot prompting in recruiting [Part 2]

Once you have a good grip on prompting in CoRecruit, the next step is teaching the AI to mirror how you actually write. This includes your tone, formatting, and how polished your writing is.

That’s where example-based prompting comes in. Instead of just asking CoRecruit to summarize a call, you show it exactly what a great output looks like. This example can be anything (a client summary, candidate submittal, etc.)

In this guide, we’ll break down how to use One-Shot and Few-Shot prompting to help CoRecruit learn from your examples.

You’ll learn when to use each method, how to structure your examples, and a few copy-paste prompt templates to get you started.

Using AI prompts to generate follow-up recruiting materials

Once your Notes are solid, the next step is generating longer-form documents. These documents can include candidate submissions, client summaries, or post-interview write-ups.

In CoRecruit , you create these inside the Follow Up Material section. Here, you provide CoRecruit with a single, well-structured example, and it automatically mirrors your tone, formatting, and style.

To train CoRecruit for these kinds of outputs, you can use One-Shot or Few-Shot prompting.

What is one shot prompting?

You provide one complete example of the desired output (like a candidate submission). CoRecruit studies that example and reproduces the same tone and layout using the new participant’s data.

Example:

[Based on this conversation, create a similar note structure using the participant’s information. Use this example for your response:

(Paste example submission here)]

This bracketed structure tells CoRecruit : “Use this format, tone, and level of detail as a template.”

What is few shot prompting?

You give multiple examples to teach CoRecruit how your writing style might vary across different roles or clients. This works best for recruiters who write different types of submissions. For instance, technical roles vs. sales roles.

[Based on this conversation, create a candidate submission using the participant’s info. Refer to these examples to guide your response:

1. (Paste tech role submission example)

2. (Paste sales role submission example)

3. (Paste finance role submission example)]

Formatting Rule: Use Square Brackets [ ]

Always enclose your instructions inside square brackets.

This signals to CoRecruit that the text inside the brackets are system-level instructions, not part of the submission content itself.

Example:

[Use the following format to create a client-ready candidate submission summary based on the participant’s information:

(Insert sample text or template here)]

If you skip brackets, CoRecruit may treat your instructions as part of the content, which can lead to formatting or structural errors.

Customize your AI prompts for specific roles

Follow-up prompts work best when tailored to the type of role or industry.

A healthcare submission sounds very different from a sales or finance one. CoRecruit learns those nuances quickly when you provide examples specific to each.

‍

For instance:

[Use this as an example for healthcare roles:

(Paste healthcare-specific submission example here)]

[Use this as an example for tech roles:

(Paste tech submission example here)]

This helps ensure every output reads as if written by a recruiter who understands that particular field.

‍

4. Adding job descriptions

Include the job description directly in your prompt to help CoRecruit align submissions with the role’s actual requirements.

Wrap it inside triple quotes (“””) so CoRecruit recognizes it as a reference document.

Example:

[Based on this conversation, use this job description as a reference:

"""

(Paste JD here)

"""]

When you do this, CoRecruit cross-references what the participant said with the job description.

‍

Setting up and managing your CoRecruit workflow

Once your prompts are ready, you can set up your workflow in CoRecruit. Start by defining how meetings are structured, how notes are captured, and how outputs flow into your ATS.

Workflows in CoRecruit revolve around Meeting Types, which act as templates for every recruiting conversation you run. They ensure your notes and submissions stay consistent and organized across different roles and clients.

‍

What are "Meeting Types"?

Each Meeting Type in CoRecruit includes three core components:

• Script: A private call guide or memo for you, the host. The AI doesn’t use it; it serves as a reference for how you plan the meeting.
• Notes: The AI-driven section that answers your questions and sends formatted notes directly to your ATS.
• Follow-Up Material: The long-form document generator that creates your candidate submissions or post-call summaries.

‍

Creating custom meeting types: Best practices & options

Create new meeting types from ones you already have

Instead of starting from scratch, it's usually easiest to duplicate an existing Meeting Type. Then adjust the Notes and Follow-Up Material to fit the new role. This preserves your formatting and prompt style while updating only role-specific details, like required skills or tone.

Though, quick note: if you want to start from a PDF job description, you'll have to create a new meeting type.

Generate a meeting type from a job description

One easy way to customize a meeting type is to upload a PDF job description directly. CoRecruit reads the document, extracts relevant questions, and automatically drafts a Script and Notes section for you. From there, you just add the Follow Up Materials you want.

Tell CoRecruit where to send your notes

Under Meeting Type details, you’ll find a field labeled Activity Type. This tags your notes when they sync to your ATS, for example as “Candidate Notes,” “Interview Summary,” or “Client Intake.”

Customizing this ensures your team’s outputs stay organized and searchable within your ATS.

Tailoring CoRecruit's responses to match your needs

Even the best-written prompts can’t anticipate every nuance of a recruiting conversation, and that’s okay.

Think of CoRecruit's CoRecruit AI outputs as drafts

As with all AI tools, it's best not to take their responses verbatim. Every output CoRecruit generates is based on your prompt instructions. If a note feels off — missing details, too soft, or full of filler — take it as an example to refine the prompt. You don't have to rewrite the entire note, but you should add your own unique insights or flavor to the note.

Small adjustments yield massive improvements in the next call.

Re-prompt if you're not happy with the first output

If you notice missing context or structure, you can re-generate your meeting type with a new prompt. Usually, this would include adding additional context or making sure you clearly specify speaker roles, for example. CoRecruit will regenerate the output using your original prompt, often correcting smaller issues like formatting or phrasing instantly.

What to do if CoRecruit confuses who’s who in a meeting

Occasionally, the AI might attribute the host’s comments to the participant. When that happens, revisit your prompt and make sure it clearly defines:

• “Host” = you (the recruiter)
• “Participant” = the person you’re interviewing

Making CoRecruit write like it’s been on your team for years

One-shot and few-shot prompting help you fine-tune your recruiting process and make it more effective. By giving the AI real examples of your tone, structure, and polish, you show CoRecruit how you write.

Over time, these examples compound. Submissions start sounding like they came straight from your desk. Think of setting up your meeting types as "teaching moments" -- each example you add helps CoRecruit learn to speak your recruiting language fluently.

‍