Invalid emails, absences and contact changes
Handle bounces, out-of-office replies, and contact proposals without sending to the wrong person.
Updated
In short
A hard bounce invalidates an address and can suspend the case until a contact is found. An individual out-of-office reply follows separate handling: the absent contact is never removed, a return date can delay communication, and a named replacement requires approval before addition. Sensitive contact changes therefore remain visible in a task instead of applying silently.
Expected result
The account keeps reliable contacts and its next communication respects absence, replacement, and approval.
Before you start
- Open the delivery event or original out-of-office email.
- Verify every proposed address directly in the received text.
Procedure
- For a bounce, open the contact and confirm the rejected address.
- Disable or replace it only from verified information.
- For an absence, note the return date and any named replacement.
- Review the contact-change task and approve only an exact proposal.
- Then check date and recipients of the next communication.
What Billabex does
Billabex distinguishes individual automatic replies from platform messages. An extracted replacement must appear verbatim in the email and still needs approval; the absent contact stays because they may return.
If the result is not what you expected
- Without replacement or usable return date for the sole contact, Billabex opens a contact task.
- A usable return date moves sending to the next business day after return.
- When all recipients are absent simultaneously, the system does not yet consolidate those absences into one blocker.