The short answer
Evaluate follow-up software by walking one real estimate through import, permission checks, draft approval, delivery, reply handling, and suppression. Verify production behavior rather than relying on a demo. Ask about message limits, additional costs, export options, and who owns the next homeowner response.
Test the record lifecycle, not just the message editor
A polished message editor does not prove that duplicates are prevented or that a reply stops the next send. Request a walkthrough that includes a revised estimate, an opt-out, a wrong contact, and an owner pause.
Use a test contact you control, not a homeowner, when validating live delivery. Separate an interactive preview from production evidence. Check what is documented and what still requires configuration.
- Import and correct one estimate without creating duplicates.
- Review separate SMS and email permissions.
- Approve the actual recipient and message.
- Verify that replies and stop requests block queued follow-ups.
Ask exactly what can happen without you
Who can change a price, confirm a visit, or restart a paused record? Those permissions should be explicit. A tool should not infer authorization for commitments from a homeowner clicking “interested.”
Check how notifications reach the responsible person, what happens if delivery fails, and how the owner can inspect message history. Clarify whether a supported integration is actually configured for your account.
Understand total cost and exit options
Ask for the subscription price, message allowances, usage costs, onboarding effort, and any cancellation terms in writing. Do not assume “monthly” means unlimited texting or unlimited contacts.
For Fencepost, the public plan is $197 per month, with message-volume allowances and any SMS costs to be confirmed before signup. The public microsite previews a workflow and does not take payments. Ask how you can export records and retain suppression history if you leave.
A practical example
A question worth asking in a demo
“If this homeowner replies five minutes before the next scheduled reminder, show me where the reminder is blocked, who gets the conversation, and how I can see the record of what happened.”
Evaluation guidance, not a claim that an untested system passes this scenario. Confirm it in the production setup you will actually use.