How to use OpenAI dots for recruiting: build an AI assistant for daily hiring work

By Screened · Updated 13 October 2026

Your manager forwards you a link to OpenAI dots with a short message:

Could we use this for recruiting?

The obvious answer is yes. A dot can draft an email or summarise a CV. The more interesting answer is that it can become the place where a piece of recruiting work keeps moving—even after the first conversation ends.

Imagine opening ChatGPT in the morning and asking one question:

What changed across my vacancies, and what actually needs me today?

The answer could already know that one interview was cancelled, another candidate has replied, a manager changed a requirement and yesterday’s missing scorecard was finally submitted. It could prepare the reply, the interviewer handover and the follow-up list without making you rebuild the context each time.

That is the real promise of dots for recruiters. Not simply “AI writes faster.” A dot can help you create a small recruiting assistant around the way you already work—one that returns tomorrow with the same vacancies, sources and standards in mind.

You do not need to be technical or redesign recruiting. Start with one repeated frustration. Teach the dot what a useful answer looks like. Then expand from there.

This guide follows that journey: from a first morning action brief to candidate replies, clearer intake questions, CV evidence, interview handovers and recurring follow-up. Every workflow includes the situation, the prompt, an example output and ways to make the result more useful for your own work.

What is an OpenAI dot?

An OpenAI dot is an ongoing AI assistant inside ChatGPT. A normal chat helps with the request in front of you. A dot is designed for work that continues: it can retain context, use apps you connect and run scheduled tasks where those features are available.

For a recruiter, dots are most interesting when the work has continuity:

• checking what changed since yesterday;
• keeping email, calendar and ATS activity aligned;
• returning to the same vacancy with the same requirements;
• preparing the next interviewer from what has already been learned;
• producing the same useful brief every morning or every Friday.

A dot is not a replacement for your applicant tracking system, or ATS. The ATS should remain the official hiring record. Think of the dot as an assistant that reads the relevant material, joins the pieces together and prepares the next move for you to review.

OpenAI currently documents dots on desktop web and in the desktop app, with availability depending on plan, region and rollout. See OpenAI’s getting-started guide.

Start with the problem you already have: what still needs attention?

The safest way to understand a dot is to give it a small problem whose answer you already know.

Consider these fictional records.

Application A-214

• Tuesday ATS note: interview booked for Thursday at 10am.
• Wednesday candidate email: “Could we move Thursday’s interview? I am available Friday after 2pm Singapore time.”
• Wednesday calendar: Thursday interview cancelled; no replacement event.

Application A-215

• Tuesday candidate email: “Is the role based in the office?”
• Wednesday recruiter reply: “Yes, the team works from the office.”

You could paste this into a dot:

Prepare a recruiting action brief as of the end of Wednesday for job J-20.

Use only the records below.

Application A-214
- Tuesday ATS note: interview booked for Thursday at 10am.
- Wednesday candidate email: “Could we move Thursday’s interview? I am available Friday after 2pm Singapore time.”
- Wednesday calendar record: Thursday interview cancelled. No replacement event exists.

Application A-215
- Tuesday candidate email: “Is the role based in the office?”
- Wednesday recruiter reply: “Yes, the team works from the office.”

Show only work that is still open. For each item, include:
- application ID
- what needs attention
- latest evidence
- next action

Do not treat a suggested time as a confirmed booking. Do not send messages, book interviews or change records.

A useful output

Two absences matter as much as the row that appears.

A-215 is absent because the candidate’s question was answered. The dot has not blindly carried forward yesterday’s list.

Friday is not described as booked because the candidate only supplied availability. An option is not an appointment.

That is the first important lesson: the best action brief does not merely collect activity. It reconciles the latest evidence and removes work that is already complete.

Make the brief fit your morning

The same workflow can produce very different results depending on what you ask for.

For a seven-item executive view:

Return no more than seven items. Put any remaining open work under “More open work”. Order the main list by real deadlines and candidate-facing commitments, not candidate quality.

For a personal recruiter list:

