Keep gunsmith repair customers in the loop
Every morning, WebRun opens FastBound, finds firearms in the gunsmithing bound book whose repair ticket has sat past its expected turnaround, drafts a status update to each owner in Gmail, leaves every message unsent for review, and posts your bench a Slack list of the stalled tickets.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep gunsmith repair customers updated on their firearm?
Every morning, WebRun opens FastBound, finds gunsmith repair firearms past their expected turnaround, and notes the owner, the work, and days on the bench. It drafts a friendly status update to each owner in Gmail, leaves every draft unsent for review, and posts your bench a Slack worklist, so repair customers stay informed without any message going out unapproved.
- Owners of long-running repairs get a status note, drafted and ready
- The oldest bench jobs surface at the top of the list each morning
- No repair update reaches an owner without staff approval
Built for FFL dealers · gunsmiths · gun stores · repair bench staff
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
cloud.fastbound.comin a real browser with your saved login - no setup, no API keys. -
1
FastBound - find stalled repair tickets
fastbound.com How to Automate FastBound
WebRun opens FastBound to find stalled gunsmith repair tickets. - Open FastBound and review the gunsmithing bound book for repair firearms past their expected turnaround
- Capture the owner, the firearm, the work requested, and how many days it has been on the bench
- Skip any ticket already updated in the last few days
Done when Every stalled repair ticket is listed with its owner and days on the bench.
-
2
Gmail - draft owner status updates
gmail.com How to Automate Gmail
WebRun drafts a status update for each owner and leaves it unsent. - Draft a friendly status update to each owner noting the repair is still in progress
- Keep the tone honest and avoid promising a firm completion date
- Save every message as a draft and leave it unsent for review
Done when A status-update draft sits ready in Gmail for every stalled repair.
-
3
Slack - post the stalled tickets
slack.com How to Automate Slack
WebRun posts the stalled repair tickets to Slack. - Post the bench a short list of repair tickets past their turnaround
- Sort by days on the bench so the oldest jobs stand out
- Note that the owner update drafts are waiting in Gmail for review
Done when The bench has today's stalled-ticket list in Slack.
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 email repair customers without me?
No. WebRun drafts each status update in Gmail and leaves it unsent. Your bench reviews every message and clicks send, so no owner is contacted until a person approves it.
How does it know a ticket is stalled?
It reads the gunsmithing bound book in FastBound and flags any repair firearm past its expected turnaround, ranking the list by how many days it has sat on the bench.
Will the same owner get an update every day?
No. It checks FastBound each run and skips any ticket already updated in the last few days, so owners get timely notes without daily repeats.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.