Certification notes
- 1 Substitutions
- 2 First authentication
- 2.1 Prerequisites
- 2.2 Steps
- 2.3 Expected result
- 3 Setup scenarios
- 3.1 Customizing the bot
- 3.1.1 Bot name
- 3.1.2 Bot avatar
- 3.1.3 Welcome message
- 3.1 Customizing the bot
- 4 Conversation scenarios: interactions
- 4.1 Quick answer
- 4.1.1 Prerequisites
- 4.1.2 Steps
- 4.1.3 Expected result
- 4.2 Google support
- 4.2.1 Prerequisites
- 4.2.2 Steps
- 4.2.3 Expected result
- 4.3 Request management — menu
- 4.3.1 Prerequisites
- 4.3.2 Steps
- 4.3.3 Expected result
- 4.4 Request management — create new request
- 4.4.1 Prerequisites
- 4.4.2 Steps
- 4.4.3 Expected result
- 4.5 Request management — file attachment
- 4.5.1 Prerequisites
- 4.5.2 Steps
- 4.5.3 Expected result
- 4.1 Quick answer
- 5 Conversation scenarios: direct input
- 5.1 Hello
- 5.1.1 Prerequisites
- 5.1.2 Steps
- 5.1.3 Expected result
- 5.2 Help
- 5.2.1 Prerequisites
- 5.2.2 Steps
- 5.2.3 Expected result
- 5.3 Search in the internal knowledge base
- 5.3.1 Prerequisites
- 5.3.2 Steps
- 5.3.3 Expected result
- 5.4 Google support
- 5.4.1 Prerequisites
- 5.4.2 Steps
- 5.4.3 Expected result
- 5.5 Request management — menu
- 5.5.1 Prerequisites
- 5.5.2 Steps
- 5.5.3 Expected result
- 5.6 Request management — create new request
- 5.6.1 Prerequisites
- 5.6.2 Steps
- 5.6.3 Expected result
- 5.7 Stop
- 5.7.1 Steps
- 5.7.2 Expected result
- 5.1 Hello
- 6 Conversation scenarios: chat commands
- 6.1 #help
- 6.1.1 Steps
- 6.1.2 Expected result
- 6.2 #exit
- 6.2.1 Steps
- 6.2.2 Expected result
- 6.1 #help
- 7 Live agent support
- 7.1 No operators available
- 7.1.1 Steps
- 7.1.2 Expected result
- 7.2 Transfer to an agent
- 7.2.1 Prerequisites
- 7.2.2 Steps: agent preparation
- 7.2.3 Expected result
- 7.2.4 Steps: transfer to an agent from user side
- 7.2.5 Expected result
- 7.2.6 Steps: transfer to an agent from agent side
- 7.2.7 Expected result
- 7.2.8 Steps: closing the conversation
- 7.2.9 Expected result
- 7.1 No operators available
Substitutions
Please make sure that for most conversation tests you use koji.customer@gmail.com account
JIRA tenant - koji-certification.atlassian.net
Jira Admin username - koji.owner@gmail.com
Jira Admin password - admin_ Pas$w0rd
Customer username - koji.customer@gmail.com
Customer password - customer_Pas$w0rd
Live agent username - koji.agent@gmail.com
Live agent password - agent_ Pas$w0rd
JSDM project name - Certification
FAQ article title – Koji sample article
First authentication
Prerequisites
1. Login as a Jira Admin to test Jira Service Desk Management instance:
Enter
koji.owner@gmail.com
as your email.Enter
admin_ Pas$w0rd
as your password.Click Log in.
Now you can access the Certification service management project in Atlassian.
2. Add the Koji application to your instance. To do so, follow the instruction described on the Installation page.
Steps
1. Log in as a user in a channel. When you open a newly installed application, the bot greets you.
2. Start talking to the bot. When the bot prompts you to log in, enter the following data:
Domain: koji-sertification.atlassian.net
Username: koji.customer@gmail.com
Password:
customer_Pas$w0rd
Expected result
The authentication is carried out successfully, the bot accepts and processes your initial input.
Setup scenarios
Customizing the bot
As a JiraAdmin go to Projects > Certification > Koji backoffice.
In Koji backoffice, go to Koji settings > Global settings.
Bot name
Press Edit button
Provide a bot name i.e. My Bot. Save changes
Refresh the page. Open the chat. New bot name appeared
Go back to Koji settings. Try
Refresh the chat. Default name Koji appears.
Note that only bot name will be changed, that only affect bot messages texts, application/connector name will now be affected.
Bot avatar
Upload the valid image file with bot avatar following the instructions below
Refresh the chat. New bot avatar will be in use.
Remove the image you uploaded from File manager.
Refresh the chat. The default Koji avatar will be used.
Note that these changes only affects bot avatar in JSM portal, application logo or bot connector avatar will not be affected.
Welcome message
Press Edit button
Provide a message. Save changes.
Refresh the page. Open the chat. New message will appears.
Go back to Koji settings. Try the following option:
Refresh the page. Open the chat. Default welcome message appears.
Conversation scenarios: interactions
Quick answer
Prerequisites
1. As a JiraAdmin go to Projects > Certification > Koji backoffice.
2. In Koji backoffice, go to Koji settings > Search.
3. Enable the Search the local FAQ parameter:
Steps
1. As a user, go to the chat.
2. Start a new conversation.
3. Select the Quick answer option.
4. When a bot asks you a question, reply with “sample article”.
Expected result
The bot shows you the FAQ article with title “Sample FAQ article”.
Google support
Prerequisites
1. As a JiraAdmin go to Projects > Certification > Koji backoffice.
2. In Koji backoffice, go to Koji settings > Search.
3. Enable the Google G-Suite support search parameter:
Steps
1. As a user, go to the chat.
2. Start a new conversation.
3. Select the Google support option.
4. When a bot asks you a question, reply with “How can I create Gmail account?”.
Expected result
The bot shows you the article from Google Help center with the title “Create a Gmail account - Gmail Help”.
Request management — menu
Prerequisites
You have passed the authentication for the first time with the bot.
First time when you start managing your requests, bot may ask you for a project, so you must select one JSDM project from the list bot provides to you.
Steps
1. As a user, go to the chat.
2. Start a new conversation.
3. Select the Request management option.
Expected result
The bot shows you the request management menu. It should include the following:
Project ID: it must match the project you’ve selected before
Filter by Status (Open by default)
Current request type (All by default)
List of requests (empty for the new customer)
Button Create new
Switcher Quick status preview/List mode
Button Done
Request management — create new request
Prerequisites
You have passed the authentication for the first time with the bot.
First time when you start managing your requests, bot may ask you for a project, so you must select one JSDM project from the list bot provides to you.
Steps
1. As a user, go to the chat.
2. Start a new conversation.
3. Select the Request management option.
4. Click the Create new button in the menu.
5. Select a ticket type from the list and respond to all bot’s questions.
Expected result
The bot displays a success message with a link to the ticket. When you follow the link, it opens a ticket on the Certification customer portal.
Request management — file attachment
Prerequisites
You have passed the authentication for the first time with the bot.
First time when you start managing your requests, bot may ask you for a project, so you must select one JSDM project from the list bot provides to you.
Steps
1. As a user, go to the chat.
2. Start a new conversation.
3. Select the Request management option.
4. Click the Create new button in the menu.
5. Select a ticket type from the list and respond to all bot’s questions.
6. When the bot asks about the request summary, you can attach files.
Expected result
The bot sends a success message with a link to the ticket. When you follow the link, it opens a ticket on the Certification customer portal. All the attached files are present, as a requests’ comments.
Conversation scenarios: direct input
Hello
Prerequisites
You have passed the authentication for the first time with the bot.
Steps
As a user, go to the chat.
Start a new conversation.
Type
hello
.
Expected result
The bot will greet you and provide the most common options you can use.
Help
Prerequisites
You have passed the authentication for the first time with the bot.
Steps
As a user, go to the chat.
Start a new conversation.
Type
help
.
Expected result
The bot will display a list of options that that you can use.
Search in the internal knowledge base
Prerequisites
Same as for the appropriate scenario with interactions.
Steps
1. As a user, go to the chat.
2. Start a new conversation
3. Type Koji sample article
.
Expected result
The bot shows you the FAQ article with the title “Koji sample article”.
Google support
Prerequisites
Same as for the appropriate scenario with interactions.
Steps
As a user, go to the chat.
Start a new conversation.
Type
How can I create Gmail account?
.
Expected result
The bot shows you the article from Google Help center with the title “Create a Gmail account - Gmail Help”.
Request management — menu
Prerequisites
Same as for the appropriate scenario with interactions.
Steps
As a user, go to the chat.
Start a new conversation.
Type
list tickets
.
Expected result
The bot shows you the request management menu. It should include the following:
Project ID: it must match the project you’ve selected before
Filter by Status (Open by default)
Current request type (All by default)
List of requests (empty for the new customer)
Button Create new
Switcher Quick status preview/List mode
Button Done
Request management — create new request
Prerequisites
Same as for interaction
Steps
As a user, go to the chat.
Start a new conversation.
Type
create ticket
.Select a ticket type from the list and respond to all bot’s questions.
Expected result
The bot displays a success message with a link to the ticket. When you follow the link, it opens a ticket on the Certification customer portal.
Stop
Steps
As a user, go to the chat.
Start a new conversation.
At any time of conversation type
stop
orexit
.
Expected result
The bot will send the message that conversation is finished and provide options in order to start a new one.
Conversation scenarios: chat commands
#help
Steps
1. As a user, go to the chat.
2. Start a new conversation.
3. Type #help
.
Expected result
The bot responds with instructions and tips of what you can do with the bot.
#exit
Steps
As a user, go to the chat.
Start a new conversation.
At any time of conversation type
#exit
.
Expected result
The bot will send the message that conversation is finished and provide options in order to start a new one.
Live agent support
No operators available
Steps
As a user, go to the chat.
Start a new conversation.
Type
talk to operator
.
Expected result
The bot replies that no operators are available and that you can create a request.
Transfer to an agent
Prerequisites
As a JiraAdmin go to Projects > Certification > Koji backoffice.
In Koji backoffice, go to Koji settings > Live agent.
Enable the Enable the live chat so your customers can interact with live agents. parameter:
In Koji backoffice, go to Configuration > Tenants > Tenant role setup.
Set role Live agent to your customer.
Steps: agent preparation
As a user, go to the chat.
If authentication is not passed yet, provide the credentials.
Start a new conversation.
Type
#on
.
Expected result
The bot will send a message about ‘on duty’ status.
Steps: transfer to an agent from user side
As non-agent user go to chat (may use portal chat or chat component inside Koji backoffice).
Start a new conversation.
Type
transfer to an agent
.
Expected result
The bot will send a message that agent will take this conversation and got a summary.
If user send a message, this message will also be sent to a live agent.
If agent send a message, user will see it on user’s side with agent’s name.
Steps: transfer to an agent from agent side
As an agent go to chat.
Prepare yourself as ‘on duty’ as it is described above.
Wait for a user who ask talking to a live agent
Expected result
The bot will send the username and conversation summary.
If user send a message, this message will also be sent to a live agent.
If agent send a message, user will see it on user’s side.
Steps: closing the conversation
From any side (agent or non-agent user) in a chat type
#exit
.
Expected result
The bot will send a message to both sides that conversation is finished.