Start social media lead management with a manual handoff your team can follow: capture the inquiry, check service fit, assign an office recipient, confirm receipt, and record the next action. Keep the original conversation connected to that record so a forwarded message does not become an ownerless request.
For a local-service business, the useful goal is an inquiry your office can assess and act on. You do not need a complex system to define that process. Begin with a shared intake log, named responsibilities, and a weekly check for requests that fell between the social inbox and the office.
Give the inbox and the office different responsibilities
Name the person responsible for noticing social inquiries and responding within the availability your business actually supports. Give that person a backup route when absent. Identify which business-controlled accounts and conversations are included in the assignment.
The inbox owner gathers initial context and explains the approved next step. The office recipient decides how the request enters your normal assessment or scheduling process. Neither role should assume the other is handling a conversation without a recorded handoff.
If an agency manages your posts, ask whether its scope includes monitoring inquiries, gathering context, forwarding requests, and checking receipt. Posting and intake responsibilities need separate answers.
When discussing social media management, ask for an example handoff using your actual office route. Agree who handles a request that arrives outside the monitored scope rather than letting the customer-facing message imply continuous coverage.
Keep an escalation owner for unclear service requests or conflicting instructions. The inbox owner should be able to ask for a decision without making an estimate or availability promise.
Move public questions into an appropriate contact route
Use public replies for general service information and directions to contact the business. Do not ask someone to publish a full address, access instructions, private project photographs, or other sensitive details in a comment.
A practical reply can acknowledge the question and invite the person to use your approved private or office contact route. Explain what basic context the office needs. Avoid implying that moving the conversation means a job has been accepted.
If the customer continues privately, gather only what is useful for the initial assessment. If your office requires a different intake route for detailed information, say so clearly and direct the person there.
Do not copy every private message into a broadly shared marketing document. Keep the intake summary focused and give the assigned recipient an appropriate way to review the original conversation when needed.
Ask enough to identify service fit
Use a short set of initial questions:
- What work are you asking about?
- What city or general service area is the project in?
- Is there a constraint the office needs to understand before discussing the request?
- How would you prefer the office to continue the conversation?
Adapt the questions to your services. A general location may be enough to check coverage before requesting a detailed address through the office’s intake process. A brief description may distinguish an installation request from work your company does not accept.
Allow uncertainty. If someone cannot identify the technical service, record their own description instead of forcing a category. Ask the office to assess the unresolved point.
Check the description against your actual scope and coverage. If the request is unsuitable, give an accurate explanation and record the reason. If fit is unclear, mark it for review; do not quietly discard it.
For local businesses, this check should reflect the work the team can assess and serve. The social inbox is an initial conversation, not a substitute for the office’s project decision.
Use a handoff record that proves who owns the next step
Create an intake record for the inquiry and link it to the conversation reference. Use the following fields as a starting point:
| Field | What to record |
|---|---|
| Conversation reference | Channel and a usable reference to the original exchange |
| Request summary | Customer’s description of the work and general location |
| Initial fit | Appears suitable, unsuitable with a reason, or needs office review |
| Contact route | Customer’s preference and the agreed way to continue |
| Inbox owner | Person responsible for the initial conversation |
| Office recipient | Named person receiving the assessment request |
| Receipt | Recipient’s acknowledgment that the handoff was accepted |
| Next action | What happens next, who does it, and the agreed follow-up point |
| Status | Current state and the reason for any hold or closure |
Keep the customer acknowledgment and office receipt separate. Telling someone “I’ve sent your request to the office” does not establish that the office has taken ownership.
Ask the recipient to acknowledge the record and state the next action. Until that happens, the inbox owner remains responsible for following up on the handoff through the agreed internal route.
For example, an inbox owner might summarize a requested service and general location, send the record to the designated office recipient, and keep it marked “awaiting office receipt.” After the recipient accepts it, the record can name who will continue the assessment. This is a workflow illustration, not a customer result.
Keep status changes understandable
Choose labels your staff can use consistently, such as “needs information,” “awaiting office receipt,” “accepted by office,” “follow-up pending,” and “closed with reason.” Record the action behind a status change.
If the customer contacts you through another route, compare the request before creating another active record. Connect a confirmed duplicate to the existing inquiry so the office can see the conversation history. Do not merge requests merely because the names resemble each other.
If information is missing, identify the question and who will ask it. If the person does not respond, use your agreed follow-up and closure practice; keep the closure reason visible.
Do not equate “accepted by office” with a confirmed appointment, estimate, or sale. The office should use your normal process to communicate what has actually been agreed.
Review missed handoffs every week
Set a weekly review with the inbox and office owners. Compare the conversations within the agreed monitored scope with the intake log, then inspect records lacking receipt, a next action, or a clear closure reason.
Look for exceptions: an inquiry absent from the log, an unresolved service-fit question, an unaccepted handoff, conflicting follow-up messages, or a duplicate still treated as separate work. Assign a corrective action and an owner for each.
Keep observations proportionate. The review can identify a process gap without proving that a sale was lost or assigning revenue to social activity. Correct the handoff before drawing a marketing conclusion.
Consider automation only after the manual fields, ownership, and status rules are clear. A tool should support the agreed process, and someone still needs to handle exceptions.
Your next action is to rehearse the handoff with an ordinary sample inquiry and confirm that the office can accept it and record the next step. If you need help defining that process alongside your social management scope, discuss your inquiry handoff with WETOP.