DealSplash for your CRM

1.What this adds to your CRM

DealSplash is a curated, brand-safe customer-acquisition channel that lives inside the CRM you already operate for each client. Install it on a client account and three things happen automatically:

• A two-stage DealSplash sales pipeline is provisioned in the client's CRM (Purchased → Redeemed).
• Four opportunity custom fields are created (Redemption Code, Expiry Date, Deal Page, Pricing Option).
• The client account is wired to receive native Contacts and Opportunities for every purchase, refund, and voucher redemption — in real time, with no Zaps, spreadsheets, or scheduled imports.

There is no parallel customer database to reconcile later. The CRM stays the source of truth.

DealSplash itself is a curated marketplace for limited-time local-business offers. Customers buy a voucher online and redeem it in person at the merchant. The integration brings every step of that lifecycle — payment, refund, in-person redemption — back into the CRM as records your existing automations already understand.

2.How install works

Install is one click, run once for each client account you want to connect. Start from Settings → Integrations in DealSplash and click Connect LeadConnector, or from the LeadConnector marketplace — both end at the same screen.

1. When LeadConnector asks where to install, choose the client account you want to install on — the individual business, not the top-level company view. If you install from the top-level company view instead, DealSplash finds the client accounts the app was installed on: with one, it connects straight through; with several, it asks you to pick.
2. Approve the OAuth scopes on the consent screen. DealSplash requests only what the integration needs to do its job — read and write Contacts, read and write Opportunities, read account metadata, write custom fields, and write to the conversation feed (without sending outbound messages).
3. We auto-create the two-stage DealSplash pipeline and four opportunity custom fields. This step is idempotent — reconnecting later never duplicates them.
4. The business signs in to DealSplash, connects Stripe so payouts route correctly, and publishes a first deal. Deal design is white-glove — handled by DealSplash with the business directly.
5. Connected more than one client account? The first one becomes the account default. Each deal syncs there unless you open the deal’s Settings → Contacts and choose a different client account for it.

If the pipeline detection step fails (rare — a name clash with a pre-existing pipeline), you'll see a one-step recovery prompt on the integration card with a link back into the CRM's pipeline editor. Fix it once and the integration finishes connecting.

3.What happens on first deal publish

A deal goes live on dealsplash.io as a public, curated listing. DealSplash handles deal design, photography, copy, and presentation; the business approves the live version before publication.

From that moment forward:

• Customers discover the deal on dealsplash.io and buy through Stripe checkout.
• Payouts route to the business through Stripe Connect — DealSplash never holds the funds.
• Each purchase generates a digital voucher delivered as an email and an Apple/Google wallet pass.
• The customer redeems in person at the business, on the date(s) the offer is valid.

Every step of that lifecycle writes back to the CRM, described next.

4.Your own domain for deal pages

A deal's link starts on dealsplash.io. Deal Settings → Domain connects a domain — yours or your client's — and from then on the deal's link, its share buttons and its social images use that address instead.

Use a subdomain. The panel starts you on one: a deals label sits in front of the domain you type, so the result is deals.yourclient.com. That shape costs one CNAME record, on that label alone, at the registrar — nothing on the root moves, and the site already living at yourclient.com keeps serving exactly as it does. Your site builder's own domain guide gives the same advice: when the root already carries a site you want to keep, give the new product a subdomain of its own.

The root is a choice, not the default. "Use the root domain instead" switches the field to the bare domain. Connecting the root replaces the records yourclient.com already has — a root A record and a www CNAME — so a site living there goes dark until it is moved. The panel says so before you connect. Pick it only for a domain with nothing else on it.

Either way, the panel shows the exact record to add once you connect, and keeps checking until the domain is live.

5.How records flow to the CRM

Three lifecycle events trigger writes into the client account the deal routes to: purchase, redemption, and refund.

4.1 On purchase

1. Upsert contact by email. Name, email, and source (DealSplash) are set, and these tags are attached: DealSplash, ds:purchased, DealSplash: <deal title>, deal:<slug>, option:<pricing-key>, purchased:<YYYY-MM-DD>.
2. Create a purchase note on the contact: deal title, business name, pricing option, redemption code, voucher expiry, Stripe payment link, wallet-pass link, public receipt link.
3. Create an opportunity in the DealSplash pipeline at the Purchased stage. Name format: <Deal title> — <Business name>. Monetary value equals the purchase amount. The four custom fields from §1 are populated.
4. Log an inbound conversation message on the customer's conversation feed. This records the event without sending any outbound SMS or email to the customer.

4.2 On redemption

• Adds a redemption note describing when and how the voucher was redeemed.
• Adds the ds:redeemed tag.
• Moves the opportunity from Purchased to the Redeemed stage. Opportunity status stays won — it is a completed sale, now delivered.

4.3 On refund

• Full refund. Adds the ds:refunded tag, removes ds:purchased, transitions the opportunity status to lost, and adds a refund note with the Stripe refund link.
• Partial refund. The contact keeps both ds:purchased and ds:refunded tags (the voucher is still partly valid). The opportunity is unchanged. A note records the refund amount for reference.

4.4 Automations you can drive from this

The tags and status transitions are designed for downstream automation. A few examples:

6.Brand-safe by design

The mass-market deals platforms attract bargain-hunters and dilute the businesses listed on them. DealSplash is the opposite shape:

• Curated, not crowded. A small selection of offers at any given time. Every business is personally vetted before being invited onto the marketplace.
• White-glove deal design. DealSplash works with the business to design the offer and the page. Photography, copy, and presentation are handled to the same standard as the rest of the marketplace — no race-to-the-bottom coupon styling.
• No fine print. Price shown is price paid. No service fees, no hidden charges, no surprise expirations.
• Local-first. Independent neighborhood businesses only. No chains, no franchises.

For the business, the channel reads as a brand-additive promotion — not a discount platform. For the CRM operator, the data shape is identical to any other native customer interaction.

7.Frequently asked questions