Automated BCC Software Undeliverable Mail Reports
Every night, WebRun opens BCC Software, checks jobs that completed their return-processing window that day, tallies the undeliverable and returned pieces with the top reasons each came back, drafts a client-facing summary email in Gmail naming the counts and reasons, and leaves it unsent for your account manager to review and send.
How do I summarize undeliverable and returned mail for a client after a job runs?
Every night, WebRun opens BCC Software and checks jobs whose return-processing window closed that day. It tallies the undeliverable and returned pieces, groups them by reason such as moved no forward or vacant, drafts a client-facing summary in Gmail, and leaves it unsent for your account manager to review and send the next morning.
- Clients get a return summary the morning after a job closes, not weeks later
- Every draft breaks returns down by reason, not just a raw count
- Nothing reaches a client until an account manager reviews and sends it
Built for lettershops · mailing houses · account managers · direct mail production teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.bccsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
BCC Software - tally undeliverable and returned pieces
bccsoftware.com
WebRun opens BCC Software to tally undeliverable and returned pieces. - Open BCC Software and pull jobs whose return-processing window closed today
- Tally the undeliverable and returned piece count for each job
- Group the returns by reason: moved no forward, vacant, insufficient address, refused
Done when Every closed job has a confirmed return count and a reason breakdown.
-
2
Gmail - draft the client summary
gmail.com
WebRun opens Gmail to draft the client summary. - Draft a summary email to the client with the total returned count and the reason breakdown
- Compare the return rate to the client's last mailing where available
- Save it as a draft and leave it unsent for the account manager to review
Done when A return summary draft sits ready in Gmail for every closed job.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it email the return summary to the client automatically?
No. WebRun only drafts the summary in Gmail and leaves it unsent. Your account manager reviews the counts and clicks send, so nothing reaches a client without a person checking it.
How does it group the return reasons?
It reads the reason code BCC Software assigns to each returned piece and groups them into moved no forward, vacant, insufficient address, and refused, so the client sees why mail came back, not just how much.
Does it wait until every piece is back before summarizing?
No. It summarizes once a job's return-processing window closes for the day, so the client gets a timely report rather than waiting for every last piece to trickle in.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.