# A Practical Inbound Enquiry Response Playbook

When someone asks about a product, service or partnership, the first goal is not to force a sale. It is to understand what they need and help them move forward without repeating themselves. This playbook gives marketing, sales and channel teams a practical shared process.

1. Capture context at the first touch

For each new enquiry, record the date and time, channel, relevant page or link, contact details the person has chosen to provide, and the core question in their own words. Do not infer intent from a campaign label alone. If you do not know what content they saw, ask politely.

**Intake fields**

  • Date/time:
  • Incoming channel:
  • Product or topic:
  • Enquirer's question, in their words:
  • Next owner:
  • Next action and due date:

2. Categorize by the next action

Use categories that help route work: pre-purchase question, request for information or quote, post-purchase support, partner or media enquiry, and unclear intent. A category should help assign an owner, not label a person without a useful reason.

When details are missing, mark the enquiry “needs clarification” and note the next question. Do not guess urgency or purchase readiness from writing style alone.

3. Acknowledge clearly; do not overpromise

A useful first response has four parts: a greeting, a brief confirmation of the question, information you can verify, and the next step. If you need to check something, say what is being checked and who will follow up. Do not promise a timeline, outcome, price or product capability that has not been confirmed.

**Reply structure**

> Thanks for asking about [topic]. I understand you’d like to know [point]. We’re checking [specific information], and [owner/team] will follow up through [channel] once we have a confirmed answer.

Adapt the language and tone to the brand and channel. Avoid sharing personal details that are not needed, especially in public or group channels.

4. Hand off with a summary, not just a link

When routing an enquiry to sales, support or production, include the original question, relevant context, what has already been answered and what still needs checking. Assign one owner and state the next action. A good handoff means the person does not have to start the conversation again.

5. Set a follow-up rhythm the team can keep

Use statuses that describe work: new, checking information, waiting on internal team, waiting on enquirer, routed, and closed. Give every open item an owner and a review date. Treat response-time targets as internal commitments the team has approved, not automatic promises created by a tool.

6. Review quality regularly

Sample conversations and ask: Was the question answered? Was the reply based on approved information? Is the next owner clear? Was unnecessary personal information collected or shared? Use recurring questions to improve website pages, FAQs or content briefs, while removing identifying details from team-learning examples.

Close-out checklist

  • The source channel and core question are recorded.
  • The reply includes only information the team can verify.
  • If something is unknown, the check and owner are explicit.
  • The handoff includes the context needed to continue.
  • The next step is clear, or the enquiry is explicitly closed.
  • Personal information is limited to what is necessary.

Turn real questions into a stronger inbound system

When the same questions recur, group them by customer need and check whether the website answers them. If new content is needed, explore Content Sprint or learn about Peko Inbound AI for website content operations. Define the team’s review and approval process before putting any workflow into use.

Start with one shared intake format and periodic review of real conversations. A useful process need not be complex; it needs to give every enquiry an owner, a trustworthy answer and a clear next step.