Docs

Help desk / Teach the agent

Service Catalog (Experimental)

Import request types from Jira Service Management or service items from Freshservice, so employees can request them in chat and Risotto files the request for them

Let employees request services from your Jira Service Management or Freshservice catalog, directly in chat. Risotto collects the request form and files the request in your ITSM for the employee.

What is it

Your service catalog already lives in your ITSM: request types such as "New laptop", "Hardware refresh", or "Onboard a new hire", each with its own form. Service Catalog brings those items into Risotto so employees can request them where they already work.

  • You import the items from your ITSM. Risotto copies each item's name, description, and form.
  • Employees request an item in chat. Risotto asks the form questions.
  • Risotto files the request in your ITSM, on behalf of the employee. If Risotto cannot collect an item's form, it sends the employee to the item's page in your ITSM portal instead. See Items requested in the source portal.

Your ITSM stays the system of record. Fulfillment, approvals, and status updates continue to happen there.

You find Service Catalog at Settings > Service Catalog. You must have permission to manage the organization to import, edit, turn on, or delete items.

The list shows each item's Name (with the logo of the system it came from), Description, Department, the form it Collects (a dash means it collects nothing), and an Enabled switch. Use Filter by name to find an item.

What's supported

SourceWhat you importRequirements
Jira Service ManagementRequest types, including their ProForma formsJira connected through the Risotto Forge app
FreshserviceService catalog itemsFreshservice connected with an organization-level API key

If a source is not connected, the import dialog shows "Source is not connected." on its tab. The same message shows when a connected source refuses access to its catalog, for example when the Jira site does not have Jira Service Management.

If the source is connected but refuses to list its catalog, the dialog shows an error instead:

  • Jira: "Jira refused access to its service desks." Check that Jira Service Management is active on the site, and that the Risotto app can see the service desk projects you want to import.
  • Freshservice: "Freshservice refused access to its service catalog." Check that the agent who owns the API key can view the service catalog.

Supported field types

Field typeJiraFreshservice
Short textYesYes
Paragraph textYesYes
EmailYesYes
URL—Yes
NumberYesYes (number and decimal)
DateYesYes
Date and timeYesYes
Dropdown / single choiceYesYes
Multiple choiceYesYes
Checkbox—Yes (shown as a Yes / No choice)

Importing items

  1. Open the import dialog

    Go to Settings > Service Catalog and click Import.

  2. Choose a source

    Select the Jira or Freshservice tab. The dialog opens on the first source that is connected.

  3. Choose a service desk or category

    Click a service desk (Jira) or a category (Freshservice). You can search the list. If your Freshservice account has more than one workspace, each category shows as Workspace / Category.

  4. Select a department

    In Department, select the team that owns the items. Every item in one import gets the same department. To import items for another department, run the import again.

  5. Select the items

    Select the items to import, or click Select all. Click Clear to start over. Freshservice items that are still drafts are not listed.

  6. Import

    Click Import N items. The button is available when you have selected a department and at least one item. To pick another service desk or category, click Back.

  7. Review the results

    Read the result for each item, then click Done.

Each item gets one of these results:

  • Imported: the item was added, turned off. The result shows how many fields Risotto imported, for example "4 fields imported." Under Not imported:, it lists each field that it could not bring across, with the reason. If no form questions came across, the result says "No form — this item collects nothing." If the item imported as a portal item, the result says "This form has fields that Risotto does not support yet. Requestors will get a link to this item in the source portal."
  • Skipped: "Already imported.", or "A catalog item named '...' already exists." Item names must be unique in Risotto, so two service desks that each have an "Access request" cannot both be imported under that name.
  • Failed: the item uses something Risotto does not support yet and has no page in the source portal, with the reason (see What is not supported yet). Other reasons are "Could not read this request type from the source system." and "No longer available in the source system."

Display-only text blocks on a form, such as instructions or notes, are not questions. Risotto does not import them and lists them under Not imported: with the reason "Display-only content, not an input." The block's text shows as the field name, so it can contain raw HTML. If an item has only display-only blocks, it imports with no form. If a block has guidance that employees must see, add it to the item's Description or Form description.

Find items that are not imported yet

