A good reply to a Facebook recommendation request answers the person's question and makes your business connection clear. Templates can help you write faster, but each response still needs the context of the original thread.
These are invented, adaptable examples. Replace every placeholder, remove claims you cannot substantiate and check the group's rules. Find Prospects Now identifies conversations for review; it does not automatically comment or message anyone.
A short checklist before posting
- Is the author asking for a recommendation, rather than only sharing an experience?
- Does your service fit the place, scope and timing mentioned?
- Does the group permit a business owner to respond in this thread?
- Have newer comments changed the request or confirmed that it is already resolved?
- Can you offer one useful next step without requesting sensitive details publicly?
Write as yourself and disclose your connection. Avoid posing as an independent customer, pasting the same sales pitch across groups or sending an unsolicited private message because someone posted publicly.
Template 1: a local service recommendation
“Hi [name], I run [business] and provide [specific service] around [area]. For [detail from the post], the first thing I would clarify is [one useful scope question]. Is that the kind of help you need? I can explain our next step here if useful.”
Use this when the request clearly fits your offer. For example, a cleaner can ask whether the author needs a one-off deep clean or a recurring service. An electrician can ask about the requested work without attempting a remote diagnosis.
Mention actual availability only after checking it. “We can definitely come today” creates an expectation that a template cannot verify. The local service playbook explains the broader qualification workflow.
Template 2: a renovation request with incomplete scope
“Hi [name], I handle [type of project] through [business]. Are you planning [scope option A] or [scope option B]? That changes what is involved in an estimate. If it fits our work, I can outline how we assess the project before quoting.”
For a bathroom request, the options might be replacing fixtures or changing the layout. Avoid promising a price before the scope is known. If photos or an address are needed later, ask permission to move into a private discussion.
See the contractor and renovation playbook for buying phrases and project qualification.
Template 3: a property owner looking for management
“Hi [name], I work with [property type] owners in [area] at [business]. Are you looking for ongoing management, leasing help or a handover from another provider? I can share what our service includes so you can compare it with the support you need.”
Keep the question about service scope. Do not ask the author to publish tenant names, access codes or contracts. A tenant complaint is not automatically an invitation to sell management services to the owner.
The property management playbook explains how to distinguish owner requests from rental searches.
Template 4: someone comparing software
“I'm the [role] at [product], so I have a connection here. We support [relevant capability], which may address your [stated requirement]. Our main limitation for your situation is [honest limitation]. Is [one essential requirement] a must-have? Happy to share a short example if useful.”
Answer the stated requirement instead of listing every feature. If an alternative is a better fit, say why. Do not claim integrations or capabilities that are planned but unavailable, and do not turn a competitor complaint into an unverified accusation.
For discovery and qualification, read finding SaaS customers in Facebook groups.
Templates 5 and 6: price questions and a request you cannot take
“The price depends on [two relevant scope factors]. I'm with [business], and we confirm those before quoting. If you share [non-sensitive scope detail], I can explain the estimate process. I don't want to give you a number that changes once the job is clear.”
Use a published rate or range only when it genuinely applies, including what it covers. Avoid treating a request for a price as permission to pressure the person to book.
“I run [business], but we don't cover [area/service] or have capacity for [timeframe]. When comparing providers, it may help to ask about [relevant practical question]. I hope you find someone who fits.”
A useful refusal is better than accepting work you cannot deliver. Recommend another provider only when you have a sound basis, and disclose any referral or affiliate relationship.
Template 7: continuing after permission
“Thanks for saying a message would help. Following up on your [specific request]: here is [the information promised]. To work out whether we can help, the next detail I need is [one relevant question]. If you have already arranged it, no problem.”
Use this after the person agrees to continue privately or asks you to send details. Keep the message tied to that request. If there is no response, do not turn it into a repeated unsolicited sequence.
If you already replied and the author asks a follow-up publicly, answer there when appropriate. A public useful answer can help other members without duplicating the conversation across channels.
Measure useful replies and agreed next steps
Record the original request, why it fits, your reply, permission to continue and the next outcome. Separate a comment, a conversation, a quote and a booked customer. Likes on a reply and many alerts are not evidence of paid work.
Use keyword templates to find suitable requests and webhook routing to assign review. Have one person own each request so multiple team alerts do not create duplicate sales replies.
Find Prospects Now scans selected accessible groups on a schedule through your Chrome session. It cannot guarantee instant discovery or a response from the author. Use the current pricing page to choose a plan after checking your coverage and operating requirements.
