Turn eighty badge scans into a Teamtailor pipeline

Eighty scans, nine conversations, one pass

The companion takes the list one row at a time: look each person up by email, merge where they exist, create where they do not, with the fields you captured and none it invented. Then it creates the application against the role you named.

The note pays for itself six weeks later: where you met them, what they said about their current team, the thing that made you take the badge. Notes attach to the candidate or the job, so the context is there in October.

Who moved through the pipeline today?

Teamtailor sorts applications by most recent stage change, which makes the standup artefact nearly free. A companion pulls everyone who moved since yesterday, which stage they landed in and which job, adds a line of context from each candidate record, and posts it where your team already reads.

Read the other way round, the same list is a stall report: applications whose last movement was fourteen days ago. Pipelines are configured per job, so the companion resolves the stages for that job before it reasons about them.

How do I fix a record without blanking the rest?

A companion patches only the fields you asked it to change.

Phone number from two devices ago, a title that changed, a tag that meant something to a recruiter who left: name those three and only those three move.

If an email edit would collide with another candidate, the write fails loudly instead of merging two people into one. Worth knowing before you run it across a hundred rows. That is data extraction discipline: read the messy source, normalise it, show the diff, then write.

Stage moves the candidate hears about

Depending on your configuration, moving someone in Teamtailor can trigger a message that lands in their inbox with your employer brand on it. So moves arrive as a proposal with the evidence beside each name, and a person approves them, which is also faster than clicking through fourteen profiles.

A companion assembles, looks up, cross-references and drafts. A person decides who advances and who hears what. Candidate messaging stays on Teamtailor’s own triggers, where your templates live. The recruiting workflows show where the handoffs sit.

Frequently asked questions