The import dialog does not mark the items that you already imported. To find and import the items that are missing, open Import, select a service desk or category, click Select all, and import. Risotto skips the items that you already have, imports the new items turned off, and shows the reason for each item that fails.

Items requested in the source portal

Some items use a form that Risotto cannot collect, for example a form with conditional logic, a Freshservice bundle, or a Freshservice field type that Risotto does not support. If the item has a page in the source portal, Risotto imports it as a portal item instead of failing it. Risotto files nothing for a portal item. It sends the employee a link to the item's page in your Jira or Freshservice portal, and the employee submits the request there.

  • In the item list, the Collects column shows In Jira portal or In Freshservice portal for a portal item. Hover it to see why the form could not be imported.
  • If the item has no page in the source portal, the import fails with the reason.
  • If you import a portal item again after you change its form in your ITSM, Risotto reads the form again. When Risotto now supports the form, the item switches to a Risotto form and keeps its name, description, department, and enabled state. Otherwise, the import skips the item and shows the reason.

Enabling an item

  1. Open the item

    In Settings > Service Catalog, click the item's row. You can also click the item's ⋮ menu and then Edit. The Edit service dialog opens.

  2. Review the details

    Check the Name, Description, Form description, and Department (see the list below).

  3. Turn on Enabled

    Turn on Enabled.

  4. Save

    Click Save. Risotto shows "Service catalog item updated".

To turn an item on or off without opening it, use the switch in the list's Enabled column. Risotto shows "'Name' is now available" or "'Name' is turned off".

In the Edit service dialog, you can change:

  • Name: what employees see. This does not rename the item in your ITSM. Two items cannot have the same name.
  • Description: what the item is for. Risotto uses the name and description to match employee requests to the item, so write it in the words employees use (for example, "Replace a broken or slow laptop").
  • Form description: the intro text that requesters see above the form's fields in Slack or Teams. This box shows only when the item has a form. The import fills it with the item's description from your ITSM. After that, changing the item's Description does not change the form description.
  • Department: the team that owns the service.
  • Enabled: turns the item on or off everywhere.

The Imported from box shows the system and the service desk or category the item came from, with an Open in Source link when Risotto has one. It also says which form the item collects before filing, or that it collects nothing.

You cannot edit the form questions in Risotto, only the form description. The questions must match the item in your ITSM, or the request will not file.

What happens when you enable an item

When an item is enabled:

  • The Risotto agent can find it and offer it during a conversation. Employees do not need to know the item's exact name. The agent matches the request against each item's name and description, so a clear description in the words employees use is what makes an item easy to find. For example, "I need a new laptop" matches "Hardware refresh".
  • A request phrased as a question is still a request. When an employee asks how to get something that IT or another team must provide, set up, or change, for example a new monitor or an address added to an email allow list, the agent searches your enabled items before it searches the knowledge base. A request to sign in to an app still goes to access requests first, and steps that employees can follow on their own still come from the knowledge base.
  • If a knowledge base answer tells the employee to request something through the Service Catalog or a request form, the agent searches your enabled items for it. On a match, it offers to file the item. On no match, it keeps the knowledge base answer and its link.
  • If an employee asks for access to an app that has no access rule, the agent also searches your enabled items before it searches the knowledge base. This does not apply to requests to remove access.
  • In Slack, the item appears in the Service list of the Start a new request form in the Risotto App Home, under its department.

When an item is disabled, it is not available anywhere. Leave an item disabled if employees should not be offered it.

Deleting an item

Click the item's ⋮ menu, click Delete, and confirm. Deleting removes the service from Risotto only. The request type or service item in your ITSM is not changed, and you can import it again.

What happens when employees request an item

In a chat conversation

  1. The employee describes what they need, or asks "what can I request?".
  2. The agent searches the enabled items and confirms which one the employee wants.
  3. The agent collects the form:
    • In Slack or Teams, the agent posts an interactive form when the form allows it.
    • In other cases, the agent asks for the fields one at a time in the conversation.
  4. Risotto checks that all required fields have answers, then files the request in your ITSM on behalf of the employee.
  5. The agent replies with the request key and a link, for example:

    :inbox_tray: I filed HR-1234 for your New laptop. You will get email updates about it — please follow it there.

  6. Risotto resolves the Risotto ticket. All follow-up happens in your ITSM.

