When you connect your JSM domain to your eesel AI bot, it will automatically index your canned replies and add them to your AI bot.
Go to your eesel dashboard and unfurl the JSM integration on the left sidebar
Click Sources
Click Canned Replies
Set them live or as drafts to enable or disable them.
Click re-sync to update them after any changes in JSM.
Note: if your canned replies haven't been added, reach out to support.
Past Issues
Training on past issues requires you to connect your Jira to the bot you want to train. Once that's done, click on your Jira integration on the left sidebar > Click 'Sources' > 'Issues'.
We recommend filtering your tickets using the query in order to get the best quality results.
Create a JSM AI Agent
eesel can automate your frontline support as an AI agent inside JSM. You can have it leave internal notes, automatically reply, and triage tickets. Once your AI has been trained and customized, it's time to link your JSM domain to your AI bot. To set up eesel as an AI agent inside JSM, see our AI Agent guide.
Create a JSM AI Copilot
Check out our setup guide for using AI Copilot in your JSM. eesel AI can act as an AI copilot for your JSM by using our browser extension.
The AI can automatically pick up on the content of a ticket, and generate a response based on the knowledge it has access to.
You can use the browser extension to select the bot you want to use for its answer, and then draft a response and chat with the bot to edit before you paste is as a reply.
JSM Actions
Once you've trained the bot and integrated it with JSM, it's important to customize it and add actions so that you can get the most out of your AI and automate manual tasks. The following are JSM specific actions. You can use them in combination with other actions on different platforms as well.
Create issue
jira_create_issue
Purpose: File a Jira issue.
Key Params:project_key, summary, description
When/How to Use: Primarily used for reporting bugs or suggesting improvements that need engineering or product team attention tracked in Jira. You must instruct the AI to identify these scenarios and gather the necessary information. Define the default project_key to use.
Example Prompt Instruction:
If you are unable to help the user with their enquiry OR it appears that they are reporting a bug or suggesting a product improvement, you must offer to create an issue for the user in our engineering tracking system (Jira). If they accept, collect a brief summary of the issue and a more detailed description. Then, call jira_create_issue with project_key set to 'ENG', using the collected information for the summary and description parameters.
Label issue
jira_label_issue
Purpose: Adds labels to a Jira issue.
Key Params:issue_key: str, labels: List[str]
When/How to Use: Use this after a Jira issue has been created or identified (e.g., using jira_create_issue or jira_search_issue) to add relevant labels for categorization and filtering within Jira. You need the issue key and the list of labels.
Example Prompt Instruction:
After successfully creating a Jira issue using jira_create_issue (and obtaining the issue key from the tool's response), analyze the user's report for key topics (e.g., 'login', 'performance'). Call jira_label_issue using the new issue_key and a list of relevant labels, e.g., labels=['bug', 'reported-by-customer', 'severity-medium'].
Search issue
jira_search_issue
Purpose: Searches for Jira issues using JQL.
Key Params:jql: str
When/How to Use: Use this when a user asks about the status of a known bug, feature request, or project item that is tracked in Jira. You must formulate a JQL query string based on the user's keywords or the issue they are referencing.
Example Prompt Instruction:
If the user asks about the status of a bug they previously reported, or asks if a known issue is fixed (and mentions keywords related to it), formulate a JQL query to search for the issue in Jira. Call jira_search_issue with the parameter jql='summary ~ "[Keywords from user query]" AND project = ENG ORDER BY created DESC'. Present the search results to the user, focusing on the issue key, summary, and status.
Assign issue (escalation)
jira_assign_issue
Purpose: Assigns an existing issue in Jira to a specific user.
When/How to Use: Use this to assign an existing Jira issue (identified by its key) to a specific team member or group within Jira, using their Jira account ID. This is useful for routing issues found via search or created by the AI to the correct owner.
Example Prompt Instruction:
If the user is reporting a front-end issue and you have found or created the relevant Jira ticket (issue key available), you should assign it to the front-end lead. Call jira_assign_issue with the issue_key and the parameter assignee_account_id='[Front-end Lead Jira Account ID]'.
Comment on issue
jira_comment_on_issue
Purpose: Adds a comment to an existing issue in Jira.
Key Params:issue_key: str, comment: str
When/How to Use: Use this to add context from the customer conversation directly to the related Jira issue. This is useful for providing engineers with additional details, clarifying user impact, or adding follow-up information. You need the issue key and the content of the comment.
Example Prompt Instruction:
If a user provides important additional details or context about a bug or feature request after the Jira issue has been created, call jira_comment_on_issue using the relevant issue_key. Set the comment parameter to summarize the new information provided by the user.
Comment on issue
jira_comment_on_issuePurpose: Adds a comment to an existing issue in Jira.
Key Params:
issue_key: str, comment: strWhen/How to Use: Use this to add context from the customer conversation directly to the related Jira issue. This is useful for providing engineers with additional details, clarifying user impact, or adding follow-up information. You need the issue key and the content of the comment.
Example Prompt Instruction: