Start here: Web Widget customizations beta

고정됨

48 댓글

  • Heather Rommel
    댓글 작업 고유 링크

    Hi Erica,

    Our concern is that some end users may not know what the widget is just looking at it. So as (and if) they move their mouse over it, we would like text to display like "Click to send us a message" or similar customized text.

    Does that help?

     

    0
  • kimberly r hayes
    댓글 작업 고유 링크

    Hi Erica!  Is there any possibility and/or ETA of seeing a capability to choose different font families for the Web Widget text?  We would love to customize the font and style so that it is more aligned with our brand and website fonts and style.

    0
  • Erica Wass
    댓글 작업 고유 링크

    @kimberly, thanks so much for writing. We don't currently have that planned. If you could, would you create a post in the customizations beta forum with that request? Then others can add use cases, etc. I'd love for you to include more specifics as well, in terms of what fonts and styles etc.

    0
  • Erica Wass
    댓글 작업 고유 링크

    Thanks for the additional detail @Heather. It's not something we're currently working on, but I've made a note of the request. 

    0
  • kimberly r hayes
    댓글 작업 고유 링크

    Hi Erica!  I am posting my question here regarding custom fonts  ----   Is there any possibility and/or ETA of seeing a capability to choose different font families for the Web Widget text?  We would love to customize the font and style so that it is more aligned with our brand and website fonts and style. Some Fonts we use on our website are Helvetica Neue Light, Avant Garde Regular and Questrial Regular and Bold.

    0
  • Alex Lee
    댓글 작업 고유 링크

    Hi Erica, 

     

    Is there a way to create a custom field for the contact form?

     

    We want to be able to enable a [select a department] field, so we can create triggers to add tags and route the tickets to the correct department.

     

    thanks!

    0
  • Erica Wass
    댓글 작업 고유 링크

    Hi @alex. Absolutely. I'm going to convert your comment into a ticket so that our Advocates can assist.

    0
  • Oleksandr Muzychko
    댓글 작업 고유 링크

    @Erica

    Here is my answer to your question "Could you tell me a bit more about your need for pre-populating the description? "

    Before switching to Widget we have been using older version (zendesk form), where we just pre-inserted few strings into the "Description" filed (preamble). Asking user to leave that text there - that preamble had additional information about the current state of user account and his ongoing activities on our web-page.

    With switching to the widget we got custom fields. There are few issue we see:

    1) Only two custom fields are allowed to be added on widget form. A limitation, but at least something. 

    2) We are not able to populate these fields (additionally to name and email) via ze.identify  

    However, experimenting with the widget I was able to hack it.

    The widget itself uses React.js framework.

    So through a certain manipulations with DOM model I've figured out how to get an access to  React's framework state. 

    Eventually ze.identify request is getting translated into reactInstance.setFormState(...) call. Technically that method allows to populate all the fields of the widget, including custom ones:

    reactInstance.setFormState({
        name: "alex",
        email: "alexTesEmail@yahoo.com",
        "12345678": "settings\address\zipcode",
        "12345679": "12345"
    });

    Where "12345678" and "12345679" are custom filed IDs we have configured using Zendesk Admin web-page.

    The problem is that I can't call this ze.identify(...) the same way (I mean with custom fields). Because these additional JS object fields I am passing to ze.identify(...) are getting truncated in widget code (looks like for security purposes), so only email and name fields are getting populated into the form.

    My "hack" to call reactInstance.setFormState(..) directly instead of ze.identify(...) stops working time-to-time. Your engineering team actively introduce new updates to the widget code, so the path to the reactInstance changes as well. 

    Please introduce new API method to pre-populate custom fields, or at-least remove the filtering of additional object fields in ze.identify(...) request handling (its actually one line of code).

    Here is your minified code which does this:


    r.setState({
          formState: h.default.pick(t, ["name", "email"])
    })

     

    I am guessing  h.default here is Underscore.js

    So to make ze.identify(...)  capable to push custom fields as well pick should be removed:

    r.setState({
          formState: t
    })

     

    Or filter fields array for pick method should contain custom field IDs:

    r.setState({
          formState: h.default.pick(t, ["name", "email", "12345678", "12345679"])
    })

    that means you can't hard code it, but auto-generate and pass as parramter

    filter = ["name", "email"];

    ...

    // on widget load for all widget custom fields:

    filter.push(customFieldID);

    ...

    r.setState({
          formState: h.default.pick(t, filter)
    })

     

    0
  • Erica Wass
    댓글 작업 고유 링크

    Hi all:

    We have added a new customization to this beta: customizable search box placeholder text. We encourage you to explore this customization alongside Contextual Help.

    We look forward to hearing your feedback on this latest addition.

    0
  • adam
    댓글 작업 고유 링크

    Can you provide the link to the documentation for that new customization? 

    0
  • Jacob J Christensen
    댓글 작업 고유 링크

    Hi Adam,

    There's an example in this very article, above under the header 

    How can I customize the Help Center search placeholder text?

    0
  • Andrew
    댓글 작업 고유 링크

    Erica, thanks for all the updates.  We're finally close to adding the widget to our site, and I just wanted to check to see if any new changes were planned soon?  There are a couple I've seen mentioned that would be great to add without having to make changes later (offering live chat AND ticket form contact options, authentication via SSO in widget).  Thanks!

    0
  • Erica Wass
    댓글 작업 고유 링크

    @andrew Congrats on the upcoming addition! Thanks so much as well for keeping such a close eye on our releases and upcoming work. The contact options customization is under active development so that will likely be the next entrant into the customizations beta.

    0
  • Erica Wass
    댓글 작업 고유 링크

    Hi all:

    I'm pleased to say that we have added contact options to this beta under the heading "How can I allow end users to submit a ticket when a chat agent is available?"

    Those who are signing up for this beta for the first time will gain access to this feature once you gain access to the beta. Those who are continuing their participation in this beta should have received an email from me with details about the rollout and how to request priority access, if desired.

    As  always, we look forward to hearing how it goes for you.

    0
  • David Elias
    댓글 작업 고유 링크

    Hi Erica,

    thank you for the documentation.

    Does this mean that we can customize the language via the Dashboard? We have three languages but when we greet our customers everything is in German.

    Or does this have to be changed via API?

    Here is an example from our French website: https://www.posterxxl.fr/mon-panier



    Thanks
    David

    0
  • John Baltazar
    댓글 작업 고유 링크

    Hi @erica,

    Is there a way to change the icon on web widget for "Help" and "Chat"?

    Thank you in advance

    0
  • Daniel Aron
    댓글 작업 고유 링크

    Hi John, you can customize the label (text) on the Web Widget launcher using the API ZESettings https://developer.zendesk.com/embeddables/docs/widget/zesettings#label.  However, at the moment we don't have the ability to customize the icon itself. I'm curious, if we did offer it, what would you expect to be able to do?

    0
  • Justin Fontenot
    댓글 작업 고유 링크

    Hello, I am having the same problem listed by Dave Weldon in https://support.zendesk.com/hc/en-us/community/posts/218033707/comments/226504588 . The top suggestions are sticky when navigating to a new route and the only way to get them to update is to do full refresh of the page in our web app.

    0

댓글을 남기려면 로그인하세요.

Zendesk 제공