At LoQutus, we believe chatbots will become a key part of digital architectures in the near future. Chatbots are a key interface to your customers, providing basic answers and guiding customers through your services. They can help you get insights into your customer needs, while at the same time improving your operational efficiency. From our experiences with chatbots, we have a lot of lessons learned to share. Keep an eye on this space to learn more! One key thing we want to share today in this blogpost is: it's important to name your chatbots!
Businesses are evolving towards self-service Business Intelligence environments. But what does it exactly mean? Why do traditional BI-environments need to be reviewed and adapted to accommodate these requirements? In this short blog post I will outline some of our key learnings.
Everyone who has worked with the public sector in Belgium knows that there are strict procedures you need to follow, in order to work together with public organizations like cities, police departments or port authorities.
3P has created software to automate the administrative process of document creation and contract follow up for public contracts. However, 3P licenses are expensive and you don’t want your entire organization contacting the legal or contract department every day to inquire about a contract’s status, right? Keep reading for a romantic story of how SharePoint can bring peace to the world of public contracts, while still benefiting from the fantastic functionality 3P provides.
Every organisation has decisions to make at many levels. At the highest level, daily decisions are made with great and lasting effects. Seen the high impact of these decisions, the strategy and context need to be kept in mind during the whole decision process. In order to make these, often tough, decisions, a lot of knowledge and experience is required, to move towards the right path. Managing this decision process is not so straightforward. In this blogpost, we’ll have a look at different ways organisations can tackle this process and leverage SharePoint with usability as the foremost criterion.
When we speak to businesses about analytics & insights, we often hear challenges from business users not getting the insights they need. Business experts have an idea of which KPI’s or metrics they would like to see, and which data is or should be available, but how can they get the outcome they need?
In this blogpost we will explain a fictional, yet realistic, scenario of how a mainframe-based retail company can succesfully join the API economy.
April 2018 is coming closer and some companies are still relying on Access Web Apps. Read on to find out basic and more advanced techniques to migrate.
It was Monday morning and there was a cheerful atmosphere among the company's IT staff. They had worked on a new project release for over one year, the acceptation testing had resulted in a convincing GO, and the deployment to the production environment had taken place during the past weekend without a single hitch. Everybody was optimistic and ready to see the results of their hard work. But it wasn't how they had expected it would be. Users called in with complaints. Their Excel sheets, which contained some custom scripting, didn't work anymore. The report they relied on gave errors. The small piece of crucial software, of which IT never knew its existence, hung on them. What had happened?
As the saying goes "Failing to plan is planning to fail", we started a quest for a planning tool. Requirements? Well, we had plenty of them. The planning tool should be flexible, should provide reports, should be accessible for everyone and should be configurable to our needs. Along the way, we tried out the Office 365 Planner, a member of the Office 365 suite. For our goals, it is a promising tool. And so, we would like to share our vision on it and explain you how you can set up your own Planner.
There was a time when integrating two typical applications required experienced integration specialists. Applications were often very dissimilar and hard to access and the tools used to create integration solutions were equally complex and only really usable by highly skilled and experienced specialists.
Although these cases very much still exist today, we can now also see cases in which people with a lot less technical expertise also integrate applications. This is possible because the applications they integrate are different from the ones we described before, and because the tools which are available to them are also very different from the ones traditionally used by integration specialists.