|
|
|
|
|
by sachin18590
2699 days ago
|
|
Thats a very good question. There were 2 main reasons for that. There are a lot of chatbot solutions to enable human initiated workflows while there were hardly any solution which enabled human in between an event driven workflow. But more importantly, since we came from a sales focused market and faced the problem of supporting human element within an event driven workflow ourselves, it was easier for us to get the relevant customer feedback. Also, chatops right now is mostly human initiated and is focused on tech. We wanted to tackle enterprise integration market where the need seemed more immediate. A lot of the people we talked to hated logging into their CRMs and updating them at regular intervals can be a very tedious task. Hence we decided to prioritize event driven workflows with human in between, while keeping the architecture open to support human initiated workflows triggered from slack as well. |
|