Relay makes it easy to work on merchants' Issues all from the same Issue modal (window). In this guide, we will go through the basic SMS workflow and functionality, with you acting as both a Customer User submitting the Issue and an agent working on the Issue.
As a Customer User
Ask your Admin to provide you a phone number for an SMS interaction. Text a help request to that number. An Issue will be automatically created in Relay.
If your phone number is associated with an existing Customer User, the Issue will be associated with that Customer User. If not, a new Customer User (and Customer) will be created.
As an agent
- In Relay, go to the Unclaimed queue in your Issues inbox.
- Review the Case Card to see the information available (e.g. Case Source icon, Owner Team, Customer SMS number, etc.).
- Claim the Issue you created. This action will move the Case to the Mine inbox queue. Verify that the Case has been moved to the right queue.
- Go to the Cases → List and find the Support issue you created.
- Double click on the Case or click on (Pencil) to open the Issue modal (window).
- On the information card at the top of the modal, verify that your name is listed as the Owner User and that the Case status is set to Remote (to learn what the different statuses mean, click here).
- Locate the Public Chat on the left side of the Case modal. Verify that the channel dropdown is set to SMS.
- Send a test SMS to the customer.
- Test the other functions of the modal chatrooms (and learn more about chatrooms here):
- Select the Private Chat tab and send a message in that chatroom. Private Chat allows agents to collaborate on the Case. Customer Users will not see the messages sent here. Learn more about using Private Chat here.
- Click on (Add Log Note) at the bottom of the chat window. Post a note in the chatroom. These notes will only be visible to you and other Relay users who have access to the Issue.
As a Customer User
Check your texts. Verify that:
- You received the messages sent from Public Chat.
- You did NOT receive records of any log notes or Private Chat messages.
As an agent
Navigate to the Issue Edit section on the right side of the Issue modal (window). Learn more about the Issue modal and its functionality here.
- Give your Issue an Issue Name.
- Add the correct tags to the Categories field.
- Tag the product this issue is associated with in the Product field (such as Vx520). The dropdown will show all products associated with that customer location. You can use the Not Listed? button if you cannot find the product in the dropdown.
- Type any additional notes into the Issue Symptoms, Diagnosis, or Resolution fields.
- Hit Save.
- Click Search Articles to search for a knowledge base article to attach to this issue (this would be the knowledge base article you would use to address the issue the customer is emailing in about).
- Open an article, review the content, and then click Add to Issue & Copy URL.
- Validate the article was added to the Articles section and close out of the search panel by clicking the X in the top right corner.
- Go to (Files) on the left navigation bar of the Issue modal and attach any relevant files or images to the Issue.
- Go back to(Issue Details) on the left navigation bar of the Issue modal. Try the following functions:
- Click the Resolve button at the top of the modal (or go to Issue Transitions → Resolve if you have a smaller screen) and set the Resolution field to Completed to resolve the Issue (or to Cancelled if you would like to simply cancel the Issue).
- Go to the Survey Channel section of the resolution form and verify that the Email toggle is off. That way, you, as a Customer User, will not receive a Customer feedback survey at the end of the interaction. NOTE: feedback surveys for SMS interactions can only be sent via email.
- Hit Save to return to the main screen of the Issue modal.
- Verify that the Issue status is Resolved (or Cancelled, if you set the Resolution field to Cancelled). You may now close the Issue.
As a Customer User
You will receive a text notification that the Issue status has changed to Resolved.