The short answer
A useful estimate follow-up text identifies your fence company, references the actual project, and asks one easy question. Keep it conversational, avoid unapproved price or scheduling promises, and use SMS only when the required permission and messaging requirements are met.
Use this after the estimate—not as a cold text
This example is for a homeowner who already requested a fence estimate and whom you are authorized to text. It is not outreach to purchased lists or a way to infer permission from an imported phone number.
The FCC’s consumer guidance discusses consent for robotexts and the ability to revoke it. Requirements depend on the message and sending method; a request for an estimate is not a blanket compliance determination. Confirm your process with your provider and qualified counsel where needed.
Personalize the useful parts
Replace every bracketed field before sending. Use a real company name and a short project reference the homeowner will recognize, such as the backyard privacy fence. Avoid including the full home address or unnecessary personal details in a short message.
- Check the recipient, current estimate, and permission.
- Use one question rather than several competing asks.
- Review the wording as the business owner.
- Include the required opt-out language and honor stop requests.
Any reply changes the workflow
A question about gates is a conversation, not permission to keep sending reminders. Pause the sequence and let the owner respond with the correct scope details. If the homeowner asks to stop, suppress further outreach rather than switching channels to work around the request.
This sample is message-body guidance, not a complete SMS compliance program. Sender registration, provider rules, sending windows, and applicable law still need review before live delivery.
A practical example
SMS body example
Hi [First name], it’s [Your name] at [Company]. Just checking on your [project] estimate. Is there a question I can help with? Reply STOP to opt out.
Illustrative text, not a legal safe harbor. Replace bracketed fields and verify permission before sending.