Skip to main content

Awesome Tools for Small Business: Customers First with FreshDesk

Small businesses often suffer with customer service, whether they realize it or not. Clients quickly learn that the best way to get a response is by identifying one person who always help them individually or, worse for everyone else, having the president's direct number on speed dial.

There are lots of tools out there that help resolve this. They handle customers in a variety of ways - it might be a CRM app or explicit help desk software. I remember fifteen years ago, a lot of companies had sprung up offering these services but they all cost money and when you're a small shop, it was often better to build it yourself.

I switched recently to FreshDesk. 10 Reasons why:

1. Growth path - their pricing models allows unlimited agents in their "sprout" plan. Many systems offer trial periods or limited number of users. Freshdesk offers strong functionality and then added features as you pay. In short, their cheapest plan is "free" with GREAT functionality.

2. Knowledge Base Portal. While you can put a lot of content on a web site via blogs and documentation searches (thanks Rick and West-Wind for that), the knowledge base portal is a critical part for customer self-service. While it's not completely configurable in the free edition, it's a great start.

3. Grouping. It's super easy to get support groups, even for sales purposes and then route tickets to

4. Basic Ticket escalation. Even in the sprout plan, you can easily identify tickets where problems may be starting and escalate those tickets.

5. Personalized URL. Your URL is your company.freskdesk.com. Your support email now becomes support@company.freskdesk.com.

6. Email handling. Forward an email to your Freshdesk support email and Bang! Ticket is created. When clients reply to that email, it is automatically added to the ticket.  If clients create multiple tickets because of the way they reply, you can easily merge tickets.

7. Customer / Contact handling. Freshdesk offers both Contact and Company grouping for clients.

8. Mobile app. The mobile app offers notifications when you're on the go. You're always in the loop.

9. Status handling. You can mark a ticket as Resolved which lets the customer know you plan on closing it soon. They can then choose if they want to re-open it.

10. Awesome premium features: satisfaction surveys, live chat and more.

Some of my small clients used to be spending $80 a month per user for just a portion of these features. While customers love the feature, it became very expensive to continue offering it. FreshDesk offers a great way for smaller companies and start-ups to be AWESOME.

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...