Set up recovery email and review your campaign

Recovery email uses a per-business managed From address with an honest Business via Porchlight identity. This setup is not a connection to your personal Gmail or Outlook inbox. Guided setup helps establish the managed route; you approve the displayed identity and mailbox, confirm recipient permission, and approve the follow-up content and schedule.

Establish the sender path

1. Open Recovery and choose Approve and test your recovery email route as the signed-in business owner with a verified owner email.
2. Review the From name, managed address, reply owner, and notification/test recipient. The controlled test and notification recipient use the current verified owner email.
3. When administrator configuration is ready, confirm mailbox ownership and choose Approve identity.
4. Choose Send test to my verified mailbox. Reply from that mailbox with the code in the test email, then Refresh test status.

The test targets the owner, never an imported customer. Readiness requires confirmed delivery and the correlated owner reply, not provider acceptance alone. A changed owner or identity requires fresh approval. If the page says tests are disabled or configuration is unavailable, request guided setup assistance; the administrator handles the managed domain, receiving route, and webhook configuration. Do not change DNS based on guessed records.

An unknown or dispatching test needs reconciliation. Do not repeatedly resend. The owner test does not enable customer outreach: customer sending and automatic enrollment also depend on separately approved deployment configuration. Follow the readiness shown in your account; a saved rule is not proof that sending is active.

Review the finite inquiry rule

Open Recovery and choose Preview and approve your inquiry follow-up rule. This rule follows up after the business has answered and the customer has gone quiet; it is not an unlimited drip campaign.

1. Confirm the organization timezone, working days, sending window, and first-touch delay in business days after known activity. Defaults start at Monday–Friday, 09:00–17:00; confirm they fit your business.
2. Choose one, two, or three messages. Later delays use calendar days after the actual accepted first touch. Confirm those delays rather than treating preview dates as delivery guarantees.
3. Select eligible sources. For imported records, select CSV and deliberately choose whether to include the existing backlog.
4. Edit every subject and message. Supported context placeholders are {name} and {project}. Include only facts and next steps your team can offer.
5. Choose Preview actual recipients and dates. Check each recipient, reviewed project, exclusions, expanded message text, and schedule. Confirm the preview before approving and enabling the rule. Editing the rule clears the preview and confirmation, so preview again.

Old quiet inquiries start no sooner than the next working day; there is no burst of historical catch-up messages. A missed local sending day pauses work for owner review. Replies, help requests, outcomes, suppression, and owner handoff stop the sequence. Disable inquiry rule stops matching scheduled follow-up; an already-started provider request may still deliver.

For a single reviewed inquiry, its conversation also offers an editable Subject and Approved message, followed by an email preview and Send approved email when authorized and configured. Review the exact recipient and facts before sending. Provider acceptance and confirmed delivery are different statuses; neither guarantees a customer response.

Keep the team ready

Agree who will monitor owner alerts and take over replies before outreach starts. Personal inbox replies and calls are not synchronized. See Replies, notifications, and opt-outs.

For a blocked sender or unclear campaign preview, include the page, visible readiness/status, and what you expected. Never include mailbox passwords, API keys, or verification codes. Get recovery setup help.