Include only actions assigned to me or waiting for my response. Put work owned by other people under “Waiting on others”.

For a change-only brief:

Compare with yesterday’s checked brief. Show new items, changed items and overdue items. Do not repeat unchanged background.

For a handover before leave:

Group the open work by vacancy. For each item, show the current state, the next action, the owner and the exact source the covering recruiter should open.

Notice how the output changes. You are not “prompt engineering” in the abstract. You are choosing the view of the work that is useful to you.

From an open action to a better candidate reply

Once the dot identifies the open action, the next question is often: what should I say?

Suppose A-214’s interviewer is available Friday at 3pm Singapore time. The candidate has said they are available after 2pm, but has not agreed to 3pm.

A weak AI draft might say:

Great, your interview has been rescheduled for Friday at 3pm.

That sounds efficient, but it has invented confirmation.

A better prompt keeps the factual state visible:

Draft a reply to candidate A-214.

Latest candidate message:
“Could we move Thursday’s interview? I am available Friday after 2pm Singapore time.”

Current scheduling state:
- Thursday’s interview is cancelled.
- The interviewer is available Friday at 3pm Singapore time.
- The candidate has not yet agreed to 3pm.

Write a warm, direct email offering Friday at 3pm Singapore time and asking the candidate to confirm.

Do not describe the interview as booked. Do not create an event or update the ATS.

Example output

Subject: New interview time

Hi Jordan,

Thanks for letting me know. We can offer Friday at 3pm Singapore time for the interview. Does that work for you?

Once you confirm, I’ll send the updated invitation.

Best,

Maya

The value is not the wording alone. The message reflects the actual state of the process: one side has offered a time; the other has not confirmed it.

Change the output for a different situation

When you owe an update but have no decision:

Answer the candidate’s question directly.

Say that the team has not made a decision.

Do not promise a date unless one has been approved.

Ask whether the candidate has a deadline we should know about.

When the delay is yours:

Acknowledge that our update is late in the first two sentences. Do not hide the delay behind generic thanks for patience.

When the candidate asks about the interview format:

Use the approved interview plan. Explain the length, attendees and exercise in plain language. Do not add preparation advice that is not in the plan.

When you need a very short message:

Keep the email under 70 words. Put the answer in the first sentence.

The dot can help you write many messages. The more important skill is making sure the source facts—and the current state—are explicit before it writes.

Turn vague manager feedback into a decision you can recruit against

Recruiters often receive feedback such as:

“These people look okay, but I hoped for someone more senior.”

The phrase sounds clear until you try to search with it. Does “senior” mean larger accounts, harder negotiations, team leadership, independent decisions or simply more years of experience?

A dot can keep the current role brief and help turn vague comments into questions the manager can actually answer.

Imagine the approved brief says the new account manager must:

• lead renewal discussions;
• identify customer problems early enough to involve the right internal team;
• work within agreed pricing limits and request approval for exceptions;
• learn the company’s product after joining.

The manager then says:

“I think we need somebody more strategic, ideally from a bigger company.”

Prompt

Help me prepare questions for the hiring manager about this account-manager role.

Current approved brief
- Lead customer-renewal discussions.
- Identify customer problems early enough to involve the right internal team.
- Work within agreed pricing limits and request approval for exceptions.
- Our product can be taught after joining.

New manager comment
“I think we need somebody more strategic, ideally from a bigger company.”

Find the important decisions hidden inside the new comment. For each one:
- explain what is unclear
- ask one plain-English question about the work
- explain how the answer would change sourcing or assessment

Do not add a new requirement. Keep the approved brief unchanged until the manager decides.

Example output

This output is useful because it does not merely rewrite the job description. It reveals the decisions underneath the manager’s language.

Use the same method for other vague requirements

For “culture fit”:

Do not use “culture fit” as an answer. Ask which observable working behaviour matters in this role, and in what situation it matters.

For “strong communication”:

Separate the communication tasks the role actually requires—such as explaining a technical issue to a customer, writing a clear handover or leading a difficult meeting—from confidence, accent or presentation style.

