Once the virtual agent is enabled on a channel that previously used JSM chat, all the JSM chat capabilities are lost.

For example: A valid JSM chat configuration would be to allow for several request types to be available and once a request is created a dropdown with request types are displayed to help seekers so they can chose one and then fill up the request for.

When VA is enabled, the default request type configured in the VA is used instead.
This is the case even when no intent matched or AI answer is found.

The VA should in those cases be able to be configured so it falls back to jsm chat's configuration.