The challenge

Build a chatbot that creates value for your business

• Ensure your chatbot meets your business needs.
• Bring scalability to your customer service delivery in a cost-effective manner.
• Measure your chatbot objectives with clear metrics.
• Pre-determine your ticket categories to use during the proof of concept.

Our advice

Insight

• Build your chatbot to create business value. Whether increasing service or resource efficiency, keep value creation in mind when making decisions with your proof of concept.

Impact and results 

• When implemented effectively, chatbots can help save costs, generate new revenue, and ultimately increase customer satisfaction for external and internal-facing customers.

The roadmap

Read our concise Executive Brief to find out why you building a chatbot proof of concept is a good idea, review our methodology, and understand the four ways we can support you to successfully complete this project. Besides the small introduction, subscribers and consulting clients within this management domain have access to:

Start here

• Build your chatbot - Executive brief (ppt)

  Almost there!

  Please enter your email and a few details and you're on your way to an efficient process.

  First Name *

  Last name *

  Company name

  * I agree to the Terms and Conditions.

  Download

  You can always get support via our Contact options.

  ×

Form your chatbot strategy.

Build the right metrics to measure the success of your chatbot POC

• Chatbot ROI Calculator (xls)
• Chatbot POC Metrics Tool (xls)

Build the foundation for your chatbot.

Architect the chatbot to maximize business value

• Chatbot Conversation Tree Library

Continue to improve your chatbot.

Now take your chatbot proof of concept to production

• Chatbot POC RACI (doc)
• Chatbot POC Implementation Roadmap (xls)
• Chatbot POC Communication Plan (doc)Chatbot ROI Calculator (xls)

1. Get people to safety by following the floor warden's information and get out if needed
   If there are no floor wardens, YOU take the initiative and alert people. Vacate the premises if you suspect danger.
   Err on the side of caution. Nobody ever got fired over keeping people safe.
2. Get people to safety (yes! double check this)
3. Check what is happening
4. Stop the bleeding
5. Check what you broke while stopping the bleeding
6. Check if you need to go into DR mode
7. Go into DR mode if that is the fastest way to restore the service
8. Only now start to look deeper

Notice what is missing in this list?

• WHY did this happen?
• WHO did what

During the first reactions to an event, stick to the facts of what is happening and the symptoms. If the symptoms are bad, attend to people first, no matter the financial losses occurring.
Remember that financial losses are typically insured. Human life is not. Only loss of income and ability to pay is insured! Not the person's life.

The WHY, HOW, WHO and other root cause questions are asked in the aftermath of the incident and after you have stabilized the situation.
In ITIL terms, those are Problem Management and Root Cause Analysis stage questions.

Deliver on your company's success by being ahead in reliability and strongly aligned capabilities.

Asset Management • Availability and Capacity Management • Change Management • Configuration Management • Incident and Problem Management • Operations Management • Release management • Service Desk.