Issue Summary

When using a Rovo custom agent, JSM ticket creation works as expected within the Rovo chat interface but fails when initiated from Slack. In Slack, the Rovo agent correctly interprets the intent to create a JSM ticket; however, instead of proceeding with ticket creation, it incorrectly requests authorization without providing any actionable way for the user to authorize.

Steps to Reproduce

1. In a Slack channel, invoke the Rovo agent.
2. Provide a prompt requesting the creation of a JSM ticket, including the keyword “escalate.”

Expected Results

The agent should invoke the JSM ticket creation skill and proceed to create the ticket directly from Slack, or clearly present an authorization flow (e.g., link/button) that, once completed, allows the ticket to be created successfully.

Actual Results

• The agent acknowledges the request (e.g., “I can help with that…”).
• The agent then states it needs authorization, but no link, button, or mechanism is provided for the user to complete authorization, and the ticket is not created.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available