Getting started

Overview

What RemixCRM is, who it’s for, and how this documentation is organized.

What RemixCRM is

RemixCRM is a multi-tenant booking platform built specifically for DJ and entertainment businesses. It handles the full workflow from first inquiry to final payment:

  • Lead capture — embed forms on your site, sync from Calendly, or POST via the Lead API
  • Client database — multi-phone, multi-email contacts with full history
  • Event management — calendar, packages, add-ons, equipment assignments, staff
  • Contracts — template editor, merge variables, in-app e-signatures
  • Invoicing & payments — Square or Stripe Checkout, plus Venmo/Zelle manual confirm
  • Communication — transactional email (Resend or your own SMTP) and SMS (Twilio)
  • Marketing — auto-sync new clients to Mailchimp or Constant Contact
  • Automation — outbound webhooks fire on every important event (Zapier, n8n, custom)

Who it's for

DJs, entertainment companies, and small event-services teams who want a single source of truth instead of stitching together five different SaaS tools. Most setup decisions default to "sensible," but every integration is opt-in and configured per-organization.

How these docs are organized

The left sidebar groups topics by category:

  • Getting started — sign up, first event, first contract, first payment
  • Payments — Square, Stripe, Venmo & Zelle, the public pay page
  • Communication — SMTP, Twilio SMS, Zoom
  • Email marketing — Mailchimp, Constant Contact
  • Scheduling — Google Calendar, Calendly, blackout dates
  • Automation — outbound webhooks for Zapier / n8n / custom workflows
  • API & webhooks — public REST endpoints
  • Operations — error reporting, uptime monitoring, etc.

Every integration page follows the same structure:

  1. What it does — one paragraph
  2. Setup — exact steps with screenshots/links to the third-party dashboard
  3. How RemixCRM uses it — which features call it and when
  4. Troubleshooting — common errors and fixes

A note on tenancy

RemixCRM is multi-tenant from day one. Every piece of data is scoped to an organization (org_id). When you sign up, you create an org; team members are invited as members of that org. Integration credentials are stored per-org — two organizations can use completely different Stripe accounts, Twilio numbers, Mailchimp audiences, etc.

If you're integrating with RemixCRM (Lead API, webhooks), every call is scoped to a single org via an API key or webhook URL that you generate inside that org's settings.