Nicereply Blog

  • Categories

  • Integrating Nicereply with Kayako Fusion

    6 comments

    Kayako Fusion integrates with Nicereply

    Our next successfull integration is with Kayako Fusion, the one of the leading multi-channel help desks out there. Let us briefly introduce you to this integration in just a few easy steps.

    In order to have a successful integration we need to set the Username in Nicereply to be the same as his Agent number in Kayako Fusion. First, login to Kayako Fusion and navigate to Staff -> Manage staff and click on the Agent you want to setup in Nicereply. Copy the Agent number from Kayako Fusion’s URL and paste it to Nicereply’s ‘Username‘ field found in Settings -> Staff -> Edit Person. The agent number in Kayako Fusion can be found at the end of that page’s URL. It should look like this:

    company.kayako.com/admin/Base/Staff/Edit/2

    Repeat this process for all the users you want to setup.

    username

     

    Next, we have to activate the Ticket Link feature (Settings -> Ticket link) to link every rating to a ticket in Kayako Fusion. We enter the ticket URL into Ticket system URL field, in this case it’s http://company.kayako.com/Tickets/Ticket/View/<TICKET_ID>.

    Important! – make sure to replace “company” with your company name in Kayake Fusion or if you run a downloaded version on your domain then the name used there.

    Ticked link

     

    Now we need to get the ticket ID for your emails. Login to your Kayako Fusion and go to Templates->Templates at left bar and then to Tickets and email_ticketstaffreplyhtml.

    edit template first step

     

    Once you get there you will see the Template code. Insert the text in the red rectangle below into the template at the same place as it is shown in the picture. Important! – make sure to replace “companyname” in both URLs for your company name as written in Nicereply.

    Please rate my reply here:<br />
    <a href="http://nicereply.com/companyname/<{$_ticket[staffid]}>
    /<{$_ticket[ticketid]}>">http://nicereply.com/companyname
    /<{$_ticket[staffid]}>/<{$_ticket[ticketid]}></a>
    <br /><br />

     

    template

    Now your emails will contain also the Ticket ID. The part of the email with the Ticket ID should look like this.

    link

     

     

    That’s it!

    You have now successfully connected Nicereply with Kayako Fusion. Your customers will now be able to rate your helpdesk emails and you’ll have the ability to easily evaluate performance of your helpdesk team AND see what ticket every rating relates to. Don’t forget to try out the integration thoroughly, and if there’s any problem, please let us know.

    Start today

    Share this:

    6 Responses to “Integrating Nicereply with Kayako Fusion”

    1. Goke Pelemo says:

      Hi! I have a question about this integration. Does it work with Kayako’s Live Chat as well? We use Kayako for our ticketing and live chat and thought it might be a great idea to have it work for both. Any insights?

      Kind regards,
      Goke.

    2. Juraj Polach says:

      Hello,
      so far we have integrated only email responces. But I had a brief look on the Templates and I am sure that it is possible to integrate it also this way, just by adding link to one of the templates showed at the end of a conversation. We will try to bring a steb by step guide.

      Thanks for the tip!

      Nicereply team

    3. Paul says:

      I don’t think {$_ticket[staffid]} is correct.

      It keeps returning 0 for us.

      Any thoughts?

    4. Juraj Polach says:

      Dear Paul,

      sorry for a slow reply, is it still an issue? The set up should be working…

    5. Philipp says:

      Hi guys

      We seem to have the same problem as Paul does. {$_ticket[staffid]} returns 0. I’m aware that this is an issue we have to solve with Kayako, but I’m still hoping you already found a solution :)

    6. Juraj Polach says:

      No unfortunately we haven’t. But we will reach out for them, because it appears, that the issue is in within Kayako. Maybe they have made some recent changes in the protocol, that would explain a change in commands as well…

    Leave a Reply