Read the front door for what may be arriving unrecognised, record the hour it landed, and put anything that may be notice in front of a named HR officer before it is answered.
A message lands unlabelled, and the hour it landed is written down before it is read.
02
Nothing in it names the statute, and under 29 CFR 825.303(b) at first nothing has to.
Reason
03
Knowledge that leave may qualify opens five business days under 29 CFR 825.300(b)(1).
04
A limitation is mentioned in passing, and 29 CFR 1630.2(o)(3) comes into view.
05
A supervisor is named, and Gorzynski, 596 F.3d 93, holds the wrong door still counted.
Decide
06
A worry about the numbers arrives, and Directive (EU) 2019/1937 Article 9 starts running.
07
A health detail is disclosed, and 29 CFR 1630.14(c)(1) governs where it may be kept.
Out
08
A contact will not classify, and that doubt is written up rather than resolved away.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Reading what may have arrived, the hour and the question the regulation directs belong to the agent. The recognition, the reply and any instruction belong to a named HR officer.
Example workflow
One contact, arrival to recognition
AgentHuman
1Contact arrivesPortal ticket, HR inbox, chat thread, phone note or a line added to an unrelated question
2Arrival fixed and timestampedThe channel, the hour, the words as sent, the topic on its face and the clock it might open
3Reading proposed, clocks namedWhat the contact may be, each deadline that would follow, the questions still open and confidence
4Controls appliedRecognition checks, clock-start checks, disclosure checks and reading confidence
No human action required
Stages 1 to 4 run unaided, and nothing is disposed of at any of them — the agent is recognising, and the officer lane opens at the confidence gate.
5DecisionSplits at the confidence gate
Nothing operative in view
Goes back in released wording only.
Anything that may be notice
Picks up a named officer read first.
Officer recognition
The contact is held with its wording, what it may be and the deadlines already open.
Recognise · Ask back · Send to counsel review
Recognised — by the named officer▼
6Ticket and records systems updatedOnly where write access and the medical-file rules allow it
7Outcome evaluatedReading stability, clock timing, officer corrections and what review found
Corrections
Each officer correction is counted back into the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding a message is not FMLA notice.
Closing a contact as routine on its own.
Telling an employee to keep a concern quiet.
Answering a disclosure with policy text.
Automation boundaryAgent acts unaided
✓Timestamp the contact at the hour it arrived.
✓Carry the eligibility-notice deadline where a named officer sees it.
✓Ask the further question the regulation directs.
✓Route a health disclosure into the confidential medical record file.
Nothing is closed as routine except inside the boundaries a named officer agreed.
Judging whether a duty to inquire arose.
Deciding an accommodation is not needed.
Ruling that a report is not a report.
Changes to the recognition or routing rules.
Example output
One employee contact, annotated
This serves a people-services team who may have to show, months afterwards, what the employer came to know and on what day — because under 29 CFR 825.300(b)(1) the clock runs from knowledge and not from a request; below is one contact exactly as the agent leaves it.
Contact record · single messageIllustrative example
Contact
Read as
Arrived
Wording of record
Confidence
To be read by
General enquiry, family illness mentioned
Possible FMLA notice, unconfirmed
Logged at 08:41, 3 August 2026
Message as sent, one thread
Held unanswered
The named HR officer, by name
As receivedTaken from the message as sent and the channel log, and it claims nothing about what the contact is in law.
What the ticket holdsMessage as sentChannel and the hourPrior contacts
Why no reply hereWhether this message is notice is a judgement a named officer makes.
ActionRecogniseAsk backSend to counsel review
What the score decidesBelow the configured threshold a contact picks up an officer read before it is answered.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Any contactThrough whatever door it came
03Knowledge
Where knowing is the trigger
29 CFR 825.300(b)(1) runs five business days from the moment the employer acquires knowledge that leave may qualify, and 29 CFR 825.303(b) says the employee need not name the statute.
01Approved path
Nobody labels it notice
In Burnett, 472 F.3d 471, summary judgment for the employer was reversed because a run of ordinary-looking communications had been handled as ordinary.
02Human review
Looked for, and not present
No published benchmark was found for recognising legally operative messages inside a general HR queue, and the EEOC guidance index itself now returns not found rather than only the withdrawn AI pages, so no guidance document is relied on here by address.
04Build an evidence trail
The contact, the hour it arrived and the officer it was raised to stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Helpdesk and ticketingServiceNow HR · Workday Help Ticket queues and the contact log
Message channelsEmail · web chat · portal form Walk-ups logged by a person
Core HR and leave recordsWorkday · UKG Pro · Oracle HCM Leave history and the reporting line
Agent
HR helpdesk and first contact
Reads what arrived Names what it may be Holds for the officer
Records and medical filesRecords store · retention schedules Separate medical-file handling
A queue-level reading figure can read clean while oblique family-health contacts carry most of the correcting. Nestack reports the officer-correction rate by contact class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Oblique family-health contacts
11.0%
3.7×
Review
Concerns about the numbers
7.8%
2.6×
Review
Supervisor conduct in passing
4.9%
1.6×
Watch
Named-policy questions
2.2%
0.7×
Normal
Bar: correction-rate lift against named-policy contacts · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unrecognised message costs
A loop closes when the message answered instead of recognised is a standing case. That suite is what the next contact window is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on oblique family-health contacts.
02Diagnose
The leave nobody saw coming because the message read as a question about sick pay is worked backwards until one cause is left standing.
03Improve
Number the ticket; the wording that raised it is filed beneath it.
04Verify
Nothing closes while one touched recognition case is still red.
05Learn
One case joins the suite, and one line joins the recognition rules.
Learn → DetectThe return edge. The next contact is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, channels, contact recognition, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Recognition scope and automation-boundary definition.
02Channel, queue and ticket-system review.
03Contact routing and recognition-boundary discovery.
04Employee contact capture.
05Recognition logic and clock binding.
06Confidence scoring and officer routing.
07Officer recognition workflow.
08Ticket-system and records integration.
09Recognition and routing cases.
10Guardrails and closure controls.
11Contact-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne queue, one populationProductionProduction service workflowAdvancedSeveral channels / languages
Introduced at Pilot
Recognition to your routing rules✓✓✓
Release by a named officer✓✓✓
Contact-volume baseline✓✓✓
Introduced at Production
Reporting by contact class—✓✓
Officer review inside your own systems—✓✓
Approved write-back—✓✓
Ticket-and-directory integration—✓✓
Introduced at Advanced
Mixed-topic recognition rules——✓
Multi-stage officer release——✓
Heavy contact volume——✓
Multi-topic recognition controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, queue complexity, topic coverage, release controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live contact channels and the officer each one raises to→Contact capture and arrival timestampingWeek 1
02Representative past contacts and how each one was handled→Channel binding, recognition logic and the contact baselineWeek 2
03Your statutory deadlines and the rota that answers them→Recognition mapping, clock binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Channel, queue and ticket-system assessment, then integration setupWeek 2
05Tickets you would not want disclosed→Recognition cases and the failure roundWeek 4
06What no ticket may close→Confidence scoring, officer routing, guardrails and release controlsWeek 3
07A named officer who takes the recognition→Release through the named officer, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
These bands are measured rather than evened; week five carries two because the two truly overlap.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Channel discovery, recognition mapping and the automation boundaryW2Queue integration and the contact-recognition baselineW3Recognition logic, clock binding and release controlsW4Evaluation suite, recognition cases and the failure roundW5Ticket-system integration, pilot contacts and targeted correctionsW6One service cycle run under the people-services lead, then Agent Care handover
Reading the bandEach band covers only the weeks its own work is named for, and week five is doubled by design.
At the end of W6Once the contact record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · HR AI agent
Build a helpdesk agent around the message nobody recognised.
A misrouted IT ticket costs an afternoon; a misrouted HR message costs a statutory clock. Show us one week of your front door and the contacts answered and shut. If a family illness, a diagnosis or a worry about the numbers came through, something began counting that day.