For a portal item, the agent asks for no details and files nothing. It replies with a link to the item's portal page, for example:

:link: New laptop can be submitted in the Freshservice portal: open the request form.

Risotto then resolves the Risotto ticket.

From the Slack App Home

  1. The employee opens the Risotto App Home and clicks Start a new request.
  2. The employee selects an Associated department. If the department has enabled items, an optional Service list appears. Leaving it empty keeps the usual Description box.
  3. The employee selects a service. The item's form replaces the Description and Attachments fields. An item with no form shows "Name needs no further details. Press Create to send the request."
  4. The employee fills in the form and clicks Create.
  5. Risotto files the request and replies in the employee's direct message thread with the request key and link. Then it resolves the Risotto ticket.

For a portal item, the form shows an Open in Jira or Open in Freshservice button instead of the item's fields. Risotto does not file the request, and the employee submits it in the portal. If the employee clicks Create, Risotto shows an error on the Service field and creates nothing.

Who the request is filed for

Risotto files the request on behalf of the employee, so the employee can see and follow it in your ITSM portal and receives its email updates. The employee's ticket must have an email address. If it does not, Risotto does not file the request and escalates the ticket.

  • Jira: Risotto raises the request on behalf of the employee when the request type allows it and the employee has a Jira account with the same email address. If not, Risotto files it as itself, and the employee may not see it in the portal.
  • Freshservice: Risotto sets the employee as the requester.

If filing fails

If your ITSM rejects the request (for example, a required field is missing or the employee is not allowed to order the item), Risotto does not tell the employee the request was filed. The ticket is escalated to your support team so a person can file it. From the Slack App Home, the employee sees "I could not file this request automatically. A member of the team will pick it up from here."

What is not supported yet

  • Conditional logic. Forms where questions appear or disappear based on an earlier answer cannot be collected in Risotto. If the item has a portal page, it imports as a portal item. Otherwise the import fails; for Jira, the import result shows This form uses conditional logic, which Risotto does not support yet. Remove the conditions from the form in the source system, then import it again. To let Risotto collect the form, remove the conditions in your ITSM, then import the item again.
  • Attachments. Attachment fields are not imported. Employees can share files in the conversation thread instead.
  • Freshservice bundles. Items that bundle other items import as portal items.
  • Other field types. Fields such as user pickers, lookup fields, cascading selects, and nested dropdowns are not supported yet. Jira URL fields are not supported yet either. See Supported field types for the types that import.
    • Jira: the import skips these fields and lists them in the import result with the reason "Field type is not supported." If a skipped field is required in Jira, the request will fail to file. Make the field optional in Jira, or keep the item disabled.
    • Freshservice: an item with an unsupported field imports as a portal item. The item list shows the reason when you hover In Freshservice portal, in the form The field '<label>' has type '<type>', which Risotto does not support yet. An item with a field that depends on an earlier answer, or with a nested dropdown, shows This form has fields that depend on an earlier answer, which Risotto does not support yet.
  • Automatic sync. Changes to an item in your ITSM do not sync to Risotto. Delete and import the item again to pick up changes.
  • Status tracking in Risotto. After Risotto files a request, it does not track the request's progress. Employees follow the request in your ITSM.
  • Other sources. Only Jira Service Management and Freshservice are supported. ServiceNow and other ITSMs are not supported yet.
  • Items fulfilled by Risotto. Every item must come from an ITSM. You cannot create an item in Risotto directly.
  • Large forms in the Slack App Home. A form with more than 98 fields, or a choice field with more than 100 options, does not appear in the App Home Service list. The list also shows at most 100 items for each department. Employees can still request any enabled item by asking the agent.
  • A Teams App Home picker. In Microsoft Teams, employees request items through the agent conversation only.

What's next

Risotto is working on catalog items that you build and fulfill directly in Risotto, without an ITSM behind them. If you have ideas or requests, contact your Risotto team, or send a message in your shared Slack channel.

Something wrong or missing? Report an issue · View as Markdown