How do you send a postcard when a Follow Up Boss lead changes stage?

Trigger on one named stage and resolve one intended mailing address.

Use the Follow Up Boss person ID as the recipient key. Record the prior and new stage when the connector exposes both. Map the selected mailing address and a reviewed template. Use a stage-event key to stop retries or repeat updates from creating another piece.

Real-estate records often contain both a contact address and a property address. State which one receives the postcard.

  1. Name the stageUse the stage that proves the follow-up moment.
  2. Choose the addressSelect contact mailing address or property address with a written rule.
  3. TestMove a test person through the stage with live release disabled.
  4. Record the resultSave mailpiece ID and exception reason without replaying the trigger.

How do you write mail status back to Follow Up Boss?

Use a note, custom field, or connected activity that preserves the source event ID.

Write accepted, held, failed, or released with the mailpiece ID and event time. Keep operational status separate from response or conversion claims.

If the writeback edits the person, confirm that the stage automation does not re-run.

Follow Up Boss field map

Resolve the address meaning before you map fields. Property location and recipient mailing address are not interchangeable.

Follow Up Boss valueMail fieldRule
Person IDrecipient_keyRequired and stable.
Stagetrigger_reasonUse the exact eligible value.
Contact mailing addresspostal addressUse when the card goes to the person.
Property citypersonalization.property_cityUse as copy, not as the mailing city unless it is the recipient address.
Template keytemplate_idPin a reviewed version.
Note or custom fieldresultKeep out of stage-trigger logic.

Preflight checklist

  • 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.

Questions to resolve before launch

Is Follow Up Boss stage change available in every connector?

Do not assume it is. Confirm the exact trigger, polling behavior, and available fields in the connection you will use.

Which address should receive the postcard?

Choose the contact mailing address unless the documented workflow intentionally mails another party. Property address can be personalization data without being the destination.

Is this a native Sendvo connector?

No native Follow Up Boss connector is claimed.

Sources and review notes

  1. Follow Up Boss: Changing a lead stageOfficial stage behavior.
  2. Follow Up Boss: AutomationsOfficial automation documentation.
  3. Follow Up Boss API documentationOfficial API record and event reference.

Product plans, trigger names, and connector access can change. Check the linked documentation and your account before production use. Sendvo last reviewed these sources on August 31, 2026.