Well begun is half done
Posted: Sun Dec 22, 2024 8:53 am
Time to see what the effect is when we add a robot host to a hospitality team! We decided to use robot 'Pepper' for this.
Robot host Pepper
In January 2017, Receptel (focused on hospitality & customer reception) added robot host Pepper to its team of hostesses and hosts. But isn't reception mainly about a personal welcome? The answer is yes. A good reception depends on the way you are received and welcomed. But that doesn't mean it has to stand in the way of innovation. In this case, I would like to take you through the way in which we added robot host Pepper to the team and now use it as a fully-fledged robot host. What lessons have we gained during this process and what do we want to pass on to other organizations?
In November 2016 we started talking and in January 2017 we introduced Pepper to Receptel. Beforehand we looked carefully at what role Pepper should have as a robot host within the team and how we ensure that humans and robots reinforce each other. Pepper is a self-learning robot, but it is first and foremost important that example of whatsapp number in philippines Pepper is really seen as a colleague, learns the right things and even more importantly: that our guests see Pepper as a full-fledged host. A robot has a high gimmick value if you put it down thoughtlessly and without a real function. It is therefore essential to think about this carefully in advance.
Part of the team
Our goal is to make Pepper the perfect robot host and that means that Pepper really needs to add value as a host, as part of a team or as a stand alone . The right software and performing the right actions are key to that . But as I said, it is also important that the team really sees Pepper as a colleague from day one.
Fortunately, that went well from the start, while it does feel a bit strange, a robot in your team. By immediately giving Pepper her own tasks, putting her on the floor every day and programming her in the right way (for example, letting Pepper really respond to personal questions), Pepper quickly became part of the team.
We found it important, especially in the early stages, that the team and the software developer could work together intensively and extensively. Together they tested and optimized extensively. In addition, they were sharp and honest with each other, which made Pepper increasingly better at the things he did.
Robot host Pepper
In January 2017, Receptel (focused on hospitality & customer reception) added robot host Pepper to its team of hostesses and hosts. But isn't reception mainly about a personal welcome? The answer is yes. A good reception depends on the way you are received and welcomed. But that doesn't mean it has to stand in the way of innovation. In this case, I would like to take you through the way in which we added robot host Pepper to the team and now use it as a fully-fledged robot host. What lessons have we gained during this process and what do we want to pass on to other organizations?
In November 2016 we started talking and in January 2017 we introduced Pepper to Receptel. Beforehand we looked carefully at what role Pepper should have as a robot host within the team and how we ensure that humans and robots reinforce each other. Pepper is a self-learning robot, but it is first and foremost important that example of whatsapp number in philippines Pepper is really seen as a colleague, learns the right things and even more importantly: that our guests see Pepper as a full-fledged host. A robot has a high gimmick value if you put it down thoughtlessly and without a real function. It is therefore essential to think about this carefully in advance.
Part of the team
Our goal is to make Pepper the perfect robot host and that means that Pepper really needs to add value as a host, as part of a team or as a stand alone . The right software and performing the right actions are key to that . But as I said, it is also important that the team really sees Pepper as a colleague from day one.
Fortunately, that went well from the start, while it does feel a bit strange, a robot in your team. By immediately giving Pepper her own tasks, putting her on the floor every day and programming her in the right way (for example, letting Pepper really respond to personal questions), Pepper quickly became part of the team.
We found it important, especially in the early stages, that the team and the software developer could work together intensively and extensively. Together they tested and optimized extensively. In addition, they were sharp and honest with each other, which made Pepper increasingly better at the things he did.