Forums/Community/Product Feedback

PlannedDoneNot planned

Pre-populate name, email, etc.

Gavin Todes
suggested this on November 04, 2010 08:18

Apparently you can no longer populate this information with the new style dropbox.  Wish I'd known that before spending time trying to figure out why I couldn't get these instructions to work: https://support.zendesk.com/entries/18026-dropbox-advanced-usage (hint: update that post to save others from wasting their time as well).

This is an important feature to those who allow logged-in users to submit a ticket to ZenDesk.  Why should they have to enter their name and email address if my application already knows that information?

 

Comments

User photo
Kamen Petrov

In fact...

I'm able to pre-populate the fields from my customers database.

The issue I ran into is when I enter the first and last names under the "name". My code looks like this:

##################

<script type="text/javascript">
  if (typeof(Zenbox) !== "undefined") {
    Zenbox.init({
      dropboxID:   "<ID>",
      url:         "<URL>",
      tabID:       "help",
      tabColor:    "black",
      tabPosition: "Right",
      requester_email: "test@domain.com",
      requester_name: 'Test Test'
    });
  }
</script>
##################

That code works and I get the email field prepopulated with the test@domain.com. I also have the name field pre-populated as well.

The issue is the name is: Test%20Test .. so.. something on the zendesk side is missing to decode that url part.

In general, it sounds to me like 1 minute fix they have to do. I'm not sure why that would not be possible ?

November 04, 2010 08:47
User photo
Gavin Todes

Thanks Kamen!  Interesting that support told me that this wasn't possible.  I was using "email" instead of "requester_email" as the parameter name.

Now I'm having the same issue as you with %20 appearing instead of a space.

November 04, 2010 13:00
User photo
Kamen Petrov

I guess they told you "email" is not an option and forgot to mention the one that is :)

 

Anyway, the %20 issue still have to be fixed.

November 05, 2010 01:28
User photo
Jake Holman
Product Manager

The URL encoding issue has been resolved. If you're not seeing it fixed, please re-generate your code.

November 05, 2010 09:10
Topic is closed for comments