FireRock Playbook

Mailbox Power: what it is, and how we use it

A direct-mail automation tool that fires a physical postcard from your CRM. This walks through the model running in the Empire Roofing account and how to set it up on another client.

Internal reference. Example verified live in the Empire Roofing sub-account.
On this page

1What Mailbox Power is

Mailbox Power is a direct-mail and print-on-demand platform. Instead of designing and mailing postcards by hand, an automation drops a contact into Mailbox Power and it prints and mails the physical piece for you.

The whole point is CRM-triggered physical mail. A CRM event (new lead, job won, website visit, birthday, dormant customer) can automatically send a real postcard, greeting card, letter, or gift to that person's mailing address.

What it can send

  • Postcards and letters
  • Greeting and thank-you cards
  • Gifts and gift cards

How it is triggered

  • From a CRM automation (our case: GoHighLevel)
  • Based on a tag, a stage move, or a new contact
  • On a schedule or one-off list upload
It sits in the same category as Thanks.io, PostPilot, and SendJim. The advantage over doing mail manually is that it is fully automated from CRM data, so mail behaves like an email step in a workflow.

2Why it is useful (local service and roofing)

Physical mail cuts through where inbox and SMS are crowded, and it does not carry the consent and carrier rules that SMS does. Common plays:

PlayTriggerPiece
New-lead welcomeLead createdIntro postcard
Post-job thank-youJob marked won or completeThank-you card
Review request by mailJob complete plus a waitCard with review QR or link
Win-backNo activity in X monthsOffer postcard
Around-the-job mailerJob addressNeighbor postcard
Website-visitor retargetingAnonymous visit identified with an addressPostcard to the visitor

That last one is the model running in Empire Roofing, and it is the most interesting because it turns anonymous web traffic into mailable prospects.

3How it connects to GoHighLevel

Mailbox Power is connected to the sub-account through GoHighLevel's integrations, which adds a workflow action you can drop into any automation. In the builder it shows up as an "Add Contact" action with the Mailbox Power icon.

Inside that action you do two things:

  1. Map the recipient fields from the GoHighLevel contact (name and mailing address) into Mailbox Power using merge fields.
  2. Pick a Contact Group. The group is the Mailbox Power campaign that holds the actual design and the send rules. Adding the contact to that group is what triggers the print and mail.
Mental model: the GoHighLevel workflow decides who and when. The Mailbox Power Contact Group decides what gets mailed. The "Add Contact" action is the bridge between the two.

4The Empire Roofing model (live example)

Workflow name: siteid visit >mailboxpower. It turns identified website visitors into mailed postcards, fenced to the service area. Here is the exact flow.

Trigger: Contact Created
A visitor-identification pixel ("siteid") de-anonymizes a website visitor and creates a GoHighLevel contact that includes a real mailing address.
↓
Condition: who qualifies
A three-way split checks the visitor's location and tags.
↓
In service area State = MN
Tagged as a site visitor and in the target state.
↓
Add Tag
Marks the contact for tracking.
↓
Mailbox Power: Add Contact
Pushes the contact into Mailbox Power Contact Group 204964. Mailbox Power prints and mails the postcard to that address.
Wrong city
Tagged a site visitor but outside the service area.
↓
Add Tag only
No mail is sent.
↓
End

A third "None" branch simply ends for anyone who matches no condition.

The field mapping on the Add Contact action

The Mailbox Power action pulls these straight from the GoHighLevel contact:

Mailbox Power fieldGoHighLevel value
Contact Group204964 (the mail campaign)
First Name{{contact.first_name}}
Last Name{{contact.last_name}}
Company{{contact.company_name}}
Street{{contact.address1}}
City{{contact.city}}
State{{contact.state}}
Postal Code{{contact.postal_code}}
Country / Email{{contact.country}} / {{contact.email}}
Status: this workflow is currently a draft with about 30 test contacts enrolled. Nothing mails until it is published.

5How to set it up on another client

  1. Connect Mailbox Power to the sub-account (via the integration / app connection) so the "Add Contact" action becomes available in the workflow builder.
  2. Build the mail piece in Mailbox Power and note its Contact Group ID. That group holds the design and send rules.
  3. Pick an address source. The contact must have a real mailing address. Options: a visitor-ID pixel like the "siteid" tool, a form that collects address, or job or opportunity data.
  4. Build the workflow: trigger on the address source (Contact Created, tag added, or stage move) then add a Condition to fence by service area (State or City) so you do not mail out-of-area.
  5. Add the Mailbox Power "Add Contact" action on the qualifying branch, map the address merge fields, and select the Contact Group.
  6. Test, then publish. Run a test contact, confirm it lands in the Mailbox Power group, then turn the workflow on.

6Things to watch

  • Address quality. Mail only works with a clean, complete address. Garbage in, wasted postage out. Filter to contacts that actually have street, city, state, and postal code.
  • Cost per piece. Each mailer costs real money (print plus postage), unlike an email step. Fence tightly by geography and intent.
  • Frequency and dedupe. Make sure the same person cannot be enrolled repeatedly. Use a tag to mark "already mailed."
  • Draft versus live. A draft workflow enrolls but does not send. Confirm the intended state before assuming mail is going out.
  • Visitor-ID accuracy. Identified-visitor data is probabilistic. Expect some mismatches and keep the service-area filter strict.

7Glossary

Print-on-demand mailThe vendor prints and posts each piece individually, triggered by data, with no pre-printed stock.
Visitor ID ("siteid")A pixel that identifies anonymous website visitors and resolves them to a person and mailing address, creating a contact.
Contact GroupThe Mailbox Power campaign that holds the mail design and send rules. Adding a contact to it triggers the mailer.
Add Contact actionThe Mailbox Power workflow step inside GoHighLevel that maps address fields and drops the contact into a Contact Group.
FireRock internal reference. General platform details reflect Mailbox Power's positioning; confirm current pricing and features on the vendor site. The Empire Roofing flow was inspected read-only and reflects a draft configuration.