Applying the web chat component of a Blueprint created a second widget in the target account, named like the source account's widget. Both widgets are active as triggers. Every target account already runs its own widget on its website, so after every apply a second active widget with a foreign name has to be found and handled by hand.

Request: let the web chat component update the target account's existing widget instead of creating a new one, or at least let us choose the widget in the apply dialog and warn before a new one is created.

Impact: Blueprints can roll out web chat settings without manual clean-up in every account.