Verify Video Callers First

Why now

As of August 2, Halo by Scam AI ranked 15th in Product Hunt’s new-product feed and focuses on determining whether the person in a video call is real. ^S1 Its launch highlights a specific gap: even if the image looks like a relative, users still need to verify through a known number or family group before sending money. ^S2

The core users are parents who live alone or are not comfortable with phone security settings, and the adult children who support them remotely. The key moment is when a familiar face suddenly asks for money, a verification code, or screen sharing. Family trust and urgency compress the time available for judgment. Adult children need to preconfigure known numbers, a family group, and backup contacts so parents do not have to find someone to verify with in the moment.

Start on Android, with Verify First as a Quick Settings tile. TileService lets users trigger a shortcut action while remaining in their current app. ^S3 Tapping it opens a full-screen protection screen that first covers verification codes and payment entry points. For supported calling apps, an accessibility service performs a fixed mute action; control rules are maintained separately for each app. Accessibility use must be clearly disclosed, and automation is limited to fixed flows triggered by the user. ^S4 Identity checks are sent through pre-registered SMS deep links or family-group links. The backend stores only challenge status, response text, and expiry time. The first release supports a small number of calling apps, does not use a real-versus-fake face model, and does not access full call audio or video.

Recruit the first users through adult children who manage their parents' phones. Position the product as a family anti-scam drill: an adult child sends a simulated loan request in the family group, and the older relative practices pressing Verify First. A results page can generate a setup checklist without private answers, making it easy to share with siblings. Short videos about setting up known numbers and backup contacts for parents are likely to drive more installs than broad messaging about deepfakes.

Halo by Scam AIGoogle

Based on its public positioning, Halo by Scam AI focuses on determining whether the person in a video call is real. ^S1 It addresses the credibility of the image or identity, which is a direct response to synthetic-face and face-swap attacks. But if a real scammer has taken over a relative’s account, content detection may not stop a transfer request. Even with an accurate result, the user still has to decide whom to contact next. It also does not establish a family verification order using known numbers, a family group, and backup contacts. This proposal’s opening is to bypass real-versus-fake detection and move high-risk requests onto a separate channel. It does not need to prove that the image is fake; it only needs a response from the relative or another family member before money is sent. The trade-off is that verification speed depends on whether family members are available, and the product must handle no response and invalid numbers.

Family passphrases and callbacks to known numbersGoogle

The FTC recommends slowing down when faced with an emergency request for money from a family member: call back using a known number, or ask a question only that person would know. ^S2 This approach is free and works on any phone. It also does not depend on face or voice authenticity models. The gap is that, under pressure during a call, people often cannot remember the full process. A victim may also stay on the original call, allowing the caller to prevent them from contacting family. Answers to ad hoc questions drawn from social media may already be exposed. A callback alone provides no clear status, and a missed call can be mistaken for reassurance. This proposal turns the advice into a button, fixed contacts, and three outcomes. It can also hide verification codes and payment entry points first, reducing the chance of acting while listening. The key question is whether the added steps will feel burdensome enough that older users bypass them.

Charge a family subscription covering older relatives, adult children, and backup contacts, with an allowance for SMS confirmations. The basic verification flow is free; automated protection rules and additional family members are paid features.

A third-party calling app can change its interface, causing mute-control targeting to fail. If the product still indicates that the call is muted, it creates a more dangerous false sense of safety. A full-screen overlay only blocks what is currently visible; it cannot ensure that system notifications or another device will not expose a verification code. If a pre-registered number has changed, the request may reach the wrong person. If a family-group account is compromised, the independent channel can fail as well. Private questions sourced from social media may not be truly private. In a genuine emergency, a backup contact may not respond promptly, leading users to bypass the process. The product requires ongoing device compatibility maintenance and repeated testing of failure states.