Does Breezy HR Remember Between Runs? The Combined Profile Aggregates. The Run Reasoning Does Not.
Does Breezy HR Remember Between Runs? The Combined Profile Aggregates. The Run Reasoning Does Not. Short answer: Breezy HR keeps a candidate profile for every person, and that profile holds a great deal. Contact details, the resume, experience and education, message history, interview schedules, scorecards, and hiring team feedback all survive between runs. Breezy HR can also combine profiles that share the same email address, so a person who applied to more than one position can be viewed acro
Does Breezy HR Remember Between Runs? The Combined Profile Aggregates. The Run Reasoning Does Not.
Short answer: Breezy HR keeps a candidate profile for every person, and that profile holds a great deal. Contact details, the resume, experience and education, message history, interview schedules, scorecards, and hiring team feedback all survive between runs. Breezy HR can also combine profiles that share the same email address, so a person who applied to more than one position can be viewed across those positions in one place. What does not survive in the same way is the work a scheduled run does across many profiles at once. The comparisons, the grouping, and the order set for the next review are not stored as a history the next run can load.
What one candidate profile keeps in Breezy HR
Every candidate in Breezy HR has a profile, created when the candidate applies to a position or is added by a team member or an external recruiter. Every candidate is also associated with a position or a candidate pool, so the profile always sits inside a hiring context.
The profile is built from three sections. Candidate Details sits on the right and holds basic information: contact information, social media links, how the candidate was sourced or added, and the preferred salary range. Hiring Managers can edit those fields directly, move the candidate to a new stage, and add tags.
Candidate Experience sits on the left. That section stores the resume, plus details about experience, education, and qualifications. Hiring Team Actions sits in the middle. Team members add feedback there, schedule and follow up on interviews, and communicate with the candidate or with each other. That section updates as the team responds to messages, scorecards, and tasks. That is durable, person-level memory: who the candidate is, how the candidate was found, and what the team recorded.
What the pipeline, the pools, and combined data keep
Each position in Breezy HR has a pipeline, a series of stages each candidate moves through. The pipeline gives a visual snapshot of the candidates for that position, and Admins and Hiring Managers can move candidates along it. Stage actions add automation on top: an action fires the first time a candidate enters a stage, and it can send a message or a questionnaire when a candidate applies, or ask the hiring team for feedback after an interview.
Candidate Pools hold people when there is no role for them at the moment. Pools are managed much like positions, can be set to Active, Draft, Closed, or Archived, and keep strong applicants tracked instead of letting them disappear when one position closes.
Combined candidate data goes one step further. Breezy HR can automatically identify multiple profiles that use the same email address and aggregate their history. When a candidate applies to more than one job, or a team member copies a candidate to another position or pool, the information associated with each position can be seen in one place. The Other Places dropdown in the Details section switches between the profiles for individual positions. Combining is enabled by default, and viewing shared data across positions requires access to those positions.
Merging is different. Up to three profiles for the same person can be merged into one profile for a single position, with one master record. Interview schedules, email and SMS history, and notes from all profiles are included, and the other profiles are removed. Following a candidate is lighter: followers get notified about communications, stage moves, and teammate notes.
All of that helps a team find and connect a candidate's own record. Notice the shape, though: every layer is organized around one person, one position, or one pool. None was built to hold conclusions that belong to a run across all of them.
What a scheduled run loses overnight
Consider a routine that runs each morning across open positions and pools. It sweeps new applications, checks candidates who appear in more than one pipeline, compares scorecards and questionnaires that point in different directions, checks pools for people who fit a newly opened role, and prepares a priority order for the day.
During that sweep, the run builds knowledge that exists in no single profile. It decides that a candidate who looks average in one position looks stronger once combined history from another position is read beside it. It notices several candidates stalling at the same stage for the same reason, and works out which pool members to check first for the new role, and why.
When the run ends, the profiles are still complete and the combined view still aggregates the same person's history. The cross-position comparison, the shared stall cause, and the pool priority order were never written to a shared history the next run can load. The next morning starts from the raw profiles again and rebuilds the same groups before any new work begins.
The cost is not lost candidate data. The data stayed in Breezy HR. The cost is repeated reasoning, paid in full on every run, for work that was already done well once.
Give the runs one shared memory
Vilix AI is built for that missing layer: one memory held outside any single candidate profile, position, or pool, which every run can load before it starts and update before it ends.
It is cloud-hosted, so there is zero infrastructure to run or maintain. No separate store has to be provisioned and keyed to candidate IDs by hand just so an automation can keep its own working notes between runs.
Every connected tool reaches the same memory over MCP. A morning screening run beside Breezy HR, an assistant drafting outreach, and a reporting step summarizing pipeline movement can all read and write the same Vilix AI memory. The same memory follows the work everywhere, across tools and devices, instead of ending at the edge of one position view.
Vilix AI stores full conversation history, not just facts extracted from it. For hiring work, that difference is practical. A stored fact can say two positions were compared for one candidate. The full history shows what the run compared, which record it trusted, and why a case was left open, so the next run can check the reasoning instead of repeating it.
With that layer, the morning changes. The first run saves its comparisons and open decisions to Vilix AI. The second run loads that work first, then spends its effort only on new applications and waiting cases. Breezy HR keeps the profile, pipeline, and pool. Vilix AI keeps what the runs learned across them.
Start free, keep control of the data
Vilix AI has a free plan forever, with no time limit forcing a choice. Paid plans start with a 7-day Pro trial with no credit card required, so a full hiring cycle can be tested before any payment.
Data stays under the team's control. Everything can be exported at any time, and everything can be deleted at any time.
Free forever, no credit card.