Standups, caught the first time.
A configuration of MeetPing tuned for engineering standups, sprint reviews, and incident bridges. Auto-arms when the call starts, pings on your name and the tickets you own, captures the 30 seconds before each ping so you can rejoin the thread without rewind.
"Wait, sorry — could you say my name again?"
The standup ritual is fifteen minutes of round-robin status with one or two moments that actually require you to speak. Most of the call is other people's status. The failure mode is the same in every engineering org: you tab into a PR review, your name comes up in a question about a ticket you own, the round skips past you, and the scrum-master tags you out-of-band ten minutes later. The cost is a context switch you would not have needed if you had heard the question at the moment it was asked.
The other failure mode is the on-call rotation. You are half-listening because you are watching alerts, and the incident commander says the name of the service you own three sentences before you process it. By the time you unmute the conversation has moved on and you are answering the wrong question.
MeetPing watches the audio path while you are heads-down. It runs on-device — Parakeet TDT v3 on the Apple Neural Engine — so there is no bot in the call, no audio leaving the laptop, no IT review needed. The listener arms automatically the moment Zoom, Google Meet, Microsoft Teams, or a Slack huddle takes the mic, and disarms when it releases. You install it once, you do not touch it again.
The watchwords for an engineering standup are predictable: your name, the names of the services or modules you own, the ticket prefix or two you are responsible for, the words "P0", "regression", "rollback", "on-call", "incident". MeetPing fires on any of them and opens the popover with the past 30 seconds of transcript already highlighted. The next 30 seconds fills in live so you can read the question while you are still tabbing back into the meeting window.
What you wire up
- Keyword watch
The matcher itself. Word-boundary regex first, then Soundex for phonetic mutations, then Levenshtein for the long tail. Handles ticket prefixes (
PROJ-1234), service names with hyphens, and acronyms that ASR normally mangles. - Profiles
The engineering profile lives separately from your personal one. Ticket IDs, on-call services, sprint identifiers — none of which should fire in your 1:1 with your manager.
- Auto-arm
Standups happen on a recurring cadence; you should not have to remember to switch the watcher on. The Core Audio + foreground-app detector handles it.
- Past-30s replay
When your name fires you get the 30 seconds before the trigger plus the 30 seconds after. Enough to rejoin the thread cleanly, not so much that you have to read.
- On-device privacy
Zero outbound calls in v0.1. Verifiable with Little Snitch. This matters in regulated environments and on customer-facing calls where the standup spills into a debrief.
Related reading
Keyword alerts on Zoom that fire on time
Why captions are not alerts, where the two-second budget goes, and the matcher passes that make uncommon names trigger.
read ›Two meetings at the same time
An audio-routing and watcher setup for the standup-plus-incident-bridge case.
read ›Why on-device ASR matters
The latency, privacy, and IT-review case for running Parakeet on the ANE instead of round-tripping to a cloud endpoint.
read ›Standups, on-call, sprint reviews.
Install MeetPing, configure the engineering profile, walk into the next standup. $24.90 lifetime, signed and notarized, on-device.