Feeling embarrassed to work on Otto. What to do :(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
21m ago
In my current company, I have been kind of forced to work on Otto products.
Looking at the OOTB AI agents/Agentic workflows, I feel like switching my career to some other better platform/technology.
see these examples:
1. Explain SLA use case - we can ask question like 'will this incident breach?' - AI agent sees if business elapsed time has crossed 70%, then it says YES. if not it says NO.
WOW use case!!!!
2. Incident Assist use case - it will give the summary of incident data including the problem and change request attached to it. But what details you know? PRB123 is attached to this incident. CHG123 is attached to this incident. Thats it 😄
Again, WOW use case!!!!!
3. Wrap up and resolve use case - one agent will generate resolution notes. another agent will create knowledge article. We already have respective gen ai skills. I was wondering what is the difference between those skills and these AI agents.
Then I see that the AI agent is using those skills only as inputs.
Again, WOW use case!!!!!
4. Schedule a change use case - it will check the Maintenance window tagged to the CI and then tell give some suggestions around planned start and end date.
Ex - For a change request, I have mentioned planned start date as 9am, end date as 6pm on Friday,
The maintenance window attached to the CI is> Only Sunday, 6am-7am
This AI agent did not even check the day (which is Sunday). It told me that the allowed duration is 1 hour.
So I am proposing the end time is 10 am.
Again, the best use case I have come across. WOW!!!
Shi**ttt use cases.................... the list goes on and on .......
I have been asked to help customers to implement these use cases. but when I start to see the use cases, my bloood boils like anything.
I want to meet the great people who approved these use cases and give them award.
