Community Lead Radar Setup SOP

SOP: Community Lead Radar Setup

Purpose: Set up the monitoring workflow that finds relevant Facebook/community posts, captures the post, drafts a response, and sends the response to Nick or the client for approval before anything is posted.

This is a setup and operating SOP. It is not a sales page.

Outcome

A client is ready for Community Lead Radar when these pieces exist:

• Approved source list: Facebook groups or other local community sources to monitor
• Service keyword map: what terms and buying-intent phrases to search
• Disqualifier list: what to ignore
• Response style guide: how replies should sound
• Opportunity log: where captured posts are stored
• Approval channel: where draft replies are sent for approval
• Posting rule: who posts the approved response

Hard rules

1. Monitor only sources the client, Nick, or Tekton is allowed to view.
2. Do not join groups, react, comment, DM, follow, invite, report, or take any visible Facebook action unless explicitly approved.
3. Do not auto-post.
4. Do not auto-DM.
5. Do not scrape member lists or profiles.
6. Capture only the post context needed to evaluate the opportunity.
7. If a group rule forbids business replies, mark that source as hold or reject.
8. If Facebook shows suspicious activity, checkpoint, or restriction warnings, stop and notify Nick.
9. Every response draft requires approval before posting.

Required inputs from the client

Collect these before setup:

• Business name
• Website
• Service area cities/towns
• Primary services to watch for
• Services to ignore
• Seasonality notes
• Best contact path: phone, booking link, form, or contact page
• Preferred reply tone
• Who approves replies
• Approval channel: Telegram, Discord, SMS, email, or GHL conversation
• Facebook group URLs or community source URLs
• Whether the client is already a member of each group
• Competitor names to avoid mentioning
• Disallowed language or offers
• Proof points we can safely mention

Step 1: Create the client radar workspace

Create one workspace per client.

Recommended folder shape:

community-lead-radar/
  clients/
    client-slug/
      intake.md
      sources.md
      keywords.md
      response-style.md
      disqualifiers.md
      opportunities.csv
      weekly-summary.md

If using Google Sheets instead of files, create one sheet with these tabs:

• Intake
• Sources
• Keywords
• Disqualifiers
• Opportunities
• Weekly Summary

Step 2: Build the source list

For each Facebook group or community source, record:

• Source name
• Source URL
• Platform
• City or service area
• Access status: client member, Nick member, Tekton access, no access
• Group rules summary
• Allowed action: monitor only, client can reply, Tekton can reply with approval, hold
• Relevance score: high, medium, low
• Notes

Use a source only if:

• It has recent local recommendation or project-request posts
• It covers the client service area
• The client or approved account can view it cleanly
• The rules do not clearly ban relevant recommendations or business replies

Reject or hold a source if:

• Access requires unapproved joining
• The group is mostly spam
• The group is political, sensitive, or high-conflict
• The rules forbid contractor/business replies
• The posts are outside the client service area

Step 3: Build the keyword map

Create keywords from the client’s actual services and buyer language.

Use three groups:

Service terms

Examples:

• landscaping
• hardscaping
• patio
• pavers
• retaining wall
• drainage
• deck
• fence
• concrete
• remodel
• roof
• plumber
• electrician
• HVAC

Buying-intent phrases

Examples:

• looking for
• need someone to
• any recommendations for
• who do you recommend
• does anyone know a
• ISO
• estimate
• quote
• contractor recommendations
• help with

Negative terms

Examples:

• hiring
• job seeker
• DIY only
• free
• complaint only
• outside service area
• vendor promo

Step 4: Set the search pattern

For each approved Facebook group:

1. Open the group.
2. Use Facebook group search.
3. Search the service terms and buying-intent phrases.
4. Sort or filter by recent when possible.
5. Review only recent posts within the agreed scan window.
6. Capture likely opportunities in the opportunity log.

Default scan window:

• Daily or weekday scan: posts from the last 24-48 hours
• Weekly scan: posts from the last 7 days

Do not inspect comments unless the post itself is unclear and the comments are needed to understand whether it is a real opportunity.

