All templates

Automated Portable Sanitation Failed Payment Recovery

When a payment fails in ServiceCore or Stripe, WebRun reads the failure details, drafts a polite recovery email with a clear payment link, and posts the account to your Slack billing channel so your team can review the draft and decide how to follow up before any customer communication goes out.

Runs on WebRun · Strict Lockdown policy
When a payment fails WebRunorchestrates each step
1 ServiceCore detect failed payment on account
2 Stripe read failure reason and outstanding balance
3 Gmail draft recovery email with payment link
4 Slack alert billing team with account details
In short

How do I automatically recover failed payments for portable sanitation rentals?

When a payment fails in ServiceCore or Stripe, WebRun reads the decline reason, drafts a polite recovery email with a payment link in Gmail, and alerts your billing team in Slack. No message reaches the customer until your team reviews and approves the draft, keeping every recovery interaction professional.

  • Every failed payment gets a drafted recovery email within minutes of the failure
  • Billing team is alerted in Slack with the decline reason and account context
  • No recovery message reaches a customer until a human reviews and approves it

Built for portable sanitation billing teams · porta-potty rental operators · sanitation finance managers · field service accounts receivable

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.servicecore.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    ServiceCore - detect failed payment on account
    servicecore.com
    WebRun in ServiceCore: detect failed payment on account
    WebRun opens ServiceCore to detect failed payment on account.
    • Open ServiceCore and navigate to the account with the failed payment
    • Capture the customer name, contact email, invoice number, amount, and date of the failed payment
    • Note whether this is a first failure or a repeat for this account

    Done when Failed payment account details are captured from ServiceCore.

  3. 2
    Stripe - read failure reason and outstanding balance
    stripe.com
    WebRun in Stripe: read failure reason and outstanding balance
    WebRun opens Stripe to read failure reason and outstanding balance.
    • Open Stripe and find the corresponding failed charge
    • Read the decline reason code such as insufficient funds or card expired
    • Confirm the outstanding balance and any retry schedule already in place

    Done when Failure reason and balance details are confirmed in Stripe.

  4. 3
    Gmail - draft recovery email with payment link
    gmail.com
    WebRun in Gmail: draft recovery email with payment link
    WebRun opens Gmail to draft recovery email with payment link.
    • Draft a polite payment recovery email using the customer name and invoice details
    • Include a clear explanation of the failed payment and a direct link to update payment details
    • Adjust the tone for repeat failures versus a first-time decline
    • Save as a draft - do not send until the billing team reviews and approves

    Done when Recovery email draft is saved in Gmail, ready for billing team review.

  5. 4
    Slack - alert billing team with account details
    slack.com
    WebRun in Slack: alert billing team with account details
    WebRun opens Slack to alert billing team with account details.
    • Post the failed payment details to the Slack billing channel
    • Include the customer name, amount, failure reason, and whether a repeat failure has occurred
    • Note that the Gmail draft is ready for team review before sending

    Done when Billing team is alerted in Slack with the account details and a link to the Gmail draft.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.servicecore.com
ScheduleRuns automatically on this cadence
When a payment fails
DeliveryHow each run's result reaches you
Payment alert · Slack
OutputWhat each run produces - A Slack billing alert plus a Gmail recovery email draft for each failed payment.
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

Will it email the customer about the failed payment automatically?

No. WebRun drafts the recovery email and saves it in Gmail for your billing team to review. No email is sent to the customer until a team member approves and sends it.

How does it know why the payment failed?

It reads the decline reason code directly from Stripe, such as insufficient funds, card expired, or card declined, and includes that context in the Slack alert and the Gmail draft.

What if the customer updates their payment and the charge succeeds on retry?

The workflow is triggered by a failed payment event. If a retry succeeds, your billing team will see the resolved status in Stripe and can discard the Gmail draft without sending.

Put this on autopilot.

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