Integrations

Connect the tools you already run your business with.

MVPConnect plugs into your phone system, your mailbox, your merchant account and your books — directly, with no middleware in between. Text and call from your store number through Twilio, Telnyx, Quo or Zoom. Thread your real Gmail or Outlook mailbox into the same inbox as Messenger and Instagram DMs. Take cards on your own Authorize.Net or Clover account, with funds settling to your bank. Push clients, sales and invoices to QuickBooks Online. Every connection is yours — your keys, your accounts, your billing.

// Messaging

Every channel a broker actually uses.

Four SMS providers, two mailbox providers, and Meta's two social channels — all landing in one inbox, threaded per client. Bring whichever accounts you already pay for; nothing here resells you a phone number.

Twilio · SMS + voice

Two-way SMS and voice from your store's own number, threaded against each client. Inbound texts raise a badge in the sidebar; outbound is one click from any client record.

  • Per-store connection — your number, your A2P 10DLC registration, your billing
  • Inbound SMS matches an existing client by number, or creates one if it's new
  • Voice on the same number, with call recording and configurable IVR menus
  • Delivery-status callbacks recorded so a failed send doesn't look like a delivered one

Telnyx · SMS + voice

A second carrier option with per-store messaging profiles, often better economics at volume. Same threaded inbox and client auto-attach as Twilio.

  • Per-store messaging profile and dedicated number
  • Inbound SMS threads under the matching client, identical to Twilio's behaviour
  • Voice supported on the same number
  • Swap providers per store without changing how the inbox works

Quo · SMS

Connect an existing Quo number for two-way SMS without standing up a carrier account. The quickest of the four to set up — paste an API key, pick a number, send.

  • Bring your own number — no carrier registration, no sub-account
  • Inbound and outbound threaded against the matching client
  • Signature-verified webhooks, so inbound stays trustworthy
  • A shared store-wide number, or per-user numbers

Zoom · SMS + meetings

Zoom does double duty: SMS through a private server-to-server app on your own Zoom account, and real meeting links generated when a video appointment is booked.

  • SMS via your own Zoom server-to-server app
  • Meeting link created at booking time and included in the confirmation
  • Same unified inbox threading as the other SMS providers
  • Connected per store from the integrations page

Gmail · OAuth

Connect your real Gmail or Google Workspace mailbox over OAuth. Client email threads flow into the unified inbox, and replies you send land in your actual Sent folder.

  • OAuth — no app passwords, no SMTP credentials, no DNS records
  • Push sync, so new mail arrives without waiting on a poll
  • Inbound threads auto-attach to the matching client
  • Per-user mailboxes as well as a shared store mailbox

Outlook / Microsoft 365 · OAuth

The same story for Microsoft 365. Inbound sync over Microsoft Graph, outbound through your own mailbox, threaded against the client like everything else.

  • Microsoft Graph sync for inbound, sendMail for outbound
  • Same auto-attach-to-client threading as Gmail
  • Sits alongside SMS and social in one inbox view
  • Connected per user, so each person's mailbox stays their own

Facebook Messenger + Instagram DMs

One Meta Business connection covers both. Authorize once, pick the page, and Messenger and Instagram conversations thread into the same inbox as SMS and email.

  • Page-level OAuth through Meta Business, with a page picker
  • Instagram DMs ride the same connection — one authorization, both channels
  • Inbound messages can trigger a workflow like any other channel
  • Threaded per client, so the conversation doesn't fragment by app

Your own sending domain

Send invoices, confirmations and broadcasts from your own verified domain rather than a shared platform sender. DKIM is verified in-app, and the platform sender is there as a fallback while you set it up.

  • Managed sending domain per store, with DKIM verification built in
  • Open and click tracking toggled per domain
  • Suppression list and per-store unsubscribes handled for you
  • Falls back to the platform sender so nothing breaks mid-setup

// Operations

Accounting, payments and marketing.

The rest of your stack, on your own accounts. Sales flow to your books, payments land in your bank, and client events reach whatever marketing tool you've already standardized on.

QuickBooks Online

Sync clients, sales and invoices to your QuickBooks company so your accountant gets a clean ledger instead of a monthly re-keying job.

  • OAuth install — connect once, token refresh handled automatically
  • Client profiles sync two-way; sales and invoices push across
  • Account mapping so entries land in the accounts you actually use
  • Payments reconcile back from QuickBooks, and disconnecting is a clean single action

Authorize.Net

Take card payments on your invoices through your existing Authorize.Net merchant account. Funds settle directly to your bank — the platform never holds the money.

  • Hosted payment form — card details never touch our servers
  • Per-invoice payment-method picker, with an optional card surcharge line
  • Webhook plus a manual-sync fallback, so a missed callback never strands an invoice
  • Refund flow that automatically falls back to a void when the charge hasn't settled

Clover

A second gateway option for brokers already on Clover. Same invoice and pay-page flow, your own merchant account, with a webhook keeping payment status in step.

  • Connect your Clover merchant account from the payments settings page
  • Sandbox mode for testing before you flip it live
  • Webhook-verified payment updates against your invoices
  • Switch which gateway a store uses without rebuilding your invoices

Klaviyo (or any webhook)

Push client and sale events to Klaviyo for your own flows, or point a generic webhook at whatever else you run. Fan out to more than one destination per store.

  • Three events dispatched: client upserted, order placed, order refunded
  • Klaviyo native, plus a generic webhook destination for anything else
  • Multiple destinations per store — fire the same event to both
  • Every dispatch is logged, so you can audit what fired and what didn't

// Lead capture

Already have a site somewhere else?

You don't have to move it. These four are inquiry-form integrations: your existing site keeps serving your pages, and the enquiries it collects arrive here as clients with a follow-up task attached. If you'd rather run the whole site in one place, the built-in website builder does that too.

Shopify

Keep your Shopify site. Drop in the inquiry snippet and submissions arrive as clients in your CRM instead of as another email you have to copy out by hand.

  • A per-store connection key, minted in the dashboard
  • Theme snippet with copy-paste install instructions
  • Submissions match an existing client by email, or create a new one
  • A follow-up task is opened so somebody actually replies

WooCommerce

Same idea for self-hosted WordPress. Install instructions are written for the WordPress admin, and the form posts straight into your client list.

  • Per-store connection key with step-by-step WordPress instructions
  • Credentials tested from the dashboard before you rely on them
  • Email-based dedupe so a repeat enquiry doesn't create a duplicate
  • Optional tag on inbound submissions for later segmentation

Wix

Point your Wix site's enquiry form at your store and the submissions land in the CRM. No migration, no code on your side beyond the embed.

  • Per-store connection key and a hosted inquiry endpoint
  • Works alongside whatever Wix site you already run
  • Submissions create or update the client and open a follow-up task
  • Connection status visible in the dashboard

Squarespace

Same again for Squarespace. If your public site lives there and you'd rather not rebuild it, this is how the leads reach your pipeline.

  • Per-store connection key with setup instructions
  • Hosted inquiry form, so nothing brittle is injected into your theme
  • Leads land in the same client list as everything else
  • Swap to the built-in website builder later without losing the leads you already captured

// Build your own

Anything we don't connect, you can.

There's a documented REST API with store-scoped keys and a live OpenAPI spec, plus signed outbound webhooks for the events that matter. If the tool you need isn't on this page, that's the path — and tell us about it, because we prioritize what people actually ask for.

Plug in and stop double-entering.

Start free, connect what you already use, and clear the backlog you've been meaning to get to.