Logging Inbound Inquiries So You Can See Which Articles Bring Real Conversations

Logging Inbound Inquiries So You Can See Which Articles Bring Real Conversations - editorial illustration

A firm that publishes regularly usually knows its page views and almost nothing about which pieces brought in a call worth having. The missing link is not analytics software. It is a few fields on every inbound inquiry, filled in the same way every time, so the CRM can answer a simple question at the end of the quarter: what did people read before they reached out?

Page views answer the wrong question

Traffic reports are easy to produce and easy to misread. An article can draw a large audience and never produce an inquiry, while a narrow piece read by a handful of people can lead to two serious conversations. A team that only watches readership will keep writing the popular pieces and stop writing the useful ones.

The question that matters for business development is narrower: of the people who contacted the firm, what brought them there, and did the conversation go anywhere? That answer lives in the CRM, not in the website report, and only if someone records it.

The four fields that make it work

A team does not need a new system to start. It needs four fields on the inquiry record, kept short enough that nobody skips them.

The first is the source page: the article, service page or landing page the person was on when they filled in the form or found the contact details. Most website forms can pass this along automatically, and where they cannot, the first reply can simply ask.

The second is the channel that brought them to that page: a search, a newsletter, a shared link, a referral from a colleague, or a direct visit. This is often a guess, and that is fine as long as the guess is recorded the same way each time.

The third is the first-call outcome, chosen from a short fixed list: not a fit, follow-up scheduled, proposal requested, or referred elsewhere. Free text here defeats the purpose, because nobody can count it later.

The fourth is a single line on what the person actually asked about, in their own words where possible. This is the field that shows whether an article attracted the right kind of reader or just a curious one.

Logging at the moment of contact, not at the end of the month

The habit fails when logging becomes a cleanup task. By the end of the month, nobody remembers which page a contact came from or what they said on the first call. The record has to be created when the inquiry arrives and finished right after the first conversation.

This is where an assistant earns its place. When an inquiry comes in through the website, it can create the CRM record, fill in the source page and channel from the form data, and draft a first reply into the inbox for a person to review and send. After the call, it can read the meeting notes and propose the outcome and the one-line summary, which the person confirms or corrects in a few seconds. The person still owns the record. The assistant just removes the typing.

Keeping the categories honest

Logging is only useful if the categories mean the same thing across the team. Two people who label the same kind of conversation differently will produce a report that tells nobody anything.

A short written definition for each outcome helps. So does a rule that nobody adds a new category without agreeing on it first. A list that grows past six or seven options stops being a list and becomes a notes field again. The channel field needs the same discipline, or the counts split across labels that mean the same thing.

Reading the results after a quarter

After three months of consistent logging, a simple report starts to say something. Sort inquiries by source page and look at three numbers for each article: how many inquiries it produced, how many reached a scheduled follow-up, and how many led to a proposal request.

Some pieces bring in a steady stream of conversations that never go anywhere, usually because they answer a question for readers who were never going to hire anyone. Others produce few inquiries but a high share of serious ones. Those are the topics worth writing about again.

The one-line summaries are often more useful than the counts. They show the actual words prospects use to describe their problem, which is the best possible source for the next article's title.

What this does not tell you

Inquiry logging shows what people read just before they reached out. It does not show everything that influenced them. Someone might have read five articles over six months and only filled in the form on the sixth. A team should treat the source page as the last step, not the whole story, and avoid cutting a topic just because it rarely appears as the final page before contact.

A routine to try this quarter

Add the four fields to the inquiry record this week, with a fixed list for outcome and channel. For every inbound inquiry over the next ninety days, have the record created on arrival and completed within a day of the first call. At the end of the quarter, spend thirty minutes sorting the records by source page and reading the one-line summaries aloud as a group.

Pick the two articles that led to the most serious conversations and plan one new piece that follows each of them. Pick the one that drew the most inquiries with no follow-up and ask what it promised that the firm does not actually offer.

Key takeaways

  • Page views measure attention. Logged inquiries show which articles start conversations worth having.
  • Four short fields on every inquiry record are enough: source page, channel, first-call outcome and a one-line summary.
  • Create the record when the inquiry arrives and finish it after the first call, with an assistant doing the typing and a person confirming.
  • Review the results each quarter and write more of what led to serious conversations, not just what drew the most readers.

Questions, answered

What is the short answer on Logging Inbound Inquiries So You Can See Which Articles Bring Real Conversations?

Most firms can say how many people read an article. Very few can say which articles led to a real conversation. A short, consistent way of logging each inbound inquiry in the CRM closes that gap without a new tool.

What are the key takeaways?

Page views measure attention. Logged inquiries show which articles start conversations worth having. Four short fields on every inquiry record are enough: source page, channel, first-call outcome and a one-line summary. Create the record when the inquiry arrives and finish it after the first call, with an assistant doing the typing and a person confirming. Review the results each quarter and write more of what led to serious conversations, not just what drew the most readers.

How does VIPMarketing approach crm & pipeline?

VIPMarketing pushes every contact, meeting and proposal to HubSpot, Salesforce or Microsoft Dynamics 365. Your CRM stays the system of record.