Web person launch handoff
Use this packet when a website manager, freelancer, agency, or internal web person needs to install Porchlight or unblock launch.
What to send
Send one message with everything they need:
- The live website URL where Porchlight should appear.
- The CMS or website platform.
- The Porchlight snippet from Settings -> Launch.
- The org slug.
- Any customer-owned consult URL, such as
https://book.example.com/site-visit. - The launch date or deadline.
- The best contact for quick questions.
- Links to the widget install guide, widget not showing checklist, and CSP guide.
Copy-ready email
Subject: Add Porchlight to our website
Hi,
We are launching Porchlight for website consult intake. Please add the snippet below before the closing </body> tag on the live site, preferably site-wide.
[Paste Porchlight snippet here]
Please keep the script src, data-org, data-source, and async attributes unchanged. After publishing, clear any CMS or CDN cache and send us the live page URL where you tested it.
If the site has a Content Security Policy, please allow https://porchlight.cymbalabs.com for the script, frame, and connect directives.
After install, we will open the bubble, send a test message, and confirm the lead reaches the Porchlight Inbox.
Thanks.
Web-person checklist
- Paste the snippet before the closing
</body>tag. - Publish to the production site.
- Clear CMS, theme, plugin, and CDN cache.
- Confirm the snippet is not duplicated.
- Add CSP allow rules if the browser blocks Porchlight.
- Confirm the exact website host is saved in Porchlight Settings -> Branding.
- Open the bubble and send a test message.
- Confirm the Porchlight team sees the test in Inbox.
What not to do
- Do not change the org slug.
- Do not remove
async. - Do not put the script only on a preview page unless that is the agreed launch path.
- Do not iframe Porchlight manually. Use the snippet or hosted intake URL.
- Do not remove the customer's existing contact forms before the pilot is proven.
Send Porchlight this context
If the web person is blocked, open support and include:
- The web person's notes.
- The live page URL.
- The CMS or hosting provider.
- Any browser console error.
- Whether they changed CSP, cache, redirects, or DNS.