Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

After weeks of preparation, training, and support, we know that there will be unforeseen issues that are outside of anyone’s control. No matter how much we train and prepare, we must plan for the unexpected.

The JUNO and Client teams work together to communicate and resolve these unexpected issues during your live event. This guide outlines an issue escalation process so everyone knows what to do and who to contact next.


Team responsibilities

The Client team is the first line of defense

After extensive training during the planning process, the Client team is the first line of defense for any questions that come up during the event. Users might ask questions through:

  • Smartloop, or your alternative help chat software. (For all users.)

  • The Mod tab in the session chat window. (Only for speakers and moderators.)

If you can’t answer a question, follow JUNO’s escalation process flowchart.

The JUNO response team

Your lead Client Success Manager (CSM) is your main point of contact during the event. All CSMs should be able to answer 90% percent of questions asked during an event. If they need help, they loop in our Tech Support team.

The Tech Support team is ready on standby for issues that escalate to them. For example, they might help with speakers' devices or platform access issues during greenroom time.


What to do when a user raises an issue

Use this flowchart to find out what to do next. See details about the communication tools below.

Flowchart describing Client team and JUNO team responsibilities. It begins with clients trying to resolve issues, then escalates to members of the JUNO team.

Gameday escalation process (click to enlarge)


Communicate with users on the site

The Client team uses these tools to hear and respond to questions from users during your event.

Help chat

Mod chat

What it is

A chatbot that floats in the corner of your site. It includes automated responses and live support.

JUNO uses a chat software called Smartloop.

In any session, speakers and moderators can privately communicate in the Mod tab in the session chat window.

Who asks questions

Any user, such as attendees, exhibitors, and speakers.

Speakers or moderators, during a session.

With direction from the Client team, JUNO can give other users access to the Mod chat if needed.

How to respond

The appropriate members of the Client team receive email invites to moderate the chatbot.

Type in the text field to chat with users who requested to speak to a live agent.

Type in the text field to chat.


Communicate with the JUNO team on Slack

Slack is the instant messenger we use for communication between the Client and JUNO teams. The entire Client team receives email invites to an event-specific Slack channel.

Send a message

The Client team should send a message whenever there’s an issue you can’t resolve.

We ask that you be as specific as possible by using this template to submit questions to the JUNO response team. We also encourage everyone to use the Reply in Thread function to keep conversations organized.

Slack message template (copy & paste)

Hi @here,

We’re having this issue:

Affected page/session URL:

Affected users' emails:

Screenshot of the issue (if possible):

 How to post and reply in Slack

To send a message:

  1. Copy the template above and paste it into your team’s Slack channel.

  2. Fill out the template with information about the issue.

  3. Click Send to post the message.

A Slack message with information filled out and ready to send. The Send button is circled.

To reply:

  1. Hover over any message in the channel and click the Reply in thread icon.

  2. Type your reply and click Send.

To open an existing message thread, hover over the message and click View thread.

An open Slack message thread. The steps to reply in a thread are highlighted. First, the Reply in Thread icon, then the empty reply message box.

  • No labels