Frequently asked questions

No. Public thread discovery is one ingestion layer in an eleven-layer GTM operating system. Wavly fuses external buying intent with first-party website signals (bp.js), product analytics (PostHog/GA4), CRM (HubSpot), and revenue (Stripe) in one Demand Graph — then orchestrates replies, Signal-to-Pages, and full attribution. Community listening alone is Clay/Common Room territory; Wavly is revenue OS infrastructure.

It's the GTM equivalent of Vercel for deploys or Stripe for billing. You install it once and it runs in the background, continuously turning real-time intent signals into customers. You don't 'do marketing' — the runtime does distribution.

Primary buyers are VP Sales, RevOps, demand gen, and GTM leaders running serious pipeline programs — teams evaluating intent, outbound, and attribution alongside Apollo-class vendors. Agencies and multi-brand operators use Scale. Free and Indie tiers exist as land-and-expand entry for smaller teams on the same runtime.

Every high-intent signal (e.g. someone in a public thread asking 'is there a tool for X?') triggers a unique, personalized landing page generated in under 30 seconds. The page echoes the asker's exact language and pains. We post a helpful, non-promotional reply in the thread. The asker clicks your profile → lands on a page that reads their mind. No competitor ships this — it's the 10x unlock.

You stay in control. Scout drafts every reply and page. You review and approve (or edit) before anything goes live. We deliberately do NOT run blast-mode autopilot — that kills accounts and brands. Approval takes seconds via keyboard shortcuts.

Every reply includes a tracked short link. Every Signal-to-Page tracks views. Every signup gets tied back to the originating signal. You see the full funnel: signal → reply → click → view → signup → MRR — in the Pipeline view.

Yes, if you want on-site behavior in the same Pipeline as your public threads. In Settings you copy a single script tag (like installing Google Analytics, but for intent). It runs only on your domain, uses a first-party visitor id, and sends page views plus signals such as pricing-page visits, deep scroll, long stays, form starts, and form abandonments—we never capture what people type into inputs. Advanced: optional custom events from your code.

We only help you post high-value, context-specific replies that follow each platform's rules. No spam, no link-dropping, no bulk DMs. Signal-to-Page is hosted at thewavly.com — you never drop an external link in a hostile thread.

Setup is 60 seconds. First signals appear within an hour of your first scan. First Signal-to-Page is ready in under 30 seconds after you approve. Time to first attributed signup depends on your ICP — most teams see a tracked click within 72 hours.

Yes — 1 product, 25 scans/day, 10 drafted replies per month, 1 Signal-to-Page. Enough to see the runtime work. Upgrade when you want volume.