New Site Live!

Drumroll please….

After battling a few delays and many long hours of work, we’re pleased to announce that our redesigned company and product sites are now live.

homepage

So, in a nutshell, here’s what you can expect from the new sites:

  • More refined, cleaner, look and feel. Having been a few years since our last version was created, it was time for a change!
  • Content for new customers. As mentioned under previous posts, we have an updated Tour, Getting started guide, and one page factsheet; all optimized for the prospective and new customer.
  • Easier to find content. Along with the new look we move important content around. For example, customer case studies/testimonials are more prominent than before. Our customers have great things to say about HelpSpot and are using it in some interesting ways, something we thought worth highlighting.
  • Quote generator. Prospective customers can now create their own quotes, just as we would provide to them. This should prove to be a HUGE time saver for us and just plain more efficient for customers. Now, instantly they can have a quote to take to management for purchase authorization.
  • New Domain. For those paying close attention, you’ll notice our old site was hosted on userscape.com. We’ve since broken out our content into 2 sites: helpspot.com (product site) and userscape.com (company site). Our founder, Ian Landsman, explains his thoughts around why we’ve done this in a recent blog post.

OK, enough blabbing on…go check it out already and tell at least 3 friends to do the same!   www.helpspot.com

Site redesign sneak-peek: the Tour

While the redesigned helpspot.com is still under-construction, our new and improved tour is starting to take shape.

Just to give you a flavor of what’s to come….
peek

What’s new with the tour? Everything! Starting with the look/feel. Carrying over the fresh color palette and new style for icons and images from the rest of the site, the message of the tour will be delivered with a polished sophistication.

Content too has seen an overhaul. I grouped features, specific tools, and over-arching philosophies into conceptual areas to provide more of a narrative for those new to HelpSpot; designed to be a logical organization of the key points for those in the market for help desk software.

  • Manage: How will HelpSpot allow me to more effectively manage my customer service?
  • Work: Which tools will support my goals of efficiency and delivering great service for every inquiry?
  • Self-Service: A must to satisfy the growing pool of web-savvy customers.
  • Measure: Reporting to measure the good, bad, ugly and everything in-between.
  • Customize: Maximizing HelpSpot’s flexible framework to create a support management tool that reflects my business needs.
  • Developer APIs: No business app. can call itself complete without full integration with vital external systems; HelpSpot is no exception.

Batch Responses from the Workspace

HelpSpot’s Batch Response/Edit Request feature saves time and increases productivity by using a single response to reply to multiple requests and/or making Request Detail changes on multiple request at once.

Batch Responses can be preformed from any filter including the Inbox and My Queue. Let’s look at My Queue as an example:

In My Queue, there are three request I can answer with one response, so I first must select the appropriate request and then select Batch Respond/Edit Request from the drop down menu.  Once these options have been selected, complete this step by clicking the Submit button.

Batch Response from the Workspace

Moving to the next screen we see the four areas for working:

  • Section 1 -  Notes
    In this section the response is added to the notes.  Typed and/or Appended responses can be used in this section.
    The additional note options functions the same here as in responding to a single request.  The note can be changed from public to private, staffers can be notified, the send email from can be changed to a specific mailbox, etc.
  • Section 2 – Request In Batch
    This section shows the request that the note will be added too and or edited.  You can remove any request from this section by clicking on the red X in the right column.

batch_request2

  • Section 3 – Batch Information & Request Details
    The Batch information section,when the generate filter checkbox is selected,  creates a filter which contains all the requests used in the batch, so if  a follow up is required at a later time, the batch can be based off that filter to update the exact same group of people.  This is particularly useful if for instance, you are an IT group and a server goes down and 50 people email you about it all at once. You could respond to all of them at one time with this feature.

    The Request Details is where custom fields, category and assignment changes will be made globally for the selected request if you select any options here.  Leave custom fields empty to maintain each requests existing values.

  • Section 4 – Begin Batch
    There are two options with Batch Responses.  You can either choose to begin the batch response and have the request update, or you can choose to Begin the batch response and close the request at once.   Once a selection has been made the Process Batch Request process will begin.  It is important not to leave this page until all processes have been completed.

batch_request3

Out of Office Setting (Individual Staff)

With summer comes vacations, which makes it a great time to discuss HelpSpot’s Out of Office feature.

Let’s start by going into the Staffer’s Preferences, by clicking on the Preference link located in the upper right corner of HelpSpot. pref

In the communications area, staff can define what happens to their requests which are assigned to them while they’re “out of office”.  Request can either go back in to the Inbox for reassignment or to a specific staffer by clicking on the Out of Office drop down box and saving their settings.

