All templates

Automated Junk Removal Failed Payment Recovery

When a payment failure is detected in Jobber or Stripe for a completed junk-removal job, WebRun drafts a polite recovery email for the customer with the failed amount and a direct payment link, saves the draft in Gmail for owner review before sending, and fires a Slack alert to your team so the recovery attempt happens within hours, not days.

Runs on WebRun · Strict Lockdown policy
Within minutes of each payment failure WebRunorchestrates each step
1 Jobber detect failed or declined payment
2 Stripe confirm failure and get payment link
3 Gmail draft courteous recovery message
4 Slack alert team to failed payment
In short

How do I automatically recover failed payments for junk-removal jobs?

When a payment fails in Jobber or Stripe for a completed junk-removal job, WebRun reads the decline reason, drafts a courteous recovery email with a direct payment link in Gmail, saves it unsent for your review, and fires a Slack alert with a link to the draft so your team recovers the revenue within hours of the failure.

  • Failed payments are caught and queued for recovery within minutes, not days
  • Decline-reason-aware messaging improves payment recovery rates
  • No card is ever charged or retried without explicit customer action

Built for junk removal business owners · hauling company finance teams · junk-removal admins · field service billing managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.getjobber.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Jobber - detect failed or declined payment
    getjobber.com
    WebRun in Jobber: detect failed or declined payment
    WebRun opens Jobber to detect failed or declined payment.
    • Open Jobber and check for invoices with a Failed or Declined payment status
    • Capture the customer name, email, invoice number, job type, and failed amount for each
    • Note whether this is a first failure or a repeated decline

    Done when Every failed payment has been identified with the customer and invoice details.

  3. 2
    Stripe - confirm failure and get payment link
    stripe.com
    WebRun in Stripe: confirm failure and get payment link
    WebRun opens Stripe to confirm failure and get payment link.
    • Cross-reference the failed payment in Stripe to get the decline reason code
    • Retrieve or generate a direct payment link the customer can use to retry
    • Note whether the card was declined, expired, or insufficient funds to inform the recovery message tone

    Done when Each failed payment has a confirmed decline reason and a direct retry payment link.

  4. 3
    Gmail - draft courteous recovery message
    gmail.com
    WebRun in Gmail: draft courteous recovery message
    WebRun opens Gmail to draft courteous recovery message.
    • Draft a courteous payment recovery email for each customer with the job reference, failed amount, and direct payment link
    • Adjust the tone slightly based on the failure reason: a lighter note for technical declines vs. a helpful nudge for insufficient funds
    • Save every draft unsent in Gmail for owner review before any email reaches the customer

    Done when A tailored recovery email draft exists in Gmail for every failed payment.

  5. 4
    Slack - alert team to failed payment
    slack.com
    WebRun in Slack: alert team to failed payment
    WebRun opens Slack to alert team to failed payment.
    • Post a Slack alert to your finance or ops channel with the customer name, amount, decline reason, and a link to the Gmail draft
    • Flag repeat declines separately so the team can consider a phone call for those accounts

    Done when Team has a Slack alert for every failed payment with a link to the ready recovery draft.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.getjobber.com
ScheduleRuns automatically on this cadence
Within minutes of each payment failure
DeliveryHow each run's result reaches you
Recovery drafts · Gmail + Slack
OutputWhat each run produces - Payment recovery email drafts in Gmail per failed transaction, plus a Slack alert per failure with decline reason and draft link.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it send the recovery email to the customer automatically?

No. WebRun drafts the recovery message in Gmail and leaves it unsent. You receive a Slack alert with a direct link to the draft so you review and send it yourself, keeping full control over every customer communication.

Does it retry charging the card without permission?

No. WebRun never initiates a charge or retry. It only reads the failure details and generates a payment link for the customer to use voluntarily when they are ready to pay.

What happens with repeat declines on the same invoice?

Repeat declines are flagged separately in the Slack alert so your team knows to consider a personal phone call rather than another automated email.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.