PeepSo support manifesto
Support is part of the product.
Fanatical support means taking responsibility for what happens after installation: the questions, the edge cases, the difficult days, and the trust behind every request for help.
A company-wide promise
for every customer conversation
Software is not finished when it ships. It becomes real when someone installs it, depends on it, and trusts it with a community of their own.
We build PeepSo to be useful, fast, and dependable. But quality is not only what the code does on a good day. It is also how we respond when the answer is not obvious, something breaks, or a customer simply needs a human being to help make sense of it.
A license is not the end of the relationship. It is the beginning of our responsibility—and that responsibility begins with attention.
Attention comes first.
A support request arrives with more than symptoms. It carries the story of what someone was trying to do when the software got in the way.
There may be a launch date approaching, a member waiting to log in, an administrator under pressure, or a workflow that worked yesterday and does not work today. We begin by listening for that context, because the fastest answer is useless if it solves the wrong problem.
Behind every conversation is a person doing real work. They may be technical or completely new to WordPress. They may be calm, confused, frustrated, or in a hurry. We answer with patience, respect, and practical language—not because it sounds nicer, but because understanding is how useful support begins.
Fanatical does not mean theatrical. It means curious, accountable, clear, and unwilling to shrug.
What the word means to us
Listening gives us the right problem. What matters next is whether we take responsibility for moving it forward.
Responsibility means staying with the problem.
WordPress sites are ecosystems. Themes, plugins, hosting, custom code, browsers, and settings all meet in one place. Problems do not always respect product boundaries.
Customers should not have to navigate our internal ones. Even when a final fix does not sit entirely inside PeepSo, we can still help gather the right evidence, explain what we see, and make the next step clear.
Some issues yield to one careful reply. Others need reproduction, testing, another set of eyes, or a product change. Staying with the problem means preserving context, following up, documenting what changed, and never making someone start the whole story again without good reason.
Persistence matters, but silence can make even careful work feel like neglect. Responsibility has to be visible, which is why clarity matters just as much.
Clarity keeps the work moving.
Customers deserve answers they can understand and use. We do not want jargon, vague updates, or instructions without reasons to become another obstacle.
When we know, we explain. When we need to investigate, we say so. When there is a tradeoff, we make it visible. We ask useful questions, respect the customer’s time, and keep the next step easy to find.
Clarity is not decoration around the solution. It is part of the solution. It gives people confidence to act, helps everyone preserve context, and turns a long investigation into a sequence of manageable decisions.
And once the immediate problem is resolved, the conversation still has one more job to do: make PeepSo better for the next person.
Every answer should make the product wiser.
Support is where product reality speaks most plainly. It shows us the distance between what we intended and what someone actually experienced.
A recurring question can become clearer documentation. Repeated friction can become a design change. A reproducible defect can become work for engineering. The individual conversation matters on its own, but the pattern behind it matters too.
Closing the loop means carrying that learning back into PeepSo. The best support does more than solve today’s problem; it helps prevent tomorrow’s.
So this is our pledge.
This is not a claim of perfection. It is a standard we return to, conversation after conversation.
We will read carefully before we reply. We will ask useful questions, say what we know, admit what we do not know yet, and keep the next step visible.
We will stay human and stay accountable. We will preserve context, use what we learn to improve the product, and remember that your community is the reason the software matters.
When you need us, start where it makes sense.
Tell us what happened, show us what you expected, and share whatever context may help. We will take it from there.
Contact PeepSo support Read the documentation Ask the community
Our customer-care workflow is powered by Awedesk, helping us keep context and follow-through in one place.
Your community matters. Helping you take care of it matters to us.
That is fanatical support.