For “more commercial”:

Ask which commercial decision the person must make, what information they use and where their authority stops.

For a requirement that may be changing mid-search:

Show which open applications and interview questions could be affected if the manager approves the change. Do not rescore anyone yet.

This is where an ongoing dot can be more useful than a one-off chat: it can compare the manager’s new comment with the current approved brief instead of treating the latest sentence as the whole truth.

Read a CV without upgrading the evidence

One of the easiest mistakes in recruiting is turning a vague CV phrase into a stronger claim.

“Supported contract renewals” becomes “led renewal negotiations.”

“Worked with the implementation team” becomes “owned implementation.”

“Helped launch new stores” becomes “led a multi-site rollout.”

The summary sounds clearer, but it no longer says the same thing as the source.

A useful dot workflow does not merely shorten the CV. It preserves responsibility and shows what is still unknown.

Example source

Current requirements

1. Lead customer-renewal discussions.
2. Identify risks early and involve the right internal team.
3. Work within agreed commercial limits and seek approval when needed.

CV passage

“Supported the account team on annual renewals for enterprise customers. Prepared usage reports, coordinated product specialists and sent follow-up materials after customer meetings.”

Prompt

Review application A-331 against the current account-manager requirements.

Current requirements
1. Lead customer-renewal discussions.
2. Identify risks early and involve the right internal team.
3. Work within agreed commercial limits and seek approval when needed.

CV passage
“Supported the account team on annual renewals for enterprise customers.

Prepared usage reports, coordinated product specialists and sent follow-up materials after customer meetings.”

For each requirement, show:
- the exact supporting passage
- what the applicant says they personally did
- what the passage does not establish
- one neutral follow-up question when useful

Keep “not mentioned” separate from “explicitly not done”. Do not give a match score or hiring recommendation.

Example output

Suggested follow-up:

“During those renewals, what part of the customer conversation did you personally lead?”

The output gives you a better next question without quietly converting related experience into confirmed experience.

What happens when the source changes?

Change the CV sentence to:

“Led annual renewal meetings for enterprise customers and negotiated terms within approved discount limits.”

Now the summary should change. The wording supports leadership and defined commercial authority.

Change it to:

“I did not negotiate renewals; I prepared reports for the account manager.”

Now the evidence is not merely missing. The applicant has explicitly said this example did not involve the required responsibility.

These three states are different:

• described: the evidence supports the responsibility;
• unclear: the source is related but does not establish responsibility;
• explicitly absent: the applicant says they did not perform it.

A useful dot should preserve that distinction.

Turn the CV review into the next interviewer’s brief

A recruiter’s work becomes much more valuable when the next interviewer can see what has already been learned and what still needs testing.

A weak handover says:

Promising enterprise account manager. Strong communicator. Please explore renewals.

A useful handover is more specific.

Prompt

Prepare a brief for the next interviewer for application A-331.

Role requirements
- lead renewal discussions
- identify account risk early
- involve the right specialist
- work within commercial authority

Checked evidence
- The CV says the applicant supported annual renewals, prepared usage reports and coordinated product specialists.
- The screening call established that the applicant presented the usage findings to customers.
- We have not established whether they negotiated terms or decided when to involve product specialists.

This interview is responsible for assessing renewal leadership and judgement about escalation.

Write a brief under 250 words with:
- why the applicant is worth exploring
- what is already established
- what remains unclear
- three questions worth asking next

Do not make a hiring recommendation.

Example output

Why explore further

The applicant has direct enterprise-renewal exposure and described presenting customer usage findings. That is relevant to identifying risk and supporting a renewal plan.

Already established

• Prepared usage evidence for renewal discussions.
• Presented findings to customers.
• Coordinated product specialists during renewal work.

Still unclear

• Whether they led the renewal conversation or supported an account manager.
• Whether they negotiated terms.
• How they decided that a product specialist was needed.

Questions

