Meta lead sources
Lead source, campaign, form, consent, and durable ingestion substrate exist. The provider-side webhook rollout and full launch acceptance are still being completed.
Integrations
Connect the work without hiding the handoffs.
The goal is one operating record, not a longer logo wall. Every connection is labeled by what is actually available, what remains in acceptance, and what is only planned.
Connection statusAvailable in parts In acceptance Available in parts Available in parts Available Planned
Useful today, honest about the edges.
Vapi and Twilio voice
Public callback ingress and governed voice substrate exist. The dialer remains disabled until its separate acceptance gates pass.
Appointments and calendars
Public booking and appointment records are available. Calendar-provider sync depth depends on the connection and remains launch-scoped.
Transactional email
Verified transactional delivery supports system confirmations and owner alerts. This does not imply every marketing or lead email workflow is active.
Stripe
Stripe provides the secure subscription-billing path used after account activation. Joining the public waitlist does not create a payment or subscription.
Carrier and quoting tools
Carrier references exist, but direct carrier connections and complete quoting-tool coverage are not promised as available.
No implied connection: a provider logo, account, or credential does not mean a workflow is active. Agent access is confirmed during activation and acceptance.
What a good connection must prove.
Correct organization and ownership
Provider events and records must resolve to the right organization without accepting a caller-supplied tenant shortcut.
Verified provider identity
Signed webhooks, OAuth, or supported provider credentials are checked before trusted state changes.
Durable result, not a queued request
The operating system tracks the destination response and business outcome instead of treating a queued network request as success.
Safe failure and recovery
Retries remain bounded and idempotent, and a failed downstream handoff stays visible rather than silently losing the work.
Bring the tools that matter into one operating flow.
Join the waitlist and follow the product as integrations become launch-ready.
Join the free waitlist