Microsoft offers the Azure Bot Service (replacing the former Microsoft Bot Framework), a managed bot building platform, which provides an integrated environment that is purpose-built for bot development, enabling you to build, connect, test, deploy, and manage intelligent bots, all from one place.
N/A
ServiceNow Now Platform
Score 8.7 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
It is suited for applications like computerizing messages, or any business thought that would require the entrepreneur to robotize their reactions, particularly assuming they are managing a ton of clients and they can't answer to every single one of them. It'd be the most ideal to computerize messages of enormous associations where the reactions measure up to the clients' assumptions. It would be less appropriate in associations where clients' viewpoints matter and every client is interesting and requires the association's consideration, where the specialist organization doesn't need to sum up the clients' interests.
ITSM is straight forward creation of Incidents and Requests. It can get more confusing as you layer more modules on top of it with event management, risk, project, etc. It also becomes more costly as everything is a different license. Integration between other external applications is very easy to do with their API. You can easily create endpoints for external apps to talk to or create REST messages for the platform to reach out directly.
They have simplified the coding for the bot in Azure, but it would help if the coding was further simplified so that non-IT can operate [and] create it easily.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
Azure Bot Service provides an integrated environment for bot development. Microsoft Azure Cloud is fully compatible and its security features. It's more important to pay attention to the logic of business than the specifics of each messenger. We don't have any issues using the bot framework because the implementation is excellent.
It provides a lot of modification options which is wonderful for certain team usage but becomes too much of a job when it comes to the Service Desk. Also on the app support side, since too much information can be carried, it affects the GUI and makes it complex.
The platform is provided as a SaaS solution and support from the vendor has been good. There are regular software releases with bug fixes, new features and enhancements, and furthermore we are given the opportunity to fully test these before rolling these new releases out into the production environment to minimise the risk of business disruption
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
Microsoft Bot Framework is much better and well more established without a lot of proprietary software/coding language. Lex is very limited with integration with standard hardware and network configurations. Lex has performance issues and was too slow to meet near real-time collaboration requirements. Bot Framework complements many other Microsoft communication products and this was key to implementing without a lot of new training required.
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is what makes it far better solution over Remedy
Our base managed service MSA is very clear and focused on our use of ITSM (ITIL role license). Other parts of the platform use some sort of transaction count licensing. This type of pricing does not work for an implementation of our scale.
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
Interfaces with the SQL data set, tracks down plans/replies, and tests them with the SDK.
Utilizing the system is made conceivable by the Bot Dev gateway. We can interface our bot in excess of ten channels, including Twilio Facebook, Twilio, Twilio, and Slack, and that's only the tip of the iceberg.
Fast implementation of our Sales & Operation/Projects controls and process - tool adapted to our needs, not us to adapt to the tool.
Once we are a consulting/implementation company, our customers are happy to see that we use what we sell, and it is easy to show them how this platform/tool can have an impact on our own business.
