Once AccuLynx is connected (see the Setup Guide above), the interesting decisions are which AccuLynx moments to mail off of, and whether you're mailing the customer themselves or the neighborhood around a job. This guide covers both, with the roofing/exterior-contractor use cases AccuLynx customers ask about most.
Two very different actions: know which one you're building
Mail to Recipients (Contact-based): sends a card directly to the AccuLynx Contact tied to the job — the homeowner. Use this for anything relationship-facing: thank-yous, review requests, referral asks, upsell offers to a past customer.
Radius Mail (Job-based): sends cards to other addresses near the job site, not the customer. This is neighbor marketing — "we just finished a roof on your street" — built off the Job's validated site address and a radius you configure. Use this to turn a single completed job into local brand awareness and new-lead generation.
These pull from different AccuLynx entities under the hood (Contact vs. Job), which is why LettrLabs asks you to pick the action before it shows you filter options — the filters that matter for "mail the customer" (contact and their job history) are different from the filters that matter for "mail the neighborhood" (the job itself: its trade type, category, and completion status).
Job-completion neighbor campaigns (Radius Mail)
The classic AccuLynx use case: a roofing or exterior job finishes, and you want yard-sign-style visibility to convert into direct mail reach around that address.
Filter Jobs on job completed date (for example, completed in the last 7–14 days) so the mailer goes out while the work — and any visible curb appeal — is still fresh.
Narrow by job trade type or job category (e.g., only Roofing jobs, not gutters or siding) if your card creative or offer is trade-specific.
Set a radius that matches how visible the job realistically is from the street — tight radii for interior-only work, wider radii for full roof replacements or exterior remodels.
Post-completion contact follow-up (Mail to Recipients)
Thank-you / review request: filter Contacts on jobs where job completed date is recent and job current milestone reflects a finished job, and send a thank-you card with a review link a few days after completion.
Approved-estimate follow-up: filter on job approved date (and optionally job approved value, to route higher-value jobs to a premium card) to reinforce the relationship right after a customer signs off on an estimate — before the crew even shows up.
Invoice-triggered referral ask: filter on job invoiced date to send a referral or loyalty offer once billing closes out a job, when satisfaction is typically highest.
Contact-based automations can combine a contact's own fields with their related job's fields in one filter (for example, "Contacts with a job where trade type is Roofing AND completed date is in the last 30 days") — use the compound job filter in the filter builder to express this instead of trying to filter Jobs and Contacts separately.
Mind the sync cadence, not just the trigger date
AccuLynx data reaches LettrLabs on a scheduled sync, not the instant a milestone changes in AccuLynx. Build in a buffer — don't assume a job marked "Completed" in AccuLynx this morning is mailable within minutes. Check the integration's last sync date before assuming a time-sensitive campaign (like a fast neighbor mailer) has picked up the newest jobs.
Let address validation work for you
Jobs and Contacts are automatically run through address validation after each sync. For Radius Mail especially, this matters twice over — once for the job site address the radius is centered on, and once for every neighboring address LettrLabs mails around it. Give a sync time to fully process before pulling a recipient preview if you're troubleshooting an unexpectedly low count.
Preview before you commit spend
Always use Calculate Preview after building your filters, for both actions. It's easy to under- or over-scope a job-based filter (e.g., forgetting to bound the completed-date range) and end up mailing a much larger — or smaller — set than intended. Layer in suppression lists for existing customers you don't want re-targeted with a neighbor campaign that's really meant for new-lead generation.
Start narrow, then widen
Because Job and Contact filters can combine trade type, category, milestone, and date range, it's tempting to build one broad "mail everything" automation. Start with one clear trigger (e.g., completed Roofing jobs only) and one clear action, confirm the recipient volume and response make sense, then add trade types or widen date ranges — rather than debugging a single automation with five stacked conditions.
Unverified: the job-completion and contact-follow-up scenarios above are grounded in the actual AccuLynx Job/Contact fields and filters available in LettrLabs (job completed/approved/invoiced date, current milestone, trade type, category, and the Contact/Job entity split between Mail to Recipients and Radius Mail). They have not been validated end-to-end against a live, connected AccuLynx account — no such sandbox was available while drafting this article — so recipient counts, sync timing, and the exact on-screen filter labels should be double-checked against a real connection before this is published.
Want help picking a first AccuLynx trigger to test? Reach out to our team — we're happy to help you scope a first campaign and card design.