Show HN: OnAir – create link, receive calls

Original Article ↗ Hacker News Discussion ↗

Product concept & core value

  • Service provides a shareable link that routes instant audio/video calls without revealing phone numbers.
  • Intended to lower friction vs. “book a call” tools like Calendly and vs. generic chat bubbles.
  • Integrates with Google Calendar; availability can be auto-managed (always on, always off, or scheduled with busy times respected).
  • Mobile apps (iOS/Android) and browser notifications let link owners receive calls.

Perceived advantages vs phone / existing tools

  • Hides personal numbers while still enabling direct contact.
  • Supports routing: round-robin across devices or team members, escalation, call logs.
  • Can capture lead info (name, email), record and transcribe calls, and potentially connect to AI agents.
  • Internationally accessible without long-distance charges; can embed as widget, email signature image, or URL on sites, business cards, cars, etc.
  • Some see it as smoother than WhatsApp/phone for small teams needing lightweight call-center-like functionality.

Skepticism & pushback

  • Several argue phone numbers with click-to-dial already provide one-click calling with better ergonomics on mobile.
  • Concerns that users won’t repeatedly check for “online” status; preference for leaving voicemail and getting a callback.
  • Some feel the main use case (customers “hopping on a quick call”) may be less compelling for younger users who avoid synchronous calls.

Pricing & business model concerns

  • Pricing page initially perceived as misleading around “$9/month” vs “$9/user/month”; confusion about how many people/links that truly covers.
  • Feedback suggests making per-user pricing explicit and offering a free tier to compete with WhatsApp and similar tools.

Feature requests & ideas

  • Scheduled calls or integrated fallback (Calendly link, offline messages).
  • SMS/WhatsApp handoff, voicemail with emailed transcripts, callback notifications when someone becomes available.
  • CNAME/white-label domains and deeper integrations (Salesforce, Gong, PBX, intercom systems).
  • Disposable/alias links, IP blocking, and rules for who can contact when.
  • PSTN/VoIP numbers as an alternative entry point for users without headsets.

Implementation notes

  • Built on LiveKit (WebRTC); previously tried Agora and found its API difficult.
  • Discussion about Ruby vs Elixir for this telecom-adjacent domain, with differing opinions on suitability.