# Review Leads and Draft Follow-Up Messages

New enquiries and booking requests can remain unanswered when owners lack a clear follow-up list. This skill prioritizes Reach leads and drafts factual messages for owners to send manually.

## Install

```bash
npx skillstore add locusintelligence-dauagency/lead-follow-up
```

## Metadata

- Status: approved
- Slug: locusintelligence-dauagency-lead-follow-up
- Skillstore revision: r1
- Version status: missing
- Tree hash: d35910f271df86f339707abe09a06151b3341b1f150a10b2a63a0786e8e4708a
- Author: locusintelligence-dauagency
- GitHub username: locusintelligence-dauagency
- License: MIT
- Repository: https://github.com/locusintelligence-dauagency/reach-skills/tree/2b10a6be9b9b9a990ae0beb360a21476fad41918/skills/lead-follow-up
- Ref: 5e1f762ecf28b75c366ed9b67053b444b2eb9ffd
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/locusintelligence-dauagency-lead-follow-up
- Manifest: https://skillstore.pages.dev/api/skills/locusintelligence-dauagency-lead-follow-up/manifest

## Capabilities

- Select an account location and stop when its Google connection is inactive.
- Retrieve merged customer leads or raw booking requests from the Reach website.
- Filter records by status and date range, with retrieval limits up to 200.
- Prioritize new or unviewed requests and display at most 10 records at a time.
- Draft short WhatsApp or SMS messages and email versions when a customer email is present.
- Use recorded names, services, and preferred slots without inventing prices, availability, or missing details.

## Use Cases

- Review Unanswered Enquiries: A local business owner reviews new website leads and selects customers who need a short follow-up draft.
- Prepare Booking Replies: A receptionist reviews booking requests and drafts replies using recorded services and preferred times without claiming confirmed availability.
- Review a Location's Request History: An agency account manager selects a client location, examines its raw booking log, and reports date coverage and retrieval limits.

## Prompt Templates

### List New Leads

```
Show my new Reach leads, with the newest first. Ask which location if needed, and show no more than 10.
```

### Draft a Short Reply

```
Draft a short SMS for the lead I select. Use only recorded details, ask for a suitable time, and do not send it.
```

### Review Recent Bookings

```
Show raw booking requests for [location] between [start ISO date-time] and [end ISO date-time]. Prioritize unviewed requests and state any coverage limits.
```

### Prepare Multichannel Follow-Ups

```
For [location] and [date range], review new leads and show 10 at a time. Draft SMS and available email versions for leads I select. Use [language], avoid unsupported claims, and disclose retrieval limits. Do not send messages or change statuses.
```

## Limitations

- Requires the hosted Reach MCP server, browser OAuth sign-in, and an active Google connection.
- Reads leads from Reach website booking forms, not every Google Business Profile contact channel.
- Does not send customer messages or change lead statuses; feature requests require separate owner confirmation.
- Phone numbers remain masked, and retrieval limits or returned restrictions can prevent a complete lead list.

## Best Practices

- Confirm the location and date range before reviewing customer records.
- Check returned limitations and missing fields before drawing conclusions or drafting messages.
- Review each draft, keep customer details separate, and send messages manually through the appropriate channel.

## Anti Patterns

- Treating the retrieved list as complete when limits or returned restrictions apply.
- Inventing missing services, prices, availability, addresses, or full phone numbers.
- Requesting automatic message sending or including one customer's private details in another customer's reply.

## Security Audit

- Audited at: 2026-10-10T22:53:19.962\+00:00
- Summary: All 15 static findings are false positives: Markdown backticks, privacy prose, and documented Reach setup URLs do not establish unsafe execution or exfiltration. The workflow limits customer data use, rejects embedded tool instructions, and requires confirmation before submitting a feature request. No evidence found of malicious intent; the hosted MCP server implementation is outside this repository.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0