Back to Blog Home

How to Handle New-Hire Emergency Contacts with an AI Company Brain

Hands holding a tablet displaying a help screen with question and support icons

Do not let the company brain collect emergency contacts. It should explain the task, hand the employee to the HR form, and learn one thing back: whether the HR system accepted the record. We recommend this boundary for two reasons. The contact is a third party who never agreed to appear in chat transcripts, search indexes or analytics, and a checklist that turns green when the form was submitted, not accepted, can leave a new hire with no working contact on the one day it matters.

What the assistant may know

Split the data into two lists before you automate anything. Private form data is the contact's name, relationship, phone numbers and whatever else HR and privacy owners approve for the form. It lives only in the HR system, never in a task description, prompt, vector index, analytics event or ticket title. Safe orchestration data is deliberately boring:

  • a stable employee identifier;
  • the form type and version, and the destination system;
  • a state such as not-started, submitted, accepted, correction-needed or unavailable;
  • a reason code that contains no contact details;
  • the owner queue and the time of the last authoritative check.

A status object looks like this:

employee_id: emp-2047
workflow: emergency-contact
form_version: 2026-08-us
system_of_record: hris-primary
state: correction-needed
reason_code: missing-primary-phone
owner_queue: people-operations
checked_at: 2026-08-27T09:15:00Z
private_fields_present: false

private_fields_present must always be false in the company-brain status service. If a connector starts returning names or phone numbers after an API change, fail closed and alert the owner instead of passing the response to the assistant.

NIST calls its Privacy Framework a voluntary tool for managing privacy risk while protecting individuals' privacy, and it publishes a Quick Start Guide of basic questions for getting going. It creates no duty for you here, but its framing fits this form: the individual whose privacy is at stake is the contact, who is not your employee and never opens your assistant. In practice that means a stated purpose for every field, a short list of places the value may travel, and explicit correction and deletion paths.

Kipwise's employee onboarding solution provides product context for assigned reading, searchable company information, and onboarding progress. Use those capabilities for guidance and task visibility. Keep the emergency-contact values and their authoritative acceptance state behind the HR-owned boundary.

Leave free text and medical details off the form

Search results for this form, such as Indeed's guide to employee emergency contact forms and Jotform's template for new employees, agree on the core: the contact's name, phone and relationship, plus a backup contact. They also add optional extras. Indeed suggests a voluntary medical section for allergies and conditions, and the Jotform template has a special-instructions field.

We recommend dropping both from the onboarding form. A free-text field invites health details that nobody planned to store, and they then sit next to a phone number that every status check, export and support agent can reach. If the company wants allergies or conditions available to first responders, collect them in a separate voluntary record with a smaller access list, and keep that record out of the assistant's reach as well.

Collect it on the first working day

Keep the form out of the pre-start packet. We recommend assigning the task on the first working day. Until then nothing needs the contact: nobody is working for you yet, so no emergency can happen at work. An offer that falls through, or a start date that moves, leaves a stranger's phone number in your HR system for no purpose. The cost is one more task on day one. If your process collects it earlier, treat a withdrawn start as a deletion trigger and suspend the reminders.

Create the task from an authoritative joiner event, not from a forwarded email or a name typed into a spreadsheet, because duplicate identities produce duplicate forms and conflicting status. Microsoft's lifecycle workflows show the shape to copy: a workflow is a task, a scope of who is affected, and a trigger of when, driven by attributes such as the hire date. Even if the emergency-contact record lives in another HR platform, build the task the same way.

Done means accepted

Model three events: form opened, form submitted, record accepted. A submission can fail validation, time out or sit in pending review, so only accepted closes the onboarding task. On submitted, the assistant says processing is pending. On correction-needed, it shows a neutral reason and a link back to the form, never the rejected value. Never invite the employee to paste the details into chat as a fallback: if the form is down, show the support route and set the state to unavailable.

The form should receive the employee's authenticated identity or a short-lived handoff token bound to that purpose, not an identifier from a query string. Return only a transaction reference and a safe status to the orchestration service. Use an idempotency key built from employee, form version and workflow instance so retries create one record, and cap the retries: a persistent error belongs to the HR systems owner, not to an endless reminder loop.

Keep the record out of the index

Do not index emergency-contact values, and do not count on hiding the page from navigation, because a search connector can still ingest it. In Azure AI Search, security filters trim results by comparing the caller's user or group identity with permission strings stored on each indexed document. That decides who sees a document that is in the index. For this record, take the stronger position that it is never there, so one wrong permission string cannot expose it.

Separate two planes of access. The guidance plane covers instructions, field definitions, update steps and support routes, which approved employees can read. The operational plane covers the actual record, which only designated roles and approved systems can open for an authorized purpose. A manager needs to know that the task is accepted, not who the contact is, so enforce that in the status endpoint instead of asking a prompt to hide fields. Log access to the operational record in the system that controls it, not in AI conversation logs.

Updates, departures and outages

Put the update route next to the original instructions. An update changes the authoritative record and invalidates any cached status, and nobody should be asked to edit a wiki page or send replacement details to a manager. Indeed's guide suggests asking for updates at least once a year, for example at the annual review or benefits open enrollment, and after life events such as a move. Use an existing trigger like that and send a reminder that names no one: "Review your emergency-contact record in the HR system."

When an employee leaves, start the approved retention or deletion workflow from the employment state. Indeed notes that employers are not typically required to keep these forms on file but should check state or local rules, so whether to keep a departed employee's record, and for how long, is an HR and privacy decision that the assistant never guesses.

If the HR API is down, return unavailable with the last-check time and a support route, and never reuse yesterday's accepted as proof. If the company brain is down, the plan still needs a direct route to the form. GitLab's onboarding handbook opens each hire's onboarding issue at least four days before the start date and assigns both the manager and a People Operations team member, who each have tasks to finish before day one. Keep owners and tasks in a place like that, outside the assistant, so one outage does not block the form.

If private data lands in chat anyway, treat it as a privacy incident: restrict the conversation, stop downstream indexing where possible, record which systems received the data, and route cleanup to the accountable owners. Do not copy the exposed values into the incident ticket.

Release rule

Release the workflow after a synthetic run for one form, one employee population and a read-only status endpoint, using synthetic contacts only: a normal submission, a missing required field, a duplicate retry, a withdrawn start, a changed form version, an unavailable HR API, an unauthorized status request and an accidental private-field response. The company brain must never show contact values in chat, search, analytics or ticket titles, submitted must never close the task, and managers must receive nothing beyond the completion state. Then search the index, chat export and analytics store for the synthetic names and numbers. The expected result is zero matches, and the company brain should reject any status response that contains a contact value.

Topics

Related posts

Your team’s knowledge, answered in Slack

Add the Kipwise Agent. It answers from your pages with the source, and asks before it changes anything. 7-day trial, no card needed.