eventScribe API Push - Login & Customer Support Instructions

Expectations

If a third-party is pushing users to the eventScribe user list, it's expected that you update end-user communications, including any Cadmium login pages, with accurate login and customer support instructions. The client should make it clear on their website/app what credentials the user should log in with (i.e. email and registration ID) and who to contact for login and access/registration support. If no contact information is present, and an end-user reaches out to Cadmium technical support, the user will be directed to reach out to the client contact on file. 


Why is this expected?

  • Cadmium technical support is meant for technical questions about the platform. Clients are expected to assign someone from their team/registration company to field end-user questions about registration, access, and login credentials 
  • Cadmium technical support will not know the users' login credentials and will not be able to assist with login questions 
  • Cadmium technical support cannot change access within eventScribe, as this originates within the third-party application. End-users need to contact registration if they want to update their registration package



Best Practices


Technical Support Popup

As a general best practice, use consistent language for the terms you select for username and access key throughout your registration confirmation email, instructional emails, and within eventScribe. 


Below are suggestions for additional text for your technical support popup. You'll want to customize this to your event. 


Settings Path: eventScribe Website >>> Settings >>> Technical Support >>> Extra Details 

  • Extra Details Title = blank
  • Extra Details Text = Please review the <a href="URL">FAQ page</a> for general questions. Log into this site with [enter login credential terminology here]. If you don't know this information, reference your registration confirmation email or contact [email and phone].<br><br>For technical support for this site, log in to submit a support ticket. Technical support is available 9am—9pm Eastern, Monday – Friday.



Login Screen

Below are suggestions for updated field values and text for your login screen. You'll want to customize this to your event. 


Website 

Settings Path: eventScribe Website >>> Settings >>> Users >>> Login Screen

  • Label: 'Username' = "Email Address"
  • Label: 'Access Key' = "Registration ID"
  • Login Tag Line = "Please enter your registration credentials."
  • Login Alert = "Registration ID not found."
  • Custom HTML At Bottom Of Login Box = "If you don't know your registration ID, reference your registration confirmation email or use the 'Forgot Registration ID?' link. If you don't know the email you used to register or need additional login support, contact [email and phone]."



Mobile App

If you have a website, update your mobile app settings to mimic your website settings.

Settings Path: eventScribe Mobile App >>> Settings >>> Accounts 

  • Entry Page
    • 'Introduction Text' = "Welcome to the [event name] mobile app! Please log in with your registration credentials."
  • Login Process
    • 'Username' Label = "Email Address"
    • 'Password' Label = "Registration ID" 
    • 'Login Instructions' = "Please enter the email you used to register and your registration ID. If you don't know this information, your ID is printed on your badge. You can also reference your registration confirmation email or contact [email and phone]."
      • Reminder: Customize this text to your event. For example, if you don't print registration ID on their badge, you should remove that text or if you call it "Badge ID" instead of "Registration ID", you should use that language.



Introduction PageLogin Page

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article