1. “Tell me about a renewal conversation you personally led. What made it difficult?”
2. “What could you agree with the customer yourself, and what needed approval?”
3. “Describe a time you decided to involve a product specialist. What did you notice?”

The interviewer receives a starting point, not a conclusion. They do not need to reread the whole CV to understand why each question matters.

Adapt the handover for a busy manager

Keep each application to 120 words. Use three labels only: Why meet, Still unclear, Ask next.

Adapt it for a panel interviewer

Include only the requirements assigned to this interviewer. Remove questions already answered in earlier stages.

Adapt it when evidence conflicts

Put conflicting evidence in a separate section. Quote both sources and do not resolve the conflict without asking.

The transition matters: the CV review should not end as a private summary in the recruiter’s notes. It should improve the next conversation.

Use the dot to reconcile scheduling, not merely find free time

Interview scheduling looks like a calendar problem. Often it is a state problem.

The candidate suggests Friday. The recruiter holds a slot. The interviewer later becomes unavailable. The ATS still shows the original appointment. Someone sends a reminder using the old time.

A useful scheduling workflow starts by asking what is actually confirmed.

Prompt

Review the scheduling state for application A-214.

Candidate’s latest message
“I am available Friday after 2pm Singapore time.”

Current calendar information
- Original Thursday event is cancelled.
- Interviewer Lee is available Friday from 3pm to 5pm.
- Interviewer Priya is available Friday from 2pm to 4pm.
- No replacement invitation exists.

Interview requirements
- 45 minutes
- both interviewers required
- 15-minute buffer after the interview
- candidate timezone: Singapore

State whether the interview is proposed, confirmed, cancelled or waiting for a replacement.

Then give up to three possible times. Show why each time works. Do not create an event or describe an option as confirmed.

Example output

Current state: Waiting for a replacement. The original Thursday interview is cancelled. The candidate has provided Friday availability, but no new time has been agreed.

There is only one valid option. The assistant should not manufacture three choices merely because the prompt says “up to three.”

Change the result for a candidate-facing message

Draft an email offering the valid option. Say it is an option and ask the candidate to confirm. Do not create the invitation.

Change it for an internal coordinator

Show the current event, cancellation evidence, candidate availability, interviewer overlap and the exact action required before the ATS should be updated.

The benefit is not just faster calendar comparison. It is avoiding false confidence about what has already happened.

Prepare a clear ATS note without writing to the wrong record

One candidate may have several applications. A note about a sales role can become misleading when it is attached to a shared candidate profile and later read during a support-role process.

Before writing, ask the dot to show the destination.

Prompt

Prepare an ATS note from the checked screening material below.

Candidate ID
C-118

Application ID
A-331

Job ID
J-20 — Senior Account Manager

Source
Screening call on 12 October 2026.

Checked facts
- Applicant prepared usage reports for enterprise renewals.
- Applicant presented those findings to customers.
- Applicant said the account manager led commercial negotiation.
- We have not established whether the applicant has led renewal negotiations in another role.

Show:
- the supported note destination available through the connected tool
- the proposed note
- any similar existing note
- anything that needs clarification before writing

Do not write the note, add a score or change the stage.

Example note

J-20 Senior Account Manager — screening call, 12 October 2026

The applicant described preparing and presenting usage evidence during enterprise renewals. They said the account manager led the commercial negotiation. Experience personally leading renewal negotiations is not yet established; ask about other roles or examples at the next stage.

The note is useful because it carries the job context with it and distinguishes what was said from what still needs checking.

Only after reviewing the destination and wording should you consider an approved write. If the tool can only write a candidate-level note, include the job and application ID in the text.

Find stalled applications without treating delay as a candidate problem

A recruiter sees that an application has been in “Interview” for 12 days. That may mean the candidate is waiting, the team is waiting for a scorecard, the vacancy is paused or the ATS stage was never updated.

Time in stage tells you where to look. It does not tell you whom to blame.

Prompt

Review active applications for jobs J-20 and J-21 as of 13 October 2026.

Flag applications that have been in their current stage for more than seven calendar days.

