Keelson integrations: YachtWorld, Boat Trader, HubSpot, Salesforce, Lightspeed, DockMaster and your calendar

Keelson integrations at a glance: what flows in and what flows out

Leads flow into Keelson; conversations, appointments and outcomes flow out to your CRM, DMS and calendars. Keelson does not replace any of these systems. It answers the lead, qualifies the buyer and books the appointment, then writes the result where your team already works.

Lead sources: marketplaces, website forms, ads, OEM portals and shows

Every lead source reaches Keelson by one of two paths: a lead email or a form webhook. Marketplaces and OEM portals typically deliver each new inquiry to a dealer email address, and many lead providers can send it in the ADF/XML format that dealer CRMs read. Adding Keelson usually means adding one forwarding address to that delivery, so your CRM keeps receiving the lead exactly as it does today.

• YachtWorld, Boat Trader and boats.com. Keelson works from the lead email and replies from your number and domain, never through marketplace messaging. Our YachtWorld and Boat Trader lead guide covers how those leads are delivered and what they cost.
• YATCO and BoatWizard. Brokerages route buyer inquiries from these platforms the same way; see Keelson for yacht brokers for how inquiries map to individual brokers.
• Website forms. Gravity Forms, HubSpot, Webflow and Shopify forms post to Keelson by webhook or send a notification email. The form's consent wording is captured with the lead.
• OEM lead portals. Manufacturer leads assigned to your rooftop arrive by the portal's notification email.
• Meta Lead Ads and Google lead forms. Ad leads go to Keelson as they are submitted, rather than waiting for someone to download them from the ads manager.
• Boat-show scans. Scanned contacts load after the show for re-engagement; the boat show follow-up guide covers the cadence.
• CallRail. Tracked calls and form fills become lead records Keelson follows up by text and email. Keelson does not answer or place voice calls.

If you already use Boats Group's LeadFlow, which the 2024 Boats Group Advantage booklet describes as importing marketplace leads into a dealer CRM, keep it. LeadFlow moves the lead; Keelson answers it. During setup we pick one intake path per source so each buyer gets one reply, not two.

CRM and DMS sync: HubSpot, Salesforce, Lightspeed and DockMaster

Your CRM or DMS stays the system of record, and Keelson writes each lead's story back to it. What goes back is the lead itself with its source, the conversation, the qualification answers (budget, timeline, trade-in, financing need, experience, intended use, home water), any appointment booked and the outcome: booked, handed to a salesperson, opted out or still in follow-up.

Exactly which records and fields are written is agreed per system during setup, because every dealer configures HubSpot, Salesforce, Lightspeed and DockMaster differently. We do not publish a fixed field map, and we will not promise a mapping before we have seen your configuration. Deals, F&I, service, parts and accounting stay in your DMS; Keelson does not touch them. Choosing a system in the first place is covered in our boat dealer CRM comparison.

Calendars: booking into Google Calendar and Outlook

Keelson books showroom visits, sea trials and video walkthroughs straight into the salesperson's Google Calendar or Outlook. During setup each salesperson's calendar is connected, and you tell us the booking rules: how long each appointment type runs, when sea trials can happen, and which salespeople take which leads.

• Keelson books into open times on the connected calendar.
• The appointment appears on the salesperson's calendar with the buyer's details.
• Confirmations and reminders go to the buyer from your number and email domain.
• Reschedules and cancellations are reflected in the salesperson's calendar.

The sea trial scheduling guide covers the confirmation, reminder and weather-hold sequence those calendar events drive.

Sending: your number, your email domain, your 10DLC campaign

Every message goes out in the dealership's name from its own number and email domain. Buyers see your dealership, not Keelson and not a marketplace, and their replies come back into the same thread your salespeople see on their phones.

• Text. Each rooftop sends on its own registered 10DLC campaign. Consent is captured at the lead source and logged, quiet hours follow the buyer's time zone, and STOP and other opt-out keywords are honoured immediately. The texting compliance guide explains the rules; it is general information, not legal advice.
• Email. Replies come from your dealership's email domain, set up with the DNS records your IT person or web host adds during setup.
• Takeover. A salesperson can take over any conversation from a phone and hand it back when done; Keelson then picks the follow-up cadence back up.

Setup steps and timing: two to three weeks, gated by 10DLC

Most rooftops are live within two to three weeks, and the 10DLC campaign is the longest step. Carrier registration runs on the carriers' timeline, so we file it on day one and do everything else in parallel.

1. Day one: 10DLC. We file the brand and campaign registration in the dealership's legal name, with the opt-in wording from your lead sources.
2. Lead sources. Add the Keelson forwarding address to marketplace and OEM lead email, and connect website, Meta and Google forms by webhook.
3. Inventory feed and policy. Connect the inventory feed and approve the policy Keelson may quote: hours, sea trial and deposit rules, delivery areas.
4. Calendars and routing. Salespeople connect Google Calendar or Outlook; you set appointment types and which salesperson takes which leads.
5. CRM or DMS. Connect HubSpot, Salesforce, Lightspeed or DockMaster and agree what is written back.
6. Persona and templates. Review the dealership's voice and the message templates before anything goes to a buyer.
7. Test and go live. Send test leads end to end, check the CRM record and calendar event, then switch on when the campaign is approved.

Full plan detail is on Keelson pricing. Multi-rooftop groups run the same steps per rooftop, with each rooftop's data kept separate.

Systems not listed: ADF/XML, webhooks and what to ask on a demo

If your system is not named on this page, it can usually still connect through lead email or a webhook. ADF/XML lead email is a long-standing dealer lead format that many providers and CRMs support, and a form webhook covers most website builders. Those two paths handle intake for most sources a dealer uses.

Writing back to a CRM or DMS we do not list, such as IDS Astra, Winboats, DealerRock or BiT, is a different question, and we will not claim a connection we have not built. Bring the system name to a demo and we will tell you plainly what works today, what would need a workaround such as emailing a summary to a shared inbox, and what we cannot do yet.

Frequently asked questions