Playbook · Investors
Postcards for motivated-seller leads in your CRM
Keep the seller, the property, and the mailing address apart. One record joins the lead ID, proof, duplicate rule, and mailpiece ID.
- Reviewed against primary sources
- Last updated: October 11, 2026
- No setup fees
Personalization
Mention the property. Mail the seller.
Property fields go in the copy. The seller's mailing address stays in its own fields.
Read the investor automation guide
The playbook
How do you send a postcard when a motivated-seller lead enters a CRM?
Trigger only after the lead meets a documented qualification rule.
- QualifyName the status, tag, score, or event that makes the lead eligible.
- Resolve recordsKeep seller, property, and mailing destination as separate objects.
- ReviewRender one proof and inspect every merge field.
- ReleaseApprove the controlled batch or record under the account's current workflow.
Read the full answer
Create a mail candidate from the CRM lead ID, seller contact record, property record, mailing address, trigger reason, and template version. Do not let every imported lead send automatically. Hold the record until required address and duplicate checks pass.
This playbook extends the broader real-estate investor automation guide.
Field map
One record makes every send traceable.
Keep the seller, property, destination, and send decision checkable in one place.
| Record area | Fields | Failure rule |
|---|---|---|
| Lead | CRM lead ID, source, status, trigger time | Hold when qualification is unclear. |
| Seller | Seller ID, name, household key | Check merged or shared records. |
| Property | Property ID, address, city | Fallback copy, or hold. |
| Destination | Recipient name and mailing address | Never silently swap in the property address. |
| Creative | Template ID, version, merge values | Proof the mapped record. |
| Control | Duplicate key, pause state, approval | Never release a held or repeated record. |
| Join | Lead ID, campaign ID, mailpiece ID | Write back before status processing. |
Seller-lead FAQ
Settle these before the first seller.
Pricing it out? See plans and per-piece rates.
Primary sources
- Sendvo: Real estate investor direct-mail automation
- USPS: Address Quality
- Zapier: Direct mail management workflows
Workflow pattern, not a connector claim. Plans: list upload, dedupe, and automated mail need Operator or Growth. Integrations and API access need Growth and connect through a no-code tool or our API. Product plans, trigger names, and connector access can change. Confirm yours before production use.
How do you add a property address and property city to an automated postcard?
Map property fields to copy fields and keep them separate from the destination address. Use property_address and property_city for the message. Use dedicated recipient address fields for mailing. Add fallback copy that removes the location phrase when the property field is missing, or hold the record.
A property can be the subject of the postcard without being the place where the seller receives mail.
How do you prevent the same seller or property from getting duplicate postcards?
Apply both a recipient rule and a property rule to remove duplicate records. Use normalized mailing address or stable seller ID for the recipient rule. Use property ID or normalized property address for the property rule. Hold records that collide and show the earlier source event, date, and decision.
Decide whether two owners at one mailing address count as one household or two eligible recipients.
How do you test a real-estate postcard automation before using paid credits?
Use a named test lead and an explicit non-mailing test path. Run the lead through the actual trigger. Confirm the seller name, destination address, property copy, template version, duplicate key, and returned test status. A preview built from hand-entered values does not test the CRM map.
Stop if the connection cannot prove that the test will not release live mail.
How do you pause a seller-lead postcard automation?
Pause release and keep new leads visible in a held queue. Record who paused it, why, and what happens to new events. Before restart, review held records for age, status changes, duplicates, and outdated offers. Do not bulk-release every held lead without a new eligibility check.
A deleted connection hides the audit trail and can make restart behavior unclear.
How do you keep the CRM record ID connected to the mailed postcard?
Store the CRM lead ID on the mail record and write the returned mailpiece ID back to the CRM. Keep both IDs on every status event and review record. Use the lead ID for the business source and the mailpiece ID for operational joins. Do not use a name or street address as the only join key.
Preserve the mapping after a lead merges or an address changes.
Should the property address always be the mailing address?
No. The property can be the subject of the message while the seller receives mail at another address.
What is the best duplicate key?
Use stable seller and property identifiers when available, plus a source event key. Address-based keys need normalization and household rules.
Can held leads send automatically after a pause?
Only if the team defines and tests that behavior. A safer restart reviews eligibility, age, duplicates, and offer validity first.
Before launch
Preflight checklist before the first live send
- Use one stable source-event ID and save it with the mail record.
- Require recipient name, address line 1, city, state, and ZIP Code before release.
- Set a duplicate rule for the person, household, property, order, or job.
- Render a proof with a test record before any funded send.
- Define who can pause the workflow and who can approve release.
- Store the source record ID, campaign ID, and returned mailpiece ID together.
- Treat mailstream events as operational signals, not proof of attention or revenue.
Build one traceable seller-lead mail record.
Keep the seller, property, destination, proof, duplicate rule, CRM lead ID, and mailpiece ID connected.