Automated Auto Detailing Failed Payment Recovery
Every morning, WebRun checks Urable and Stripe for failed or unpaid payments from the past 7 days, drafts a polite payment recovery message for each affected customer, queues those messages for your review, and posts an outstanding balance summary to Slack.
How do I automatically follow up on failed auto detailing payments?
WebRun checks Urable and Stripe every morning for failed or unpaid invoices from the past week. For each one it reads the failure reason from Stripe, drafts a polite recovery SMS via Twilio and an email via Gmail, and queues both for your approval. A Slack summary ranks outstanding balances by value so you tackle the biggest ones first.
- Failed payments are caught and followed up within 24 hours
- Failure reason from Stripe guides the customer to the right fix
- Largest outstanding balances are surfaced first for priority follow-up
Built for auto detailing shops · ceramic coating studios · mobile detailers · car care businesses
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
app.urable.comin a real browser with your saved login - no setup, no API keys. -
1
Urable - find unpaid or failed invoices
urable.com
WebRun opens Urable to find unpaid or failed invoices. - Open Urable and filter invoices to unpaid or payment failed status
- Capture customer name, invoice amount, service date, and contact details for each
- Note how many days the payment has been outstanding
- Exclude any invoice already in dispute or written off
Done when All outstanding invoices from the past 7 days are listed with amounts and contact details.
-
2
Stripe - check failed payment status
stripe.com
WebRun opens Stripe to check failed payment status. - Open Stripe and check the payment intent or charge status for each failed transaction
- Identify whether the failure was due to insufficient funds, an expired card, or a bank decline
- Note the failure reason so the recovery message can suggest the right next step (update card vs. try again)
Done when Each failed payment has a failure reason captured for use in the recovery message.
-
3
Twilio - draft recovery SMS for review
twilio.com
WebRun opens Twilio to draft recovery SMS for review. - Draft a brief, polite SMS for each customer with a mobile number on file
- Reference the service, the amount due, and a simple action step (e.g. a payment link or a number to call)
- Queue as a draft for your approval before sending
- Never charge or retry a card automatically
Done when Recovery SMS drafts are queued for every failed-payment customer with a mobile number.
-
4
Gmail - draft recovery email for review
gmail.com
WebRun opens Gmail to draft recovery email for review. - Draft a recovery email for customers who prefer email contact
- Keep the tone professional and friendly; include the invoice details and a payment link
- Save as a Gmail draft for your review before sending
- Never charge or retry a card automatically
Done when Recovery email drafts are saved in Gmail for every eligible email-preference customer.
-
5
Slack - post outstanding balance summary
slack.com
WebRun opens Slack to post outstanding balance summary. - Post an outstanding balance summary to your owner or finance channel
- List each unpaid invoice with customer name, amount, days outstanding, and failure reason
- Sort by amount descending so the largest balances are addressed first
Done when Owner has an outstanding balance snapshot in Slack sorted by value.
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 retry the charge or contact the customer automatically?
No. WebRun drafts recovery messages for your review and never retries a charge or sends a message on its own. Every customer communication and payment action requires your explicit approval.
How does it know why the payment failed?
It reads the failure code from Stripe (such as insufficient funds or expired card) and includes a tailored action step in the draft message so the customer knows exactly what to do.
What if a customer already paid by another method?
It reads live invoice status from Urable each run, so any invoice that has been marked paid or settled is automatically skipped and removed from the outstanding list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.