Step 5: Capture each opportunity

Minimum fields for the opportunity log:

• found_at
• client
• source_name
• source_url
• post_url
• post_age
• author_display_name, if visible
• post_snippet
• matched_service
• matched_keyword
• city_or_area
• lead_score
• suggested_reply
• risk_notes
• approval_status
• decision_by
• decision_at
• posted_by
• posted_at
• notes

Use the post URL whenever possible. If the platform does not provide a clean URL, capture enough source/date/context to find it again.

Step 6: Score the post

A lead

Use when:

• The person is actively asking for a service the client offers
• The location matches the service area
• The post is recent
• The request is specific enough to reply naturally
• The client has a clear next step

Action: send for approval quickly.

B lead

Use when:

• The post is relevant but vague
• Timing or location is unclear
• The request might be a related service
• A soft helpful reply could make sense

Action: send if decent, or include in a digest.

C signal

Use when:

• It is useful market intel but not worth replying
• People are discussing pricing, competitors, demand, or pain points
• There is no clear response opportunity

Action: log only or include in weekly summary.

Reject

Use when:

• Vendor spam
• Job seeker
• Outside service area
• Old post
• Unrelated topic
• Complaint thread where replying would look opportunistic
• Sensitive legal, medical, political, or personal issue
• The group rules make replying risky

Step 7: Draft the response

Good response rules:

• Sound local and human
• Keep it short
• Answer the request directly
• Avoid hype
• Avoid canned sales language
• Ask one useful clarifying question when helpful
• Mention the client only when natural
• Respect group rules
• Do not make price, timeline, warranty, license, or availability claims unless confirmed

Avoid:

• “DM me” as the whole reply
• Generic agency copy
• Over-polished sales language
• Repeating the same template in every group
• Aggressive urgency
• Unsupported claims
• Posting links when the group rules discourage links

Step 8: Send the approval packet

Send this format to Nick or the client:

Community Lead Radar opportunity

Client:
Group/source:
Post URL:
Post age:
Matched service:
Lead score: A/B/C
Why it fits:
Risk notes:

Post snippet:
"..."

Suggested reply:
"..."

Reply options:
APPROVE
EDIT: [notes]
SKIP

Nothing gets posted until the approval decision is recorded.

Step 9: Post or hand off the approved reply

Default V1 rule:

• The client posts the approved response themselves.

If client-posting mode is active:

1. Send the approved copy.
2. Include the post URL.
3. Tell the client to paste the reply exactly or send edits back first.
4. Mark the opportunity as handed off.

If Tekton-managed response mode is explicitly approved:

1. Post only the exact approved copy.
2. Do not improvise in the thread.
3. Record who posted it and when.
4. Capture the final posted URL or confirmation note.

Step 10: Weekly summary

Send or store a weekly summary with:

• Sources scanned
• Opportunities found
• A/B/C counts
• Replies approved
• Replies skipped
• Posts handed to client
• Posts Tekton replied to, if applicable
• Common services requested
• New keyword ideas
• Sources to add, keep, pause, or remove

Setup QA checklist

Before the client is marked active:

• Intake is complete
• Approved source list exists
• Each source has access status and rule notes
• Keyword map exists
• Negative keywords/disqualifiers exist
• Response style guide exists
• Opportunity log exists
• Approval channel is confirmed
• Posting rule is confirmed
• Test search was run in at least one approved group
• At least one sample approval packet was drafted
• Nick or the client approved the workflow

Example setup

Client: hardscape contractor

Service terms:

• patio
• pavers
• retaining wall
• outdoor living
• drainage
• walkway

Buying-intent phrases:

• looking for someone
• recommendations for
• need a contractor
• quote for
• backyard project

Reject terms:

• job opening
• hiring
• DIY
• free materials
• complaint only

Sample captured post:

Looking for someone to redo our backyard patio this summer. Any recommendations?

Lead score: A

Suggested reply:

If you are still looking, [Client Name] handles patio and outdoor living projects around [City]. Are you looking for design help too, or mostly someone to install from a plan?

Approval packet gets sent before that reply is posted.