Customer story · Internal IT
A Telegram outage report becomes the correct service request
Tariq supports field staff who report access and device problems through Telegram.
Learn more
- Before
- A manager writes “warehouse scanners are down” in a regional chat. Copying that sentence into Jira creates a vague issue with no request type, affected site or impact.
- The moment it changes
- The agent asks for the missing site and device group, then prepares the correct Jira Service Management request with impact, diagnostic messages and the verified requester. A possible major incident requires human confirmation.
- After
- IT receives an actionable request, the Telegram chat gets the issue key, and later status changes can be summarized back to the manager.
- Result
- Informal incident language becomes structured service work without pretending the model diagnosed the outage.
What moves where
| Verified requester + location | JSM requester and organization |
|---|---|
| Impact and symptoms | Request type and description |
| Source chat | Issue key comment in Entergram |