OOO

What’s important to note here is that any request that are in the staffer’s queue, will not be moved out unless an update has been made.  At that point the request will be reassigned to the Inbox or to the staffer designated in the preference settings. Also, when staffers set this option,  an “Out of Office” is placed next to their name in the assignment box so other staffers can see they’re out.

Remembering the ‘Customer’ in Customer Service

Going through some content as we port to the NEW helpspot.com design (sneak-peek to come…), I came across this article written by Ian, our founder, a few years ago. It’s great–although brief, it encapsulates our underlying vision of HelpSpot when we started and what continues to guide development and support.

Enjoy this oldie but goodie!

***********

At its functional core, HelpSpot is a help desk ticket system. Yet that label, ticket, never appears in the system. It’s one of the first things we choose NOT to do when designing HelpSpot. In our experience one of the major factors that separate a truly great help desk system from a merely average one isn’t technology, but rather a customer-focused attitude.

Sure having a great help desk ticket system with robust functionality is important, and we believe HelpSpot is, but it goes deeper than that. It largely comes down to the attitude conveyed towards the customers inquires. A bad help desk system almost always has a poor attitude towards incoming customer inquires. New ‘problem tickets’ enter the system and are viewed with disdain; as nuisances that need to be quickly closed in an effort to simply ‘clear’ the queue.

How do you distinguish this subtle difference in customer focus?

Start by thinking about the terminology for a moment. The word ‘ticket’ doesn’t express the importance of the customers inquiry nor does it adequately convey the care which is required to make a customer happy. More than likely the phrase ‘problem ticket’ conjures up images of working at a deli counter, where answers are churned out like a Reuben on rye. On the other hand HelpSpot uses the term ‘request’ which has a much different tone by providing a subtle emphasize on the importance of the interaction, rather than churning through the task at hand to move onto the next.

Also consider the supplemental tools brought to the customer experience. HelpSpot provides a customer portal complete with a searchable knowledge base, in the form of knowledge books, forums, and a means to submit and manage all open requests. Giving customers the tools they want and need, while allowing help desks to proactively address common customer concerns in mediums that customers find comfortable and easy-to-use. With the capability these tools bring for interaction between support staff and customers, help desks will be able to foster a complete community around their product/service.

Your Help desk staff don’t want to feel like they work in a deli, churning through an endless stream of faceless ‘problem tickets’ using a system that values the ‘ticket’ over the customer experience, as this lack of customer-focus will be quickly reflected in the level of service they provide. A help desk system focused on the customer interaction, like HelpSpot, will prevent even the best of support staff from falling into the ‘deli counter’ funk.

Hot off the press: HelpSpot Fact Sheet

Based on feedback from those in the help desk software evaluation process, we’ve created a 1 page fact sheet for HelpSpot. flyer

It’s a quick look at what we do, a sampling of who we serve and what they’re saying about us, and–of course–how to find out more about HelpSpot. We think it’s the perfect overview for those doing initial research to bring to team or management meetings.

Download and share with friends and colleagues!

HelpSpot Fact Sheet

Overridding Default Email Templates

In my last post I discussed HelpSpot’s default Email Templates, when they are used and how to modify them.  With the release of version 2.6.0,  it is now possible to override these default templates providing further customization and flexibility to your organization.  This is particularly useful for companies that have multiple domains or mailboxes that are managed in a single HelpSpot installation.

Practical Application

You may be wondering, why would you want to over-ride your default templates.   Let’s say you had one mailbox for servers@yourcompany.com and one for help@yourcompany.com.  Keeping your clients informed of server changes is important to your customer service, so you might want to have an auto reply for servers@yourcompany.com, which contained links to the network up time, & traffic reports.  On the other hand, help@yourcompany.com needs to include the support hours and links to your Knowledge Books & password resets,  to promote customer self-service.

Let’s take a look at how resolve the above scenario.

Mailboxes and their templates are found under Admin ->Mailboxes.
  1. The first step is to configure or modify the mailbox for the email address servers@yourcompany.com.
    Once the account is established and tested, we’ll can configure our mailbox specific templates.
  2. Scrolling down to the Email Templates section.   You’ll notice that here again we have four configurable
    templates associated with this email account.    We’re going to configure the Auto Reply to meet the requirements above.email_1
  3. Click on the arrow to the left of the Auto Reply option.
    email_2
  4. Add the content & placeholders to both the HTML and the Text version of the automatic response.
  5. Optional: Make additional content changes to any or all of the other templates in this area.
  6. Click on the save edits button, to save changes.

