Docs

Help desk / Where tickets come from

Creating Tickets from Microsoft Teams

How Risotto turns Microsoft Teams channel posts and direct messages into tickets, and how it keeps several requests apart in one chat

Risotto creates tickets from two places in Microsoft Teams: channels you add as request sources, and direct messages employees send to Risotto.

Channels

A Teams channel creates tickets once you add the Risotto bot to the team and add the channel as a request source. See the Teams channel setup guide for the full flow, and Request Sources for the per-channel settings.

Which posts open a ticket depends on the channel's Silent channel setting:

  • Silent channel off: every new post in the channel opens a ticket.
  • Silent channel on (the default for a new channel): only a post or reply that @mentions Risotto opens a ticket. When you mention Risotto in a reply, the earlier messages in the thread are added to the ticket so Risotto has the context.

Risotto answers in the post's thread. It first posts the ticket ID and title, such as [IT-142] Laptop Wi-Fi Connection Issue, then shows a status card while it works, and replaces the card with its answer.

Each request stays in its own thread:

  • Replies in the thread go to the same ticket. In a silent channel, Risotto ignores replies unless the ticket was opened by mentioning it or the reply mentions it.
  • After the ticket is resolved, a reply that @mentions Risotto reopens it. Other replies get a private note, seen only by the sender, explaining how to reopen the ticket or start a new thread.
  • A new post opens a new ticket.

Direct messages

Anyone in your organization who has the Risotto app in Teams can message Risotto directly to open a request. There is no channel to add and no opt-in. See Microsoft Teams app setup to make the app available to everyone.

When the app is installed for someone, Risotto sends them a one-time welcome message in their chat.

One chat, several requests

A Teams 1:1 chat has no threads. Every message lands at the end of the same conversation, so several open requests share one chat.

Risotto reads each message against the requests already live in that chat and decides where it belongs:

  • An answer continues the request that asked. If a responder asks "What kind of headphones do you use? With mic, without?", the reply "With mic please" goes to that request, even though it would read as a new request on its own.
  • A new topic opens a new request. "I need to request PTO for 4 days next week" starts its own ticket, even mid-conversation about something else.
  • When Risotto can't tell which open request a message continues, and those requests belong to one department, it continues the most recently active one. If they span different departments, it opens a new request instead, so an HR answer never lands on an IT ticket.

A new request starts with its ticket ID and title, as in a channel. When more than one request is live, Risotto also names the one it is continuing before it replies:

Continuing [IT-151] Headphones Request

Which requests Risotto considers

Risotto matches a message against the live requests in that same direct message chat. It does not consider:

  • Requests opened in a Teams channel. Those belong to their channel thread, and Risotto replies there.
  • Requests from Slack, email, Jira, or the portal. Only Teams direct message requests are matched.
  • More than the 5 most recently active requests. Older ones fall out of consideration.
  • Requests resolved more than an hour ago. Inside that hour, "that didn't work" reopens the request instead of opening a duplicate.

Anything outside that set opens a new request.

Messages that never open a ticket

Greetings and help commands are answered directly and never create a request:

  • Greetings: hi, hello, hey, yo, hiya, howdy, hi there, hello there, thanks, thank you
  • Help: help, ?, commands, command, menu

A message with no text and no screenshot gets a short reply asking what you need.

Other behavior

  • Screenshots. A screenshot sent with no caption goes to the request that asked for one.
  • Edits. Editing the message that opened a request that's still open updates the request text. If that message included a screenshot, the edit is recorded as a note on the request instead. This works the same for the post that opened a channel request. Editing a later message, or deleting a message, doesn't change the request.
  • Waiting on an approval. While a request waits for an approval or identity verification, your messages are added to it and Risotto replies that it will pick them up once that's done.
  • When a person takes over. Once a request is escalated, or someone on your team takes it over, Risotto steps back. The employee's later messages are added to the request for that person to read, and Risotto does not answer. Bringing up a new topic still opens a new request, which Risotto handles as usual.

Asking Risotto to take another look

A Teams chat has no bot to mention, so a direct message cannot use the @Risotto mention that hands a request back to the agent in a channel. Risotto offers a button instead.

When the employee writes again on a request a person has taken over, Risotto files the message on the request and posts a card:

Someone from the team is handling [IT-83] Desk Setup and WiFi Issue, so I am staying out of it. Your message is on the request. Use the button if you want me to take another look.

Take another look

Pressing the button changes the card to "Taking another look now.", clears the escalation, and puts Risotto back on that request, which it then answers as usual. The status a person set is left as it is. If the request was resolved in the meantime, pressing the button reopens it.

Routing direct messages to a department

By default, Risotto classifies each direct message request on its own. To send every Teams direct message to a single department instead, go to Settings → Request Sources, click Manage in Microsoft Teams, and on the Requests tab open Personal Chat and set Lock to department.

Personal Chat appears in the list of Teams channels once someone has sent Risotto a direct message. See Request Sources for the other channel settings.

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