Cedric F. Jacob

Using NoteFlow could do the trick for you. It mimics that old feature.

https://www.zendesk.com/marketplace/apps/support/1081069/noteflow

This is really something a lot of my clients need. Please consider.

Hi team,

We are using JWT authentication for end-users in our app. That way they can start chatting with us right away without providing their personal information. (Or so we thought)

However, even when adding the email address to the JWT payload, the email address is not carried over to the Zendesk end-user profile.

    let payload = {
      name: 'Example Person',
      email: 'some@example.com',
      external_id: '123',
      scope: 'user'
    };

    var token = await jwt.sign(payload, 
    'xxxxxxxxREPLACEDxxxxxxxxx', 
    { header: { kid: "xxxxxxxxREPLACEDxxxxxxxxx" } });

This works really well and  the enduser does get the little green tick as seen below:

But only the name seems to be added to their profile.

This rings true for the Webwidget and both mobile SDKs.

So at the moment, we are still asking our users for their email addresses via chat. But this is less than perfect. Any idea?

Thanks

Hey guys,

Some of my clients had a similar issue, so I created an app.

My new Signature 4 Groups app might be helpful here.

It allows admins to set one signature per group using any placeholders, liquid markup as well as HTML for formatting.

https://www.zendesk.com/apps/support/signature-4-groups/

Let me know if you have any questions. I wrote a small blog-post about the app here:

https://www.cedricfjacob.com/viewpost.php?post=setting-a-different-agent-signature-for-each-group-in-zendesk

Hey Sorin,

I had some time and made this one for you:

{
"name": "ACS Customer Information",
"author": {
"name": "s v",
"email": "sv@xxx.xxx",
"url": ""
},
"defaultLocale": "en",
"private": true,
"location": {
"support": {
"ticket_sidebar": "assets/iframe.html"
}
},
"parameters": [
{
"name": "ACSServiceBaseUrl",
"type": "text",
"secure": false,
"required": true,
"default": "yoursubdomain",
}
]
"version": "1.0",
"frameworkVersion": "2.0"
}

So I added parameters and moved "ACSServiceBaseUrl". This is the name of your parameter, which will be provided as text and the default filled in will be "yoursubdomain".

Good luck with it :)

Can you try adding all your settings under "parameters"? 

You can see a few different type of parameters / settings here:

"parameters": [
  {
    "name": "subdomain",
    "type": "text",
    "required": true,
    "secure": false,
    "default": "yoursubdomain"
  },
  {
    "name": "token",
    "type": "text",
    "required": true,
    "secure": true
  },
  {
    "name": "useSSL",
    "type": "checkbox"
  }
]

Hi Eswari,

I hope this message finds you well and healthy.

You would do this by adding parameters to your manifest file:

"parameters": [
  {
    "name": "subdomain",
    "type": "text",
    "required": true,
    "secure": false,
    "default": "yoursubdomain"
  },
  {
    "name": "token",
    "type": "text",
    "required": true,
    "secure": true
  },
  {
    "name": "useSSL",
    "type": "checkbox"
  }
]

You can retrieve the setting values in your app with client.metadata():

var client = ZAFClient.init();
client.metadata().then(function(metadata) {
  console.log(metadata.settings);
});

You can find more here: https://developer.zendesk.com/apps/docs/apps-v2/setup#defining-installation-settings 

Hope this helps.

Cedric

Thanks Nicole!

You are very welcome Sorin.

Hi Sorin,

No worries at all.

One would actually only name the parameters in the manifest file. The manifest file does not hold the values. It is more of a placeholder. 

The actual values are applied within Zendesk. So what happens if you were to add the following parameter to your manifest file?

  {
    "name": "subdomain",
    "type": "text",
    "required": true,
    "secure": false,
    "default": "yoursubdomain"
  },

First you would need to change your app to use this parameter in your code. You would get those parameters using client.metadata():

var client = ZAFClient.init();
client.metadata().then(function(metadata) {
  console.log(metadata.settings);
});

Next, when installing the app in Zendesk, you would have to open the settings of your newly installed app and provide the sub-domain within the settings. That value is then used within the app.

This way you can create an app, that would work in any environment as the end-user can enter the values for those variables that differ from company to company.

Maybe have a look at some of your Zendesk apps within Zendesk and check out there Settings page to get a better understanding. Hope this helps.