Email Templates

HelpSpot was designed to with the intention to give users full control over how you communicate with your customers, by giving you the ability to fully customize email templates to include the information specific to your organization.

HelpSpot includes 10 default templates found in the Admin -> Tools -> Modify Email Templates Section.  They are available in both plain text and HTML formats,  to ensure users without HTML email support can view emails in their mail client. Because of this, both versions of the templates should be edited when modifying them for consistency.  Additionally, HelpSpot provides dynamic placeholders which can be inserted into the templates to provide specific information.

Let’s take a closer look at these templates and their uses.

  • Public Notes to Customers -  Emails to customers use this template. This is a great place for a unified footer or to brand with your organizations design.
  • External Notes – Used when staff select the “External Note” option under the note box on the request page. External notes are notes which are usually sent to someone other than the customer (such as a vendor), but where the response is threaded privately back into the request.
  • Request Created by Portal Form- When a customer submits a request via the portal form this template is automatically sent to them as an acknowledgment email.
  • Notify Staff on A Request - is used when you choose to notify a staff member from a specific request.
  • Staff Notifications – Any emails to staff members about events like reassignment, customer replies, and new unassigned requests use this template.
  • Reminders-This template is used for reminder emails to staff.
  • Forum Topic Subscriber -When a forum thread is updated this template is used to send all thread subscribers an email.
  • New Staff Welcome – When a new staff member is created in Admin ->Staff this template is automatically sent to them with their credentials and instructions for logging into HelpSpot.
  • Retrieve Portal Password – When customers clicks “Retrieve My Password Link” from the Portal’s Request Check page, this email template is sent with the password included.
  • SMS Messages – This template is used for the body of SMS messages the system generates.

Placeholders

Placeholders are specially designed code blocks that are replaced with specific chunks of information such as a the Email Subject, the URL address to check a request, the customers first and last name, etc.

Placeholders start and end with two pound signs, which must remain in this syntax for them to function correctly.

Example:  ##MESSAGE##

email_templates

Email Templates and placeholders.

Placeholders can be added to both the text and HTML templates and the template’s subject line, by simply clicking on the Insert Template Tag drop down menu and selecting one from the list.

email_placeholders2

Practical Use

Frequently we get request from organizations who want their Pubic Notes to Customers template to function like a “normal” email, where the history of all the previous correspondence is included, instead of the note.

This can be accomplished easily by adding  the “last email by customer” placeholder to customers email template.  So then when you send a public response, an email is sent to the user. If the user replies by email, the previous correspondence is included in that email. This continues for the duration of the correspondence.

lebc

Last Email By Customer

Another common request we get is from organizations is the ability to filter request notifications in their mail client, such as Outlook.  One way this can be achieved is by adding the “Category” placeholder directly into the subject line.  Email notifications can then be arranged by category.

cat_subject_fin

Sorted by Category in Email Client

Finally, some organization prefers to inform your customers of the status of the request, letting them know if their request is active, closed or pending.    This is simple to accomplish by adding the “Status” placeholder within the body of the Pubic Notes to Customers template.

Status Placeholder

Status Placeholder

Sending Attachments From The Portal.

A question recently sent to me by a customer asked how they can accept attachments via the request form.  Which reminded me that customers often aren’t aware of these 2 settings:

  1. Admin -> Settings -> Portal -> Allow file attachments: yes/no
  2. Admin -> Settings -> Portal -> Do Not Allow Attachments with These Extensions:

portal_file_attachmentsSetting, “Allow File Attachments” to yes, will provide an upload text box to your Portal’s Request Form page allowing customers to send attachments with their request.  However it’s important for the security of your server,  that you define attachment extensions that are not allowed.  For example: executable (exe) files or Visual Basic (vb) scripts.   You can put as many different file extensions in the “Do Not Allow Attachments with These Extensions” box, but make certain that you separate them with a comma.

Reopening A Request

This weeks setting exploration is on  Reopening a Request located in  Admin ->Settings->Email Integration.

We found that many customers like to save request notification emails for months on end, which can be problematic if they respond to an old request with a new issue.  Help Desk staffers end up wasting time researching historical information and manually creating new requests.   So, this setting was developed to control how many days a reply will automatically cause the request to be reopened.

In most installations this will be set for 30 days.  However, if normally your requests are wrapped up in 2-3 days moving this setting to 10 days may be more appropriate and decrease the number of re-opened requests. Some of our customers always want closed request to be reopened, which can be achieved by setting  Days to zero (0).