How to Measure Social Media Enquiries

The first step is to decide what you are measuring. A like, a website visit, a direct message and a suitable customer request are different outcomes, even when they come from the same post. If you do not define them separately, you will end up comparing activity that has very different meanings. A post with many likes may simply be visually appealing, while a post with fewer reactions may produce the sort of request that leads to real work.

A useful set of definitions usually includes at least four stages: enquiry, qualified enquiry, quote and booking. An enquiry might be any customer contact that refers to your service. A qualified enquiry might be a request that matches the service you provide, the area you cover and enough detail to discuss the job properly. A quote is the point where you have enough information to price or estimate. A booking is the point where the work is agreed. Keeping those stages separate helps you compare content more honestly.

This is also where consistency matters most. If one team member treats every direct message as an enquiry and another only records messages that are clearly in scope, the figures will not match. The report will suggest patterns that are really just differences in counting. Writing the definitions where the team can see them reduces that risk and makes later comparisons more reliable.

Not every post is trying to do the same job, so it should not be judged in the same way. A helpful checklist or advice post may encourage saves, later visits and more considered enquiries. A booking reminder may prompt direct messages quickly. A project photo may attract attention without leading to many suitable requests. None of those outcomes is automatically good or bad; what matters is whether the post did what it was meant to do.

For that reason, compare posts with similar goals over a useful period. If you put a reminder post beside an educational post and expect them to perform identically, you are likely to misread the results. The reminder may produce a smaller number of messages, but those messages may arrive faster and be more ready to book. The educational post may produce fewer immediate responses but more useful future enquiries. Their value depends on purpose, not on a single universal measure.

An illustrative example helps here. Suppose one post is intended to explain a service area, while another is intended to encourage bookings for an available slot. The first may be worth judging on whether it attracts the right sort of enquiries; the second may be worth judging on how many people respond quickly enough to fill the slot. That is not a benchmark or a prediction. It simply shows why the same number can mean different things in different contexts.

Once someone gets in touch, capture the basic source information as part of the enquiry record. A simple log might include the date, the channel, the relevant post or link if you know it, the service requested and the next action. This does not need to be complicated. What matters is that the information is complete enough to support a later review, rather than depending on memory alone.

It can also help to ask how the customer found you, but only where that fits naturally into the conversation. Some people will know immediately, some will remember the general route rather than the exact post, and some will have seen several pieces of content before contacting you. That means an unknown answer or a multiple-sources answer should be allowed. Forcing certainty where none exists can make the records look neater than they really are.

The main point is to avoid turning uncertain information into a fake exact answer. If a customer says they found you through social media but cannot name the post, that is still useful. It tells you the channel mattered, even if the specific content cannot be pinned down. Treat that as a legitimate note rather than a problem to be erased.

Tagged links can help when you want to see which content or campaign led to a visit, but they only work well if the naming is consistent. If one post uses one pattern and another uses a different one, the resulting records become harder to compare. A consistent naming convention makes it easier to sort the data later and reduces the risk of mixing up similar campaigns.

It is also important to test the destination. A tag does not help if the link goes to the wrong page, or if the destination is broken. Likewise, tags do not automatically prove that a later booking came from the original click. They may show that the link was used, but they do not remove the need for judgement. The analytics setup has to record the tagged link properly, and even then it will still describe one part of a customer’s path rather than the whole journey.

A practical way to think about tagged links is as a tracking aid, not a verdict. They can make the evidence clearer, especially when you are comparing posts with similar aims. But they do not replace the rest of the record, and they should not be treated as the final word on attribution.

A large number of enquiries sounds positive until you look at how many are actually suitable. If many people contact you for services you do not provide, outside your service area or without enough detail to proceed, the volume alone can be misleading. That is why qualification matters. It tells you how much of the response is genuinely useful.

One practical measure is the qualification rate, which is the share of recorded enquiries that meet your definition of suitable. As an illustrative calculation, if 4 out of 20 recorded enquiries are suitable, that is a 20% qualification rate. This is only a method example, not a benchmark or an expectation. It simply shows how separating the stages gives you a clearer picture than counting raw messages alone.

This distinction also helps when a post seems successful but does not create much work. A high number of unsuitable enquiries may mean the post was too broad, unclear or aimed at the wrong audience. By contrast, a smaller number of enquiries that are mostly suitable may be far more valuable. The report should help you see that difference rather than rewarding volume on its own.

Meaningful comparison depends on context. A one-off post and a recurring content type should not be judged in exactly the same way if their goals differ. Likewise, a post reviewed too quickly may miss later enquiries that arrive after someone has thought it over. A useful period gives the content enough time to do its job, while still keeping the review close enough to the post to be relevant.

It can help to group similar content together. For example, one set might be posts that explain a service, while another set might be posts that encourage direct action. Within each group, look for patterns in suitable enquiries, quotes and bookings. That does not mean every post has to match the others exactly. It means you are comparing like with like more often than not.

This is also where common mistakes appear. People sometimes compare the most visible post of the month with a quieter post from a different aim, then assume the more visible one performed better because it had more likes or comments. Without matching the purpose and allowing enough time, the comparison can lead to the wrong conclusion. The easiest way to avoid that is to review content in categories rather than as isolated moments.

When a post underperforms, the cause is not always the content itself. Sometimes the issue is reach, meaning not enough of the right people saw it. Sometimes it is relevance, meaning the message did not match the audience’s needs. Sometimes the post lacked enough information for a customer to act. In other cases, the problem sits after the enquiry, where slow or unclear follow-up leaves a useful lead unfinished.

A post that produces unsuitable enquiries may need clearer coverage. For instance, if people ask for services you do not provide, the message may need to be more specific about what is included. A post that looks useful but sends people to a broken destination needs a link fix before more promotion. Those are different problems, and the report should help you separate them rather than treating all poor performance as one issue.

This is where interpretation matters as much as measurement. The figures can tell you what happened, but they will not always tell you why. Use the numbers as a prompt to ask whether the issue sits in the post, the link, the service description or the response process. That approach is more useful than simply deciding a post “didn’t work” and moving on.

A simple record is often enough. It may be a spreadsheet, a log in your existing system or another basic business record that already suits the team. The important point is that someone can update it without effort and understand it later without needing a long explanation. If the record is too complicated, people stop using it or start entering inconsistent details.

Jasoto’s guidance here is to keep outcomes in available business records or your existing system, and that is sensible because it keeps the process practical. A small accurate log is more useful than a large dashboard whose figures no one can explain. If the team cannot tell what a number means, they are unlikely to use it well in later decisions.

That does not mean every detail has to be captured forever. It means the fields you choose should support the comparisons you actually want to make. Date, channel, post, service requested, qualification status and next action may be enough for many small businesses. The right level of detail is the one you can maintain consistently.

The point of tracking enquiries is not to create more data for its own sake. It is to support one sensible change at a time. Once you have reviewed the records, ask what the evidence suggests: is the issue reach, relevance, missing information or slow follow-up? Then choose one improvement that matches that finding. If the evidence is not clear, do not pretend it is; leave the record marked as uncertain and look again after more results come in.

This is especially useful when a post has a clear weakness. If a useful post is being held back by a broken link, the best improvement is to fix the link rather than rewrite the whole message. If the post is attracting the wrong sort of enquiry, the next step may be clearer wording about the service area or the type of job accepted. The aim is not to change everything at once, but to make a specific change that the evidence supports.

It is also worth recording attribution limits when you interpret the results. That reminder keeps the report honest. Social media can contribute to an enquiry without being the sole cause, and that is normal. By accepting the limits of the data, you avoid overclaiming and make the report more useful for the next round of content decisions.