| Table of Contents | ||||
|---|---|---|---|---|
|
Substitutions
Please make sure that for most conversation tests you use koji.customer@gmail.com account
JIRA tenant - koji-sertificationcertification.atlassian.net
Jira Admin username - admin@companykoji.owner@gmail.com
Jira Admin password - admin_ Pas$w0rd
Customer username - customer@companykoji.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
...
1. Login as a Jira Admin to test Jira Service Desk Management instance:
URL: Go to koji-sertificationcertification.atlassian.netUsername: admin@company.
Enter
koji.owner@gmail.comPassword: as your email.Enter
admin_ Pas$w0rdas 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.
...
Domain: koji-sertification.atlassian.net
Username: customer@companykoji.customer@gmail.com
Password:
customer_Pas$w0rd
...
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.
| Info |
|---|
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.
| Info |
|---|
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.
| Info |
|---|
Note that these changes only affects welcome message in JSM portal, application initial message will not be affected. |
Conversation scenarios: interactions
...
4. When a bot asks you a question, reply with “Koji sample “sample article”.
Expected result
The bot shows you the FAQ article with title “Koji sample “Sample FAQ article”.
Google support
Prerequisites
...
No operators available
Steps
...
As a user, go to the chat.
...
Start a new conversation.
...
Type
talk to operator.
Expected result
...
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 talk to operator.
#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.