The questions brokers actually ask.

Velora Marketing is the outbound engine for benefit brokers. It runs email, SMS, ringless voicemail, LinkedIn, AI voice agents, and direct mail through one playbook that pauses on reply, escalates on intent, and books meetings on your calendar. It bolts onto Atlas, HubSpot, or Salesforce, or runs standalone with Atlas CRM included.

Employee benefits brokers, brokerages, and benefits agencies in the United States. We have specific motions for solo brokers (under 25 groups), multi-producer agencies (25–100 groups), and enterprise brokerages (100+ groups across multiple offices). We do not currently target P&C, life insurance, or non-benefits insurance verticals.

No, but it can. Velora Marketing runs on top of an existing CRM (HubSpot, Salesforce, or Velora's own Atlas CRM). Every send and reply syncs back bidirectionally. If you do not have a CRM, Atlas is included at no additional cost — broker-native contacts, deals, renewal calendars, and book-of-business reporting.

No. AI voice agents are one of seven channels — they handle inbound triage and structured outbound qualification calls. The product is a cadence orchestration platform with broker-native intelligence (Form 5500 Signal Engine, Carrier Disruption Radar, Renewal Autopilot). The 'AI SDR' framing has been ground down by 11x.ai and Artisan to a tainted category we deliberately don't position into.

A daily-refreshed lookup over the public Form 5500 dataset (employers with 100+ enrolled lives are required to file). Velora flags employers in your territory who are 90 days from renewal, recently changed broker of record, are above or below the median benefits cost for their industry, or filed late — any of these are real signals to start a conversation. No peer marketing platform ships this.

When a carrier shrinks a network, drops a market, changes its underwriting posture, or adjusts large-group renewal positioning, Velora flags every group in your book affected by it. You get a same-day list of clients with a real reason to call. We track the major medical carriers (Aetna, BCBS, Cigna, United, Anthem) plus the largest regional carriers.

Seven: cold email (Resend + Gmail/Outlook OAuth), SMS cadences (Twilio), ringless voicemail (Slybroadcast), AI voice agents (Retell + ElevenLabs), LinkedIn (in flight), direct mail (planned), and lead-intent reply routing across all of the above. They share a single playbook layer — one config controls all seven.

Velora's AI voice agents are conversational — they ask discovery questions, listen, follow up, and qualify based on the prospect's actual answers. They identify themselves as Velora calling on behalf of your agency, follow your state's required TCPA disclosure preamble (TX SB 140, CA AB 2905, etc.), and never claim to be a human. Recordings are stored, replayable, and labeled for compliance review.

Yes. Brokers commonly start with email + AI voice as the primary motion, then add SMS and ringless voicemail when their prospect base warms up. Each channel is independently toggleable per playbook and per contact. Compliance constraints (TCPA, CTIA) are still enforced on whichever channels you turn on.

Every inbound — email reply, SMS, voicemail return, LinkedIn message — flows through an AI-powered classifier that labels it as interested, not-now, unsubscribe, bounce, OOO, or question. Each label fires a deterministic action: pause the cadence, snooze for the right month, hard-stop the contact, route to a producer's inbox, or auto-respond. You only see the replies that need a human.

Resend handles the modern infra (TLS, SPF, DKIM, DMARC) and we monitor inbox placement per domain via DMARC reports plus inbox-placement testing. New domains get a 14-day warm-up flow. We surface alignment failures and per-domain reputation in the deliverability dashboard. Yahoogle's one-click List-Unsubscribe (RFC 8058) is on every email by default.

Three primary: Atlas CRM (Velora's own broker-native CRM, included at no cost), HubSpot, and Salesforce. Each connection is bidirectional — every send, reply, voice transcript, and AI-classified intent writes to the contact and deal record. Atlas is native (shared schema, no field mapping). HubSpot connects today by pasting a Private App access token into the connect flow; full OAuth handshake is on the near-term roadmap. Salesforce connects today by pasting a session/access token (Production or Sandbox); a Connected App + OAuth 2.0 / JWT bearer flow is on the roadmap once the Connected App passes Salesforce review. Both forms hit the same downstream sync code; the auth method is what's evolving, not the integration depth.

Yes. Standalone mode uses Atlas CRM internally as the contact + activity store, but you don't have to log in or use it. Activity is exported nightly as a CSV or webhook to wherever you do work. Most pilot brokers start standalone and migrate into the CRM surface later.

Direct integrations with Applied Epic and AMS360 are on the enterprise-tier roadmap as custom integration work. For mid-market brokers, the standard pattern is a nightly CSV export from the AMS into Velora's contact ingestion endpoint — proven across pilots. Enterprise tier includes a custom-build integration as part of onboarding.

Cal.com (recommended), Google Calendar, Outlook, and Atlas calendar. Hot replies route to the right meeting type with the prospect's context pre-filled, so the prospect picks a slot from a calendar link customized for them and you see them on your calendar with notes attached.

TCPA enforcement happens at the dispatch layer, not as a producer-side checklist. We maintain a 51-state matrix (FL, WA, OK, MD mini-TCPA, plus 47 others), enforce quiet hours and day-of-week rules per state, and inject AI-voice disclosure preambles for jurisdictions that require them (TX SB 140, CA AB 2905). The platform refuses to send when state rules aren't met. 24 tests cover state-by-state transitions.

STOP, UNSUBSCRIBE, REMOVE, QUIT, CANCEL, and END are honored within seconds across SMS, email, and voice. The contact is hard-stopped on every channel, the cadence terminates, and a do-not-contact flag is written to the CRM. We send the CTIA-required confirmation reply to SMS opt-outs but no further messages.

Not yet. The audit period is scoped for late 2026. We will not claim SOC 2 in writing or in-product until the report is in hand. Our security posture is published openly at /security with honest 'shipped / in-flight / planned' labels — no marketing fiction.

Velora Marketing does not currently process Protected Health Information by default. Plan-data ingestion is explicitly scoped to non-PHI fields (group name, plan year, renewal month, enrolled-lives band). A HIPAA-aware mode for agencies that handle PHI is on the roadmap; we will require a signed BAA before enabling it. Until then, the safer default is to keep PHI in your AMS.

Velora's primary audience is U.S.-based brokers, but the platform respects DSAR (data subject access request) flows and supports per-contact data export and erasure. The cookie consent banner and public-facing DSAR submission flow are both in flight on the marketing surface. Server-side, the data deletion path has been wired since launch.

Every multi-tenant table (companies, deals, activities, notes, clients, brokers) carries an agency_id column with composite indexes. Queries filter on agency_id at the data layer — by construction, not by application logic. This was completed across 31 routes in April 2026 and is verified by 31 dedicated tests. See /security for the full posture.

Neon Postgres in U.S. region, encrypted at rest with AES-256. Object storage (audio recordings, uploads) on Vercel Blob, also AES-256, scoped per-agency, signed-URL only. Application is deployed on Vercel's edge network in U.S. regions. Sub-processor list is published at /security with each vendor's purpose, region, and homepage.

Within Velora Health: a small operations team has read access for support and incident response. All access is logged via the append-only events table. Within your agency: SSO + role-based permissions (planned) gate per-producer scoping. We do not share customer data with third parties for any purpose, including model training.

Yes — at any time, no friction. Full-export endpoint is in the admin surface. Returns JSON with every contact, dispatch, reply, and audit event tied to your agency. We don't lock you in. Procurement-tier brokers can additionally subscribe to a nightly warehouse-mirror webhook for continuous mirroring.

Three tiers — Pilot, Agency, Enterprise — sized to your book. Pilot suits solo and small shops with capped send volume; Agency fits 5–50 producer firms; Enterprise is an annual contract priced by office count and total send volume. We're in pilot pricing — every engagement is scoped one-on-one. Contact us for pricing.

Pilot tier is month-to-month with no annual lock-in. Most agencies treat the first 30 days as the trial — they ship one cadence, see the metrics, and decide. We also offer 14-day shadow pilots where we build one cadence on a sample of your book and run it without you needing to sign anything. Contact us for a shadow pilot.

Solo brokers: 20 minutes (CSV import, domain auth, first cadence dispatch). Multi-producer agencies: 1–2 weeks (CRM connection, per-producer scoping, sales-leader dashboards, first 3 cadences). Enterprise: 4–8 weeks with a named implementation lead — SSO, custom AMS integration, multi-office data partitioning, compliance review.

Full feature surface, capped send volume. You can use every channel, every intelligence engine, every CRM connection. The cap is on monthly volume only. Most solo brokers stay on Pilot for 6–12 months and pay the platform off with one new closed group.

Yes — bundled standard with Agency and Enterprise tiers. A named implementation lead walks through CRM connection, domain auth, A2P 10DLC registration, deliverability warm-up, first cadence build, and producer training. Pilot tier is self-serve but documented; we'll answer Slack questions directly.

Apollo and Outreach are general-purpose B2B outbound platforms — strong at SDR motions in tech sales. They don't model employee benefits: no Form 5500 Signal Engine, no Carrier Disruption Radar, no benefits-specific TCPA matrix, no broker-native merge tags (SIC, enrolled lives, renewal month). Velora is purpose-built for benefits brokers, with the broker domain knowledge baked into every layer. See /vs/apollo for the full comparison.

AgencyZoom and Zywave are agency management systems with a marketing module bolted on — they handle contracts, compensation, member enrollment, and policy management as the core, with marketing as a side feature. Velora is the inverse: outbound and pipeline-generation are the core surface, and we integrate with the AMS rather than replace it. See /vs/agencyzoom and /vs/zywave for the side-by-side.

HubSpot is a strong general CRM and marketing automation platform. We integrate bidirectionally with HubSpot — many Velora customers run Velora alongside HubSpot, with HubSpot as the contact + deal source-of-truth and Velora as the outbound dispatch + intelligence layer. The two are complementary, not competitive. If you're choosing between them for outbound only, Velora's broker-native intelligence wins on conversations-per-touch.

Yes — and the marketing agency typically becomes more productive. Velora handles dispatch and cadence (the mechanical layer); the agency handles strategy, content, and creative (the high-value layer). Several pilot agencies have an external marketing-services partner who builds content into Velora templates and reviews monthly performance.