Assigning to @Cntlsn so he can think about some design concepts here while much of the team is at Hackathon.

Below are two different sets of mockups (for both desktop and mobile) tackling the two issues mentioned in the description:

• noticing the help panel CTA
• understanding what the help panel is about

1. The first option explains what the help panel is and makes the CTA more visible -- and it is more invasive. In both the desktop and mobile version the popup contains information about what kind of actions can be taken from the help panel: "It’s time for your first edit!
 Click here to browse frequently asked questions, or ask your own question to the Help Desk. (Questions are usually answered within ~15 minutes).":
   • Desktop version, a popup pointing at the CTA appears on first edit with an animation right after the CTA's animation with, and with a movement that shows its dependency from it.
     
     Desktop Mockup:
     
     Desktop Animated gif:
     

• Mobile version, a fullscreen popup appears on first edit after loading the editor, and blocks the view until the user press a button that says "Ok, got it". The mobile version of the copy also illustrates the help panel icon, as it is not pointing directly to it.
  
  Mobile mockup:
  

2. The second option only makes the CTA more visible -- and it is less invasive. On first edit an animation, similar to the two dots highlighting the link and cite icons of the editor menu bar, leads user's eyes to the help panel CTA:
   
   Desktop animation:
   
   Mobile animation:
   

@Cntlsn -- I think we should start with the option of the pulsing call to action, and I think it should only pulse during the first edit session that a user sees it. We should do it such that it pulses until it is opened. Could you please update the description with those specifications? After you do that, I'll move it to Upcoming Work along with specifications on timing and how we will be careful to detect the difference in open rate.

@MMiller_WMF specifications added to the task description.

Animations are disturbing and, at the end, annoying. The pulsing option should be limited in time (5 sec for instance). The information panel would be more interesting, because it guides the user.

hi @MMiller_WMF - per our discussions together, and also with @Cntlsn, suggest we pause this task as low prio given that the click rates are actually pretty high as it is for help feature. Or else if it is easy to do, can we keep it to a 5sec pulse like Benoît says? I agree a constant pulse until it is clicked would be very annoying and distracting for something that is optional.