Separate the website from the connected experience
Web Spark creates the website. Supported Site Spark and Proof Pulse deployments supply their own visitor experiences. The source application remains responsible for its lead, consent, messaging and booking behavior. Installing a website component does not duplicate every CRM workflow inside Web Spark.
A connected product must be available, enabled and owned by the same workspace. Separate app subscriptions, source configuration and permissions may apply. The entire Work Mode plugin library is not a general-purpose Web Spark script library.
Prepare the source app first
- Open the intended Site Spark or Proof Pulse deployment.
- Confirm it belongs to the same business and workspace.
- Review its branding, destination, consent wording and supported action settings.
- Confirm the source is active and ready before returning to the website.
For Site Spark, distinguish an inquiry form, a conversation and a booking-related path. Do not label a service request “appointment confirmed” unless the connected workflow actually confirms it.
Bind the connection to the website
Open the website’s Connections management area. Select the supported source deployment and follow the displayed origin and approval requirements. An origin is the exact website address allowed to use the integration. A preview address and a future custom domain are not interchangeable.
For a domain change, complete the displayed domain and certificate review and approve the intended future address where the interface requires it. Use the exact address shown; do not add arbitrary wildcard origins or paste a third-party script into the brief.
Add and review the component
Use the available connection/component controls to place the supported experience on the page. Save the draft and verify that the selected connection matches the intended business. A private preview may not reproduce every public-origin behavior, so keep a public test in the launch checklist.
Changing a source deployment or its version can require a new website release. Inspect the preparation summary rather than assuming an old release automatically uses every later source change.
Test the complete path
After approved publication, open the real HTTPS domain on desktop and mobile. Check the component loads, links go to the correct destination and the public phone is correct. With the business’s permission, submit one clearly marked test inquiry using a contact you control. Be aware that a test can send messages or create real CRM records.
Confirm the result in the source application. A button click is not a delivered lead; a submitted lead is not a booking; a booking is not a completed job. Inspect each stage that the business actually uses.
If a connection disappears or is denied
Check workspace ownership, source status, entitlement and the exact live origin. A paused source, changed domain or expired hosting can affect serving. Do not create duplicate connections or relax security to hide the problem. Include the website and source deployment references in the support request, but never the secret keys.