Keep your LOS and AMS, and work every Lead around them

• The consent certificate stored on the Lead as evidence before the first message goes out
• Leads delivered to the Botsplash intake endpoint with source and campaign
• Botsplash CRM routing can require the certificate before a Lead is offered

How it connects: LeadConduit delivery to the Botsplash receiver URL; certificate field mapped to the Lead.

• The identity token captured with the Lead and kept as consent evidence
• Botsplash CRM can require the token before outreach and show it to the owner on the Lead
• Lead quality signals available to routing and scoring rules

How it connects: Token captured on your form or by your lead source and mapped to the Lead.

• Leads posted in real time to the Botsplash intake endpoint; the clock starts on arrival
• Source and campaign on the Lead for source-to-funded reporting
• A returning borrower becomes a new Lead on the existing Contact, not a duplicate

How it connects: Receiver URL per lead source; the marketplace representative turns delivery on.

• Pricing scenarios pulled into the conversation so a loan officer answers a rate question from the record
• The quoted scenario stored on the Lead in Botsplash CRM
• Rate-watch signals can open a recapture Lead when a scenario improves

How it connects: Pricing engine credentials per workspace; products and scenarios confirmed per setup.

• A built-in channel: Messenger threads in the same inbox as SMS and chat
• Consent captured per channel and the thread kept on the Contact
• A Messenger inquiry becomes a Lead with its source in Botsplash CRM

How it connects: Connect your Facebook Page from the Botsplash channel settings.

• A built-in channel: Instagram DMs in the shared inbox
• The thread on the Contact, with consent per channel
• An Instagram inquiry becomes a Lead with its source in Botsplash CRM

How it connects: Connect the Instagram business account from the Botsplash channel settings.

• A built-in channel: WhatsApp in the shared inbox, templates for the first message
• Consent per channel and the thread on the Contact
• A WhatsApp conversation lands on the Lead in Botsplash CRM

How it connects: WhatsApp Business account connected through Botsplash.

• Sign in with Google for your team
• BookMe reads calendar availability and writes bookings back
• Gmail stays your mailbox; Botsplash does not replace it

How it connects: Google sign-in and calendar access granted by each user.

• Sign in with Microsoft for your team
• BookMe reads Outlook calendar availability and writes bookings back
• Outlook stays your mailbox; Botsplash does not replace it

How it connects: Microsoft sign-in and calendar access granted by each user.

• Single sign-on for agents and admins
• Users provisioned and their state-licensing attributes updated through the Botsplash API
• Role and workspace access aligned with your identity groups

How it connects: A SAML or OpenID Connect app in Okta; provisioning through the API.

• Calls stay on the contact-center platform; Botsplash carries the text and chat conversations
• Numbers, dispositions and suppression exchanged as Botsplash CRM workflow steps
• The conversation and the call land on the same Contact

How it connects: API-based; the exchange is confirmed per setup.

• DNC status synced into Botsplash so a flagged number is visible before outreach
• Suppression applied as a Botsplash CRM workflow step on the Lead
• Scrub results kept on the record for your compliance team

How it connects: Account connection; scrub schedule agreed per setup.

• Botsplash events (conversation started, lead qualified, consent changed) trigger or suppress Iterable campaigns
• A STOP in Botsplash reaches the campaign tool
• Campaign attribution carried onto the Lead in Botsplash CRM

How it connects: Iterable API key and an event mapping.

• Triggers on new lead, new conversation and consent change
• Actions to create a Lead or send a message
• Botsplash CRM upserts by identity, so a zap never creates a duplicate Contact

How it connects: Botsplash app in Zapier.

• Chat started and lead captured sent as analytics events
• Landing page and campaign parameters captured on the Lead in Botsplash CRM
• Source-to-funded reporting that starts at the click

How it connects: Measurement ID in the chat widget settings.

• The chat widget on every page through a plugin or script
• Site forms posted to Botsplash so a form fill becomes a Lead with its page and campaign
• Routing by the page the visitor was on

How it connects: Plugin or a script tag; form fields mapped to the Lead.

• The chat widget on every page through a script tag
• Site forms posted to Botsplash so a form fill becomes a Lead with its page and campaign
• Routing by the page the visitor was on

How it connects: Script tag; form fields mapped to the Lead.