It pings the moment your name fires.
The whole point of MeetPing is keyword watch. You give it a list of names and topics. It runs every confirmed Parakeet token through a word-boundary regex, a Soundex pass, and a Levenshtein fallback. The instant any one of them matches, the popover opens.
Most people who try MeetPing do it for one of three reasons: they keep getting asked questions in standups while half-listening, their name comes up in customer calls and they miss the cue, or they sit on three meetings at once and physically cannot pay attention to all of them. The pitch is the same in every case — you don't need every word, you just need the moment your name or your topic surfaces.
That moment is what keyword watch detects. The watcher reads confirmed Parakeet output token by token (we ignore the volatile partials so a half-formed word doesn't trigger), runs a Unicode-aware word-boundary regex, and only then fires. A keyword like rob won't match robust. A keyword like api won't match capital. There is an 8-second per-keyword cooldown so a single mention pings exactly once.
okay let's pull up the metrics from last sprint and walk through them
the activation chart is up 14% week over week, retention basically flat
we did get a bunch of churn from the enterprise tier, mostly billing-related
so on the next quarter — Ogtay, what does the
roadmap look like for the listener service?
do we still want to ship the remote alerts channel before the holidays?
and how are we thinking about the privacy posture of on-device Parakeet
right, makes sense — pin that for the security review thread
Three matchers, one watcher
Proper nouns are where ASR breaks. The decoder has heard a million sentences with the words "October" and "captain"; it has heard ten with "Ogtay" and "Ksenia". Streaming Parakeet on uncommon names produces predictable mutations: Ogtay comes out as octaye, october, or even aug-tay. None of those substrings match your literal keyword.
MeetPing runs three matchers per token in this order: a word-boundary regex (cheap, exact), a Soundex equivalence check (catches phonetic mutations), and a Levenshtein distance check with a small edit budget (catches the rest). Soundex maps both Ogtay and octaye to the same four-character code O323; Levenshtein with edit distance ≤ 2 picks up the long tail. We score each match and break ties in regex's favour so common words don't false-fire.
For a worked example of the phonetic algorithm, see the phonetic-match writeup.
Real keyword lists, from real users
- Engineeryour-name, ship-date, p0, on-call, postmortem, regression
- AEyour-name, account-name, ARR, churn, renewal, procurement, legal
- PMyour-name, roadmap, q3, OKR, NPS, beta, launch
- Parent on standbyyour-kid-name, school, principal, fever, pickup
Watchword lists live in profiles, so your engineering keywords don't fire during a customer call. See profiles for how to set those up.
Profiles
Per-context watchword presets. Engineering, sales, all-hands, parental. One click to switch.
Past-30s replay
Every ping comes with 30 seconds of context before the keyword and 30 seconds after.
On-device privacy
Zero outbound calls. RAM-only audio. No transcript file. Pulled from a real audit.
Stop missing your name.
Add ten keywords, hit save, walk into your next meeting. The popover only opens when one of them fires.