THE WORKPLACE FILE
●SERA / AI OMBUDSMAN / WORKPLACE REPORTING / PUBLIC WAITLIST
Company / Human resources / 01

Sera wants to make speaking up feel safe.

An AI proxy between employees and HR. A simple idea with a difficult assignment: make the first conversation feel safe enough to start.

Advertisement

An employee has a concern. Before anybody in HR hears it, that employee has another concern: what happens to me if I speak? Sera has built its proposition around the space between those two thoughts. The Boston company calls its product an AI ombudsman, a private intermediary for workplace reporting. Its interesting idea is about who carries the message. The employee supplies the concern. Software is meant to stand between the person and the organization receiving it.

The short version
  • Sera proposes anonymous or named workplace reporting, with an AI proxy between employee and HR.
  • The intended buyers are chief human resources officers and senior leaders.
  • The public homepage invites visitors to a waitlist.

The first audience is the person who hesitates

Consider a hypothetical employee deciding whether to describe misconduct. A form can ask for dates, names and details. It cannot make the decision to disclose feel safe. Sera’s employee page puts control over identity at the beginning of the process: the reporter chooses whether to remain anonymous or use their name. The next step assigns Sera the role of proxy. HR then receives and reviews the issue.

That sequence is the product’s clearest explanation. For the employee, the proposed benefit is a way to communicate a concern while withholding identity. For the employer, it is a route for hearing information that might otherwise remain private. Those are different incentives sharing one interface. Sera has to make the arrangement credible to both sides.

The proposed reporting journey
  1. 01ChooseAnonymous or named
  2. 02RelaySera acts as proxy
  3. 03ReviewHR receives the concern
The message moves. Identity is meant to move only by choice. Diagram of Sera’s published workflow.

A buyer, a user, and a delicate bargain

Sera addresses its homepage to CHROs and senior leaders interested in trust, security and accountability. Its employer page pitches risk reduction and employee retention. This places the business in workplace reporting and employee relations software, alongside the tools organizations use to receive misconduct concerns and manage their response.

The commercial direction is business to business: sell the reporting capability to an organization whose employees use it. The public invitation is to join a waitlist, while the employer page offers a demonstration. For a prospective buyer, the useful next conversation would cover the subscription, implementation work and responsibility for handling incoming concerns. Those are separate costs, even when they arrive under one purchasing decision.

There is a small but consequential tension here. The organization would buy the tool; the employee would decide whether to trust it. A pleasant interface cannot settle that bargain by itself. An employee wants to understand who will read the report. A buyer wants enough information to act. The proxy has to preserve a workable relationship between those needs.

“SERA Acts as Your Proxy”

Sera’s employee reporting workflow

Anonymous is the entrance. The handoff is the story.

Anonymous reporting already has competitors. NAVEX describes anonymous communication between a reporter and an organization’s whistleblowing team through EthicsPoint and WhistleB. AllVoices offers anonymous or named reporting feeding into case management. Sera therefore enters a market where privacy, reporting channels and follow-up are established buying considerations.

Its chosen distinction is the AI intermediary, expressed through the ombudsman label. That is a more personal promise than an electronic suggestion box. It implies help conveying a concern across an uncomfortable boundary. Sera’s FAQ also describes AI assistance with verification and identifying patterns. These are the company’s descriptions of its approach; evaluating them would require seeing how the system handles an actual reporting scenario.

The word ombudsman deserves attention, too. The International Ombudsman Association organizes its professional framework around independence, impartiality, informality and confidentiality. For a buyer considering Sera, that framework supplies useful questions: who controls the intermediary, what gets passed along, and how are the limits explained? A product name opens that discussion. The operating arrangements have to finish it.

Sera’s purple workplace campaign illustration: a collage of faces with secure, anonymous and actionable messaging
A dozen faces. One awkward first conversation. Sera’s published campaign illustration puts people behind the reporting pitch; it is promotional artwork, not a team portrait.

The privacy policy has a second audience

Sera’s privacy notice, dated February 14, 2025, identifies the business as Sera Inc. It describes facilitated reporting as helping users communicate workplace incident information. The document also lists incident descriptions among sensitive information the service may process. That matters because a report can carry far more revealing material than the name field suggests.

The notice names Google Cloud AI, OpenAI, Anthropic and Amazon Web Services AI as third-party AI service providers, and says inputs, outputs and personal information are shared with such providers to enable the AI products. These are disclosed technology providers, rather than evidence of commercial endorsements. An organization considering a deployment should understand the particular data path its employees would use.

Here is the practical distinction: keeping a name from HR and determining which systems process a report are two different design questions. Sera’s proposition concerns the first; its privacy notice makes the second visible. A useful demonstration would walk through both, using a fictional incident and showing what the employee, HR reviewer and service providers each receive.

A useful thing to copy

Explain the handoff before asking for the story: who receives it, what they see, and who acts next.

Trust needs somewhere to go

The copyable lesson in Sera’s design is that a reporting journey begins before submission. Give people a clear identity choice. Explain the intermediary. Show the destination. Those steps turn a broad promise about workplace transparency into a sequence an employee can inspect. They also give a buyer something concrete to test during procurement.

The organizational work comes after that sequence. A private channel needs a responsible recipient, a sensible response process and people willing to address the concern. Where the recipient ignores reports, or where incident details identify the reporter despite a hidden name, the channel’s usefulness narrows. That is an operating condition to examine, rather than something a privacy button can resolve.

Sera’s wager is that an AI proxy can make a difficult first conversation easier to begin. The compelling test is ordinary and specific: can an employee understand the choices, tell the story and see how it reaches someone able to respond? A workplace reporting product earns its place in that handoff.