Because the first install is usually straight to production. It appears on every page including the ones it should not, with default styling, in front of real customers.
Installation adds the widget to your site with a single script tag, or through your tag manager.
The snippet takes an environment, so it can run on staging or behind a preview flag first. Page rules and styling are set before it is enabled for real traffic.
The widget is installed on staging, checked against the real site, its page rules set, and only then switched on for production traffic.
It will not need a developer for changes. Styling, rules and hours are configuration, so only the initial snippet is a code change.
It loads asynchronously and does not block rendering; the assistant's knowledge is fetched on first interaction rather than on page load.
It loads asynchronously and defers its payload until first use.
Yes, with the same environment control.
The domains to allow are listed in setup.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.