For each one, show:
- application ID
- current stage
- date the application entered the stage
- days in stage
- latest relevant activity
- next owner if recorded
- what needs checking

Exclude withdrawn and closed applications. Separate paused vacancies. Do not use “last updated” as a substitute for stage-entry date.

Example output

The third row is important. A missing date must not become “zero days” or an invented estimate.

Adapt the report for a weekly review

Group the applications by the decision or dependency holding them up: manager review, interview scheduling, missing feedback, candidate response or data problem.

Adapt it for candidate experience

Highlight cases where the candidate was promised an update or has asked a question that remains unanswered.

This turns a generic ageing report into a practical list of process problems.

Close the loop: what actually got finished?

At the end of the day, a generated draft can look deceptively like completed work.

A reply was drafted but not sent. A time was proposed but not booked. A note was prepared but not saved. If the next morning’s brief treats those actions as complete, the workflow becomes less reliable over time.

Prompt

Compare this morning’s checked action brief with the current records.

For each action, classify it as:
- completed, with evidence
- still open
- superseded
- blocked
- completion uncertain

A drafted email is not a sent email.
A proposed time is not a booked interview.
A prepared note is not a saved ATS note.

For completed actions, show the record that confirms completion.

For uncertain actions, say what should be checked before anyone retries the action.

Example output

This is where a dot starts to feel like an ongoing assistant rather than a text generator: it helps keep the difference between intended, drafted and completed work visible.

When should you connect live systems?

You can learn the workflows above with fictional records or a dated export. A live connection becomes useful when the job depends on current information.

A morning action brief may need:

• the ATS for application stage and feedback;
• email for candidate questions and replies;
• calendar for interview state and availability.

Connect one source at a time and test a record you already know. The practical question is not “Is the app connected?” It is:

Can the dot retrieve the exact evidence this workflow needs, and can I verify it?

Reading an application does not prove the tool can read every scorecard. Reading a calendar does not mean an invitation was sent. A failed source should appear as a limitation, not as an empty result.

OpenAI explains dots’ connection and data controls in its privacy, security and safety FAQ.

Turn a checked workflow into a recurring brief

Do not schedule the first version of a task. First run it manually, notice what it gets wrong and correct the method.

Once the morning brief reliably distinguishes open, completed and inaccessible work, you can ask the dot to repeat it.

Create a recurring version of the checked recruiting action brief for jobs J-20 and J-21.

Run it Monday to Friday at 8:30am Singapore time.

Use the same sources, definitions and output format as the brief we checked.

Show:
- new actions
- changed actions
- overdue actions
- unresolved candidate commitments

Do not repeat unchanged background.

If a source is unavailable, label the brief incomplete and name the missing source. Do not send messages, book events or change ATS records.

Before saving the schedule, show me the full task, schedule and destination for review.

A useful recurring task should give you a shorter path into the work—not create a new report you must decode each morning.

Pause it when the vacancies close. Change it when the process changes. Review the first few runs against the source records.

What an excellent first dots workflow looks like

The strongest starting workflow is not “automate recruiting.” It is:

1. choose one vacancy;
2. ask for a read-only action brief;
3. compare every item with the source;
4. correct the method when it carries stale work forward;
5. add live sources only when the brief needs them;
6. schedule the task only after the output is reliably useful.

The point is not to build a perfect recruiting dot on day one. It is to create one small workflow that makes you noticeably better at the work already on your desk.

Start with the morning action brief. When it reliably shows what changed and removes work that is already complete, let the same dot help with the next move: the candidate reply, the question for the hiring manager, the interviewer handover or the end-of-day reconciliation.

Over time, the valuable skill is not “prompt engineering.” It is learning how to turn your recruiting judgement into a clear, repeatable method. The dot brings continuity; you decide what good recruiting looks like.

A successful workflow should leave you feeling more on top of the process—not because the AI has taken over, but because fewer important details have to live in your head.

For the next step after a useful action brief, see The Shortlist Problem: why good CVs aren’t enough.