Complex day at Verkada

Commit the phone path before 50 entrances copy a failing route

Published Oct 28, 2026

You’re the product manager. Your team is in the room.

The setting

makes cloud-managed security and building systems for businesses and institutions with many sites. lets visitors reach a person by video or audio call to get into a building or ask for help.

The phone integration promises one answering experience while its failure path can strand visitors at the door.

The rollout protects a uniform corporate phone workflow, while the calling path must preserve a reliable handoff when an endpoint or network policy fails.

Who you’d be doing this for

“A courier was already talking to us, then the audio vanished and the tenant called asking why we never answered.”

Eshe Mburu · Security Operations Supervisor · a character in this brief

Oversees operators who verify visitors and unlock doors across a multi-tenant office portfolio.

What is at stake

Visitors at two pilot buildings lose live calls after an answer connects. You must choose a routing path that protects the rollout without locking in an unverified failure mode.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • enterprise phone consistency vs. verified call resilience
  • fast rollout vs. reversible evidence gathering
  • aggressive failover vs. operator context
  • network remediation vs. calling-path accountability

Why Verkada

Intercom calling must remain reliable across PSTN and VoIP endpoints as enterprise customers connect entrances to corporate phone platforms.

Written with these in mind

technical enterprise product managercommunications platform product managerphysical security product leader

Not your kind of problem? 77 more at Verkada, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Verkada. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on crossing a deadline that can't be undone.

The same setting, from another role

Each is set around Verkada’s Verkada Intercom, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to engineer security-critical controls whose correctness holds up even when carefully examined by skeptics.