Skip to main content
Open Products → Web Chat. The page appears when Web Chat settings are enabled and your role has access to them.

​
Website Widget

Use Website Widget for the chat launcher installed on your website.
  1. Turn on the widget only when its configuration and installation are ready.
  2. Choose the widget theme color and the correct country, United States or Canada.
  3. If enabled, configure Validate service area and write the message shown for an unsupported ZIP or postal code.
  4. Configure schedule negotiation and booking-window availability only when the team’s booking setup is ready.
  5. For ServiceTitan teams, enable schedule-window or job-creation behavior only after the CRM connection, catalog mappings, and booking test are complete.
  6. Review the available notification actions: send texts, send emails, create ServiceTitan jobs, trigger emergency handling, and email recipients.
  7. Save the settings.
These switches control different actions. For example, Send emails does not create a ServiceTitan job, and Create ServiceTitan jobs does not by itself guarantee a recipient receives an alert.

​
Install the widget

Copy the installation snippet generated by the dashboard and add it before the closing body tag on the website. Use the optional snippet only for the behavior described beside it. After deployment:
  1. Confirm the script loads on the intended production pages.
  2. Open and close the launcher on desktop and mobile.
  3. Test one valid and one invalid service area.
  4. Test an in-hours and out-of-hours scheduling request.
  5. Verify the configured email, text, emergency, and CRM actions.
Enabling Web Chat in Avoca does not install it on your website. Likewise, leaving an old snippet in the site can keep loading the experience after a dashboard change. Coordinate dashboard and website releases.

​
Hosted Chat Page and Embedded Chat

Hosted Chat Page and Embedded Chat appear only when that Web Chat rollout is enabled for the team.
  • Use Hosted Chat Page to configure the branded full-page experience and its copy, colors, contact details, and generated URL.
  • Use Embedded Chat to configure a chat experience placed inside a page and copy the generated embed snippet.
Save branding changes before copying a URL or snippet so the deployed experience matches the current preview. Do not construct chat URLs or installation code by hand; use the values generated for the selected team.