The basics of how to get the best help possible for your WordPress site, from vetting a developer/designer, picking a place to get your theme/plugin, what kind of info to include in support requests, and what the support agents need to help you.
8. Spoiler Alert
⢠Support agents typically are in the support field to
help people.
⢠We actually enjoy it, and really want to help you
succeed online.
9. BAD Requests
⢠âDoesn't work, white page, see attached. Very easy to
understand, just not working.â (no attachment)
⢠User: âWhen is someone going to reply to me?â
Me: âWell, Jerry replied to you on June 3, but you havenât
answered his questions yet.â
User: âWell, sorry, I didnât realize Jerry was the one-stop-
shop for support.â
⢠âWould you please check on what your problem isâ
⢠âSend me instructions for using your software or I will delete
it.â
11. Sometimes It Goes Like This
⢠Youâre cruising along in your site setup. Everything
is going smoothly, and then:
⢠Something breaks.
⢠You go through all the basic debugging steps, but
you are left with no other option.
⢠You have to contact the maker of the theme/plugin
that you are using.
12. So, You Submit Your Support
Request
⢠You tell the support agent about your issue, but you
havenât sat through my talk all the way yet, so you
donât know how best to do this.
13. Slow It Down
⢠Just breathe. Itâs best for all of us. Being snappy or
mean is NEVER the best way to get someone to
help you.
⢠âHELP!â is an email subject that will definitely grab
attention, but itâs not going to get your issue fixed
more quickly.
14. So *How* Do I Get Good
Support?
⢠The easiest way to think about submitting your
support request (ticket/email/chat/phone/however) is
to give as much info about the problem as possible.
15. Sandwiches; We All Love Them
⢠Imagine trying to order a sandwich, stepping to the
counter and blurting out âHOAGIE!â. Would you
expect that worker to intuitively build a chicken
bacon sub with spinach and pickles? We need a
little more information before we start making that
sandwich.
16. Before You Start Typing
⢠When exactly did you first notice the problem?
⢠Have any updates been applied to your website recently?
⢠Have you changed themes or made any design changes?
⢠Have you installed any new plugins?
⢠Can the issue be replicated on multiple devices?
⢠Is your problem happening in one browser, or all of them?
⢠Do you see any specific error messages?
17. Describe Your Issue
⢠If you want a quick helping hand, and a thorough
resolution, then please describe to us your issue.
Describe it in-depth. Tell us *exactly* what is
happening.
⢠Your subject line or first chat is super important to
give us info right away.
⢠The easiest way to tell us is to walk through exactly
what you were doing when the issue happened.
18. Screenshots!
⢠The single easiest way to show us how you got the
error, and what page you are on, etc.
⢠There are a lot of free solutions out there for taking
and sending screenshots. https://cloudup.com/
⢠When I see a ticket with a screenshot, I do a happy
dance. We all love happy dances.
19. Videos!
⢠Possibly even better than a screenshot.
⢠Might make me do an even more intense happy
dance.
⢠If you are on a Mac, you can use QuickTime, and on
Windows, I think you can use Windows Movie
Maker. Also, a lot of the screenshot programs you
use will also do screencasting videos.
20. We Need This Info:
⢠Please, Please, Please send your site URL.
⢠Send us your site login if itâs for a plugin or theme or
something similar thatâs misbehaving.
⢠Send us links to your issue.
⢠Do not send us a 5 page Word document attached
to the ticket, with 6 embedded images. I donât own
Word.
21. There is No Such Thing as
Too Much Info
⢠There really isnât.
⢠Not sending us enough info will delay your
ticket/chat being helped, and likely require us to
request more info from you rather than do what we
both want and actually solve your problem.
24. Make Sure You are Sending
What the Tech Needs:
⢠A lot of times, there are very specific things that you
need to include in your request that arenât in any
general list that I can put up here.
25.
26. Say Thanks
⢠We love hearing thanks. We are human too!
⢠Typically you will end up talking to the same person
more than once, so itâs in your favor to be on their
good side, not the customer from hell.
28. You Have Options:
⢠There are a *lot* of quality places to get some
awesome additions for your WordPress site
(themes, plugins, services, etc.)
⢠The quality of WordPress add-ons in general has
been on a steady climb since I have been working
with WordPress.
29. Letâs Dive Into Plugins
⢠The best place to find or start looking for plugins
(when you are starting out) is WordPress.org
⢠The code has been reviewed by volunteers, and
should be safe to add to your site. You still need to
check and verify your site doesnât have code
conflicts.
30. Here are Some Things to Look
for with Plugins:
⢠Make sure that the plugin is licensed under the GPL
(as is legally required, since they are building off
WordPress)
⢠Look around at what other people are saying. Ask at
the Happiness Bar after this about plugins you need.
⢠Read articles about plugins, and plugin authors.
31. Plugin Checklist:
⢠Has the plugin been updated recently to be
compatible with the latest version of WordPress?
⢠Does it have a strong rating (at least 4 stars or
better) from the WordPress community?
⢠When you visit the plugin authorâs website, does it
appear current? Does it offer support?
32. âPlugin Theoryâ
⢠Plugins should only be installed on an âas-neededâ
basis, not on an âas-wantedâ basis. By keeping this
simple tenet in mind, your plugin strategy will
already be much more solid than most.
33. Hereâs How to Find a Good
Theme:
⢠Make sure that the theme is licensed under the GPL
(as is legally required, since they are building off
WordPress)
⢠Look around at what other people are saying. Ask at
the Happiness Bar after this about a theme you
need.
⢠Read articles about themes, and theme authors.
34. Theme Checklist:
⢠Has the theme been updated recently to be
compatible with the latest version of WordPress (or
plugin that they integrate with)?
⢠Does it have a strong rating (at least 4 stars or
better) from the WordPress community?
⢠When you visit the theme authorâs website, does it
appear current? Does it offer support?
35. Does That All Sound Familiar?
⢠Plugins and themes are both just code.
⢠They both have many resources around the web on
picking good ones, and many places you can check
for recommendations.
36. Some Other Issues with
Themes and Plugins
⢠I would try to get your code from somewhere that
does only or mostly WordPress stuff.
⢠Personally, I would avoid the large conglomerates of
code. There are a lot of good things on the big sites,
but you need to know exactly what you are looking
for.
37. Plugins Vs. Themes
⢠Donât buy a theme that bundles in plugins. Itâs an
extremely bad practice that leaves you open for
hacks and also conflicts.
⢠Another thing to avoid is themes that add
functionality. Functionality is for plugins.
38. Developers are a Bit Different
⢠Sometimes you donât need to hire a developer. Sometimes a
service is better for you if you just need a bit of help with your site,
not something made from scratch.
⢠WP Curve
⢠Maintainn
⢠WP Site Care
⢠If you need a dev for a larger project than maintenance or small
tweaks, then check out Codeable
⢠For a large project, you can look at http://directory.codepoet.com/
39. WordCamps are Amazing
⢠For more than one reason, obviously, but finding
someone or something to take your site to the next
level is not something to take lightly.
⢠I, or other speakers would *love* to get the chance
to talk to you about our favorite themes, plugins, or a
great developer or agency for you.
40. Ask the People You Already
Trust
⢠If you have an awesome host, ask them what themes they
recommend, or plugins.
⢠If you are in love with plugins from one place, ask them
about themes (a lot of times, like at WooThemes, we
actually do both.)
⢠When you find an awesome theme, a lot of times there are
plugins or plugin companies that work well with the theme.
⢠Your developer should have a recommendation for almost
all these things as well!
41. More Info on the Good Guys
⢠http://wptavern.com/
⢠http://torquemag.io/
⢠https://managewp.org/
⢠http://wpbeginner.com
⢠http://sellwithwp.com
42. 2 Things to take away from this session:
1. Give the support agent as much info as possible.
2. Use high-quality code and people.
Iâm with WooThemes, and Iâm going to be talking about getting help for your site. Weâre going to go over a few different areas, from how to help others help you, and then finding good places to get code.
This is a team photo from our most recent WooTrip.
They told us to act like a ninja, but I was already being Batman, so⌠I just went with that.
Itâs almost an unwritten rule that every tech session has to have at least one lego picture, so here is the required slide.
Itâs also a requirement that you include cat pictures, but thatâs not really my style, so here is a picture of my Airedale.
So, a lot of you are probably thinking that I am going to be speaking about specific things that you need to say or do to help people help you. After all, itâs their job, right? If there is one thing that I can get you take away from this, itâs that support agents can only do as much as you allow them to. You have your part in support as the user as well. Most of the examples I will use in this talk will be from a product support perspective, but they can be applied to other things like hosting or anything else.
The average support agent (like me) is actually keenly interested in helping you out, and are not trying to be jerks or anything like that. We really are here to help.
Just donât end up like these next examples
Here is some examples of bad support, but not bad from the support agent. These are the kinds of tickets or responses from users that make us want to facepalm.
I just canât even. What am I supposed to do with that? You can see that those are the most ridiculous examples, but sometimes extremely well-meaning people do similar things, by just not knowing what they need to send/tell the support agent.
Run a few quick test to make sure that your massive issue is *actually* an issue with the website, and not something else.
The list above seems rather extensive, but typically if you think about it for a little bit, one or 2 will stick out at you.
Tell them the story of the social blocker and submitting a ticket over the sharing feature not working on a news site.
Make sure that the issue is not a PICNIC error.
One of the best ways for us to find out what you are seeing is to show us what you are seeing.
Side note: please send screenies.
Remember, we want to solve your issue just as much as you do.
So what kind of info do we need?
This is a great site that tells you a lot of the basics of your system, and spits it out into a file that you can send the support tech.
Follow the instructions that the support tech gives you (or the form)
Iâm not saying this simply because I work in support, but because itâs always a good practice to show gratitude.
Sometimes the best written plugins just wonât work with each other, or with certain themes, but by using quality plugins and themes, you can almost eliminate conflicts.
Frankly, I wouldnât even consider installing any plugin for which the answer to all of the questions above was not âYes.
Something I like to call Plugin Theory, or a way to think about adding and managing plugins. Donât add in plugin (or themes for that matter) willy-nilly.
Itâs basically the same checklist for plugins and themes.
If your theme bundles in functionality, it locks down your site to that theme only.
You have some of the best theme shops, plugin developers, and site developers at your fingertips at WordCamps, so why would you not use them?
WP Tavern is one of the most well known blogs about WordPress stuff.
Torque is owned by WPEngine, and does a good job
ManageWP is more of an aggregator for all the best articles on WordPress stuff around the webs
WPBeginner does exactly what you think. Itâs a huge resource for new users to WordPress
I am fairly focused on e-commerce, so sellwithwp is for that niche.
Well this is about the end of the presentation. Thanks for joining me.