Recent searches


No recent searches

Cale Shapera's Avatar

Cale Shapera

Joined Apr 15, 2021

·

Last activity Feb 01, 2022

Following

0

Followers

0

Total activity

11

Votes

0

Subscriptions

5

ACTIVITY OVERVIEW

Latest activity by Cale Shapera

Cale Shapera commented,

Community comment Q&A - Help center and community

+1.

I cringe when someone shares one of our articles on Facebook.

View comment · Posted Apr 19, 2019 · Cale Shapera

0

Followers

0

Votes

0

Comments


Cale Shapera commented,

Community comment Q&A - Help center and community

Just bumping this thread, as I'd still love to be able to have a legible sharing image for our help center links. I can't use Kevin's solution as the logo in the help center has to have white text.

The solution I thought of is to have a blue background on the logo (to match the header background of our help center), but that will sometimes render improperly (as the blue in an image, and the blue in our header can render differently as one is a css hex code and one is just a color in a .png).

View comment · Posted Mar 28, 2018 · Cale Shapera

0

Followers

0

Votes

0

Comments


Cale Shapera commented,

Community comment Q&A - Help center and community

Hi Jessie!

Thanks for looking into this for me. I think that it's actually pulling the logo image (ours is white text with a transparent background). Our favicon is a black logo with a transparent background. If it was pulling in the favicon then I'd actually be fine with that!

Attached our some images for reference.

 

Help Center header (w/ logo):

Link image:

Code in the tag. It adds a new og: image, but because it's lower down than the one that Zendesk automatically adds, the offending white one is usually displayed:

Thanks again for looking into this and I appreciate your help!

Cheers,
Cale

View comment · Posted Mar 09, 2018 · Cale Shapera

0

Followers

0

Votes

0

Comments


Cale Shapera commented,

Community comment Q&A - Help center and community

I'm having the same issue as Clayton. I'd like to be able to use a non-logo image as the image when sharing articles. I'd be grateful for any Javascript/jQuery workaround too.

View comment · Posted Feb 28, 2018 · Cale Shapera

0

Followers

0

Votes

0

Comments


Cale Shapera created a post,

Post Discussion - Tips and best practices from the community

Hi fellow KCS-ers!

This post will cover the following details of our KCS implementation using Zendesk:

  • Roles and coaching scheme
  • Help Center sections
  • Article linking workflow
  • Article flagging workflow
  • Article creation workflow
  • Article templates
  • Things we'd like to change about the Knowledge Capture App

We are introducing KCS to a fairly mature CX department (~20 front line agents, ~30 other roles, a popular Help Center with ~700 articles). We’ve begun the first wave of a two wave implementation just this week.

Roles and Coaching Scheme

We currently have three main KCS roles:

  • Reader (can view, link, and flag articles)
  • Contributor (can create and edit internal articles, external articles need to be reviewed by their Coach)
  • Publisher (can create and edit external articles, can be a Coach)

New hires start as Readers and progress to Contributor level after a few KCS training sessions during their onboarding.

Currently, all of our KCS articles are internal, so Contributors and Publishers have, essentially, the same permissions. However, Contributors have Coaches who review all their articles.

Contributors level up to Publisher after receiving over 90% on their coach-administered AQI report for 4 consecutive weeks (or after three weeks of 100% performance), and after proving that they take a KCS approach (capturing the customer’s issue in internal notes, searching the Knowledge Capture App) to each customer interaction. Coaches administer the AQI at weekly meetings.

In addition to the three main levels, we have:

  • Coaches
  • Knowledge Domain Experts

Our current Coaches are six people who were beta-testing our KCS tech stack and workflow prior to the first wave. They received Publisher status as a result of that experience. Now, they're each responsible for coaching three Contributors toward Publisher status.

Going forward, the KCS council will decide which Publishers will become Coaches.

We have three Knowledge Domain Experts (KDEs). These KDEs are responsible for managing the health of the overall knowledge base. They also are responsible for fixing flagged articles and monitoring the quality of Publishers' articles.

Help Center Sections

We have a fully fleshed out Help Center right now with articles that are long, detailed, and wholly non-KCS. These are divided into sections which correspond to our productions feature set.

