Recipe: Add Zendesk Request links in your Resource Center

Last updated:

Note: This article covers a Recipe that can be used with the Resource Center launched after Feb. 18th 2019. 

Overview

If you needed to reach out to Pendo's Technical Support team, you may have submitted your request using the "Technical Support" module inside the Resource Center.  

mceclip0.png

This recipe covers how you can also build this custom module for your own Resource Center.

Ingredients (What You Need)

To configure your Resource Center, you will need the following items:

  • Administrator permission on your Pendo Subscription
  • Link to create a new Zendesk request
  • Link to view all your Zendesk requests

 

How To Make It

Step 1. Navigate to Resource Center

Click on the "Guides" section and then "Resource Center" in the left-hand navigation. 

mceclip0.png

Note: If you have multiple applications setup, you will see a list of Resource Center(s) that have been configured. Choose the Resource Center you would like to add this custom module.

Step 2. Add a new Sandbox Module

To add a new module, hover over the "home view" in the draft tab to reveal the "Add Module" option. 

 mceclip1.png

Click on "Sandbox" module and choose "Add Modules."

mceclip3.png 

Step 3. Configure the Sandbox module in Visual Design Studio

Open your Resource Center in Visual Design Studio by clicking on the "Manage in App" option. 

mceclip8.png

Once you're in the designer, choose the Sandbox module in the tray and use the sample HTML/CSS code snippets as a base template to configure your module.

mceclip4.png

mceclip5.png

HTML Snippet

<div id="intro">
<h3>Need more assistance? Contact our Technical Support Team or view all of your existing tickets below. </h3>
</div>

<div id="support-links">
<button class="button-link-1">
<a href="add-your-zendesk-request-link-here" target="_blank">Create New Ticket</a>
</button>
<button class="button-link-2">
<a href="add-your-zendesk-see-all-requests-link-here" target="_blank">See All Tickets</a>
</button>
</div>

<div class="note">
Powered by Zendesk
</div>

CSS Snippet

h3 {
padding-left: 30px;
padding-right: 30px;
font-size: 16px;
font-family: inherit;
}

.button-link-1, .button-link-2 {
padding: 30px;
margin-top: 5%;
margin-bottom: 3%;
margin-left: 10%;
margin-right: 10%;
width: 80%;
border: 1px #eee;
border-style: solid;
font-weight: 600;
}

.note {
padding: 50px;
text-align: center;
color: #ccc;
}

Once you're done configuring your module, save your changes and exit the designer.

mceclip6.png

Step 4. Adjust your target segment (if applicable)

A new Zendesk request can only be submitted by end users, not agents. If you want, you can hide this module from your internal users by segmenting to customers.

Note: Make sure to add yourself to the segment temporarily so you can test the module in the next step. 

mceclip9.png

Step 5. Stage your changes

Push your changes into "Staging" to see and test your module in your staging environment.

mceclip10.png

Tip: If a user doesn't meet segmenting rules, he or she will not see the module in their Resource Center.

If you don't have a staging environment, you can update the segment to target yourself and push it to Staging. Then, you can test it on yourself when you promote it to Production. 

Step 6. Deploy to Production

After you tested your module, you're ready to push your updates to Production.

mceclip11.png

Tip: If you updated the segment to yourself to test, don't forget to update the target segment back to your end users and push to production again. 

 

 

 

Was this article helpful?
2 out of 5 found this helpful