website widget

title: "Website Widget for Lead Generation" category: "Contractors" description: "Embed a scheduling widget on your website to receive job requests with date/time preferences"

Overview

The website widget lets you embed a job request form directly on your contractor website. Homeowners can submit requests without leaving your site, including their preferred date and time for the work. You'll receive notifications just like marketplace job requests. It's a simple way to turn website visitors into customers.

Setting Up Your Widget

Accessing Widget Settings

1. Go to Settings in your contractor dashboard
2. Click the "Website Widget" tab
3. Copy the embed code shown on the page and paste it into your website where you want the form to appear

Customizing Widget Colors

You can match the widget to your brand:

• Choose primary and accent colors in the widget settings
• Preview changes using the embedded preview on the settings page
• Save colors to update the embed script so all new widget loads reflect your brand

Widget Notification Email

By default widget submissions are sent to your company's contact email. You can override this with a dedicated widget notification email (for example: appointments@yourcompany.com) in the Website Widget settings so leads route to the right inbox for scheduling and follow-up.

SMS Consent & Evidence (New)

You can now enable company-specific SMS consent that appears on your embedded widget and is recorded as evidence when customers submit the form.

What to configure

• In Settings → Website Widget, open the "SMS Consent" section.
• Toggle "Enable SMS Consent" to require an opt-in checkbox on the widget.
• Enter the public HTTPS URLs for your Privacy Policy and Terms & Conditions. Both links are required when SMS consent is enabled.

What customers see

• When enabled, the widget shows a concise consent checkbox and disclosure text that includes:
  • The company name
  • A brief description of message types (inquiry, quotes, appointments, orders, deliveries, installations, and service)
  • Message frequency, data rates, STOP/HELP instructions, and that consent is not a condition of purchase
  • Links to your Privacy Policy and Terms & Conditions

Evidence captured

• When a visitor submits the widget and SMS consent is enabled, the system records consent evidence with:
  • accepted: whether the checkbox was checked
  • disclosure: the exact disclosure wording shown at submit time
  • phone: phone number provided (required to opt-in)
  • recordedAt: ISO timestamp of submission
  • privacyUrl and termsUrl: the URLs you configured
  • source: "WEBSITE_FORM"
• The recorded disclosure must match the live wording at submission. If the consent wording or company settings change, the form will reject mismatches and prompt the user to reload the form before resubmitting.

Important behaviors & validations

• If SMS consent is enabled, both Privacy Policy and Terms & Conditions URLs must be valid public HTTPS links.
• A visitor cannot opt into SMS without providing a phone number. If they check the consent box but provide no phone, submission will be rejected and the widget will request a phone or uncheck consent.
• If SMS consent settings are later disabled in your dashboard, previously captured evidence remains attached to the submission but the widget will no longer show the checkbox.
• The disclosure text is generated server-side from your company name and the two configured URLs; do not manually alter the widget's disclosure text in the embed.

Embedding the Widget

Copy the embed snippet from the Website Widget settings and paste it where you want the form to appear:

<!-- Example embed (automatically provided in settings) --> <div id="blueclerk-widget"></div> <script src="https://app.blueclerk.com/api/public/widget/script/[companyId]?form_location=blueclerk_embedded_widget"></script>

Notes:

• The embed script loads a branded, responsive form and applies your saved colors.
• If you enable SMS consent after embedding, visitors must load the page again to see the updated checkbox and disclosure wording.

Receiving & Working Leads

• Widget submissions create a lead/ ticket in BlueClerk with the same workflow as other inbound channels.
• If you configured a widget notification email, submissions are sent there; otherwise they go to your company's primary contact email.
• All captured consent evidence is stored with the lead/submission for compliance and auditing purposes.

Tips

• Make sure your Privacy Policy and Terms & Conditions pages are publicly accessible over HTTPS before enabling SMS consent.
• If you change either URL or your company name in Settings, expect the widget disclosure to change; users who loaded the older form may need to reload to resubmit.
• Route widget notifications to a shared inbox (appointments@ or leads@) if multiple team members handle scheduling.

Questions

Q: Do I need to enable SMS consent to send SMS from BlueClerk?
A: No. SMS consent on the widget only controls that specific website intake flow. You can still send transactional or campaign SMS through BlueClerk according to other consent rules and your own workflows; enabling widget SMS consent ensures explicit opt-in was collected for inbound web submissions.

Q: What happens if a visitor's recorded disclosure doesn't match the current wording?
A: For security and legal consistency the submission will be rejected and the visitor will be asked to reload the form. The system verifies the disclosure text at submit time to ensure what was shown matches what is stored.

Q: Where is consent evidence stored?
A: Consent evidence is attached to the lead/submission record generated by the widget and is available in the lead/ticket details for review and auditing.