These existing sections are visible to anyone, and can be managed by "Managers". Front line agents cannot create or edit articles in these sections.

For KCS, we have two sections:

  • KCS - Internal
  • KCS - Future External

Both of these sections are set up so that they can be viewed and managed by "Agents and Managers". This means that front line agents can create or edit KCS articles, and none of our customers can view these articles.

We intend on making the "KCS - Future External" section visible to anyone eventually but, for now, the articles are for internal use only.

Article Linking Workflow

  1. Agent receives a phone call
  2. Agent enters the caller's name and email into a new Zendesk ticket
  3. Agent creates an internal note with the issue (in the customer’s words) in the body and a keyword relevant to the issue as the subject
  4. Agent submits the ticket as new
  5. Agent stays on the ticket
  6. Agent listens to the customer’s question or issue
  7. While listening, Agent searches the Knowledge Capture App and finds an article which solves the issue
  8. Agent uses the article to help the customer
  9. Phone call ends
  10. Agent links the article to the ticket using the Knowledge Capture App
  11. Agent copies the resolution steps from the article into the email response (if necessary)

This workflow has been working fine, although we wish the Knowledge Capture App search was available without creating an internal note. This would allow us to skip steps 3-6.

Article Flagging Workflow

  1. Agent receives a phone call
  2. Agent enters the caller's name and email into a new Zendesk ticket
  3. Agent creates an internal note with the issue (in the customer’s words) in the body and a keyword relevant to the issue as the subject
  4. Agent submits the ticket as new
  5. Agent stays on the ticket
  6. Agent listens to the customer’s question or issue
  7. While listening, Agent searches the Knowledge Capture App and finds an article which is relevant to the issue but has errors/omissions
  8. Agent works with the customer on their issue
  9. Phone call ends
  10. Agent flags the part(s) of the article which need improving
  11. Agent sends a follow-up email to the customer

We've set up a trigger so that all tickets with the “knowledge_capture_flagged_article” tag are moved to a specific View. This View is only available to a specific Zendesk Group (which contains only our Knowledge Domain Experts). The Knowledge Domain Experts are responsible for addressing the flagged article.

Article Creation Workflow

  1. Agent receives a phone call
  2. Agent locates the customer in the admin panel
  3. Agent copies their name and email into a new Zendesk ticket
  4. Agent creates an internal ticket with the issue (in the customer’s words) in the body
  5. Agent stays on the ticket
  6. Agent listens to the customer’s question or issue
  7. While listening, Agent searches the Knowledge Capture App but doesn’t find a useful relevant article
  8. Agent captures information for a potential article
  9. Phone call ends
  10. Agent creates a KCS article (if time/situation permits)
  11. Agent links the article to the ticket
  12. Agent sends a follow-up email to the customer with the new article’s resolution steps pasted (if necessary)

Article Templates

We use three templates:

  • How-to
  • Q&A
  • Issue/Solution

How-to

Q&A

Issue/Solution

Things we’d like to change

  • We’d like to be able to search the Knowledge Capture app without having to create an internal note and submit a ticket first
  • We’d like to be able to create fields in Zendesk which would map to the KCS article templates
  • In terms of analytics, we’d like to be able to:
    • Separate KCS articles from non-KCS articles when looking at linking stats
      • We’re linking a ton of non-KCS articles to tickets, but would love to be able to see the chart below with just KCS articles (certain Help Center sections) included
    • There is no clear way to link articles and the tickets they helped to solve
    • It’s difficult to give Coaches (who are front line agents) access to dashboards in GoodData related to the Contributors they’re coaching
      • This is because it would also give them access to dashboards showing performance metrics for themselves and their peers

Conclusion

As a CX department, we're really pushing hard to implement a KCS mindset into our everyday workflow. The Knowledge Capture App is a big part of that workflow and we're really excited to be a part of its ongoing development.

Posted Sep 01, 2017 · Cale Shapera

3

Followers

29

Votes

7

Comments


Cale Shapera commented,

Community comment Discussion - Tips and best practices from the community

Nice post! Thanks for sharing your implementation details, Daniel.

View comment · Posted Aug 15, 2017 · Cale Shapera

0

Followers

0

Votes

0

Comments