ConnectWiz Integrations
Your stack, connected — and described by what it really does.
Integration pages usually list logos. This one lists behaviors: what syncs, in which direction, under whose ownership, and where the honest boundaries are. Because "integrates with X" is a claim about depth, not a sticker.
Commerce
WooCommerce & WordPress
WooCommerce — two-way, governed
One-click pairing, deep product import, real write-back — under field-level ownership you choose, a rehearse mode per operation, and a visible conflicts ledger. The full story is on the Commerce page.
Full pageWordPress plugin
Embeds the chat widget on your site and mints signed SSO tokens — logged-in customers are recognized in chat, orders and all, without re-registering.
Full pageGoogle & Meta shopping feeds
A tokenized product feed in Google’s schema (Meta Commerce Manager reads the same) keeps your ads catalogs in sync — no app review in the path, no manual re-uploads.
Shopify Soon
The groundwork is real — Shopify customer identities already federate onto contacts, and today Shopify stores connect via the API and webhooks. A native two-way sync in the WooCommerce mold is on the roadmap, and this badge flips when it ships, not before.
Full pageSupport & tickets
Zendesk — a bridge for teams mid-transition
Push: tickets out
ConnectWiz ticket conversations create Zendesk tickets and mirror replies as comments — so a team still living in Zendesk sees the work without asking.
Full pagePull: agent replies back
A Zendesk trigger posts agent comments back into the ConnectWiz thread — secured by a shared secret, with a loop guard so the two systems never ping-pong a comment forever.
Honest scope
It’s a ticket bridge — create, reply, both directions toggleable — not a Zendesk help-center, macro or SLA import. Teams use it to migrate gradually, then switch it off.
CRM
Estesoft Stella — your CRM, visible from the conversation
The first provider on our provider-agnostic CRM port: clinics running Stella keep their CRM and gain a conversation layer that actually knows it.
Live context, identity-locked
Appointments, quotes, balances, notes and documents from Stella surface on the conversation — and the AI can read them for exactly this customer, never by guessing an ID.
Bookings write back
An appointment made in a chat lands in Stella’s diary — and where the vendor’s API can’t carry a detail, the sync says what it dropped instead of dropping it silently.
Deliberate refusals
Medical treatment records are never read or displayed, the vendor’s own lifecycle labels are never overwritten, and no full two-way mirror is pretended — the boundaries are design decisions, written down.
Estesoft Stella — full page · Running a different CRM? The port is provider-agnostic by design — tell us yours. And when you’re ready to leave the old system entirely, the migration engine below carries your history in.
Marketing & providers
Bring your own providers — the house philosophy
AI: your keys, 5 providers
Wiz runs on your own provider keys across five AI providers and dozens of models — no token markup, model choice per use, and the freedom to leave any vendor. The full story is on the AI page.
Push: your OneSignal
Visitor web push runs through your own push app on your own domain — because that’s how web push actually works, and pretending otherwise breaks on day one.
Bookings out, busy time in
Appointments push to Google, Microsoft 365 and Apple/CalDAV calendars and vanish on cancel; external busy time subtracts from availability, so no door — human or AI — can offer a taken slot. Details on the Booking page.
Direction per source
Each calendar plays the role you assign — read, write, both, or busy-only — so the clinic’s shared calendar and a practitioner’s personal one coexist without overwriting each other.
Ads & compliance
The plumbing between conversations, ad platforms and regulators
Meta Conversions API
A won deal reports back to the ad that started the chat — as a purchase event with proper identity matching per channel — plus lead-quality signals from your CRM funnel. Your dataset, your token, off by default; four gates (consent included) before any event leaves, and a health panel showing what was sent and what was refused, with reasons.
Full pageHonesty rule for this section
Ad and compliance integrations only ever fire behind consent gates, and every refused event is logged with its reason. If a number can’t be matched confidently, it isn’t guessed — a wrong identity costs someone else’s privacy.
Migration
Leave your old CRM. Keep your history.
A real migration engine
For supported source systems: contacts, appointment history, quotes, sales orders, receivables and notes import through a queued, resumable engine — run with our team, because switching CRMs deserves an operator, not a button.
Skips reported by name
The engine refuses to invent values — a record missing its currency or date is skipped and counted, so "migration complete" never hides records still living in the old system.
Ownership flips last
Data ownership transfers as the final step, after the import proves itself — the old system stays authoritative until the moment you decide otherwise.
One OpenAPI contract
The entire platform is specified in a single OpenAPI 3 document — the same contract our web panel and mobile app generate their types from. No shadow endpoints, no doc drift.
Scoped Commerce API keys
Tenant-issued keys with explicit scopes — catalog read, orders read, orders write — power your own storefront or app on our catalog and order engine.
Inbound webhooks, secured
Any external system can start an automation: each flow webhook trigger has its own URL, its own secret, HMAC verification and replay protection — and payloads are data, never instructions.
Outbound: flows call you
The REST step calls your systems at exactly the moments you draw on the canvas. A generic subscribe-to-all webhook feed isn’t built yet — stated here, not discovered in a sales call.
Depth beats logos.
Connect the pieces you already run — and know exactly what each connection does before you flip it on.