All templates

Automated Held Ticket Release Plans

Each afternoon, WebRun opens FEARTICKET, finds peak nights that are sold out or nearly sold out, reviews the held, comp, and staff-hold inventory sitting on each time slot, proposes how many of those held tickets are safe to release, logs the plan to Google Sheets, and pings you in Slack to approve before anything is put back on sale.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every day at 1:00 PM WebRunorchestrates each step
1 FEARTICKET find sold-out nights and held inventory
2 Google Sheets log the proposed release
3 Slack ask you to approve the release
In short

How do I safely release held tickets on sold-out haunted house nights?

Each afternoon, WebRun finds sold-out peak nights in FEARTICKET, reviews the held and comp inventory on every time slot, and proposes how much is safe to release while keeping a buffer for staff and press. It logs the plan to Google Sheets and pings you in Slack, so tickets go back on sale only after you approve the release.

  • Unclaimed held tickets on sold-out nights turn into extra sellable inventory
  • Staff, press, and guest-list holds are always protected by a buffer
  • No ticket goes back on sale without your approval

Built for haunted attraction owners · revenue managers · box office managers · Halloween event operators

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

  2. 1
    FEARTICKET - find sold-out nights and held inventory
    fearticket.com
    WebRun in FEARTICKET: find sold-out nights and held inventory
    WebRun opens FEARTICKET to find sold-out nights and their held inventory.
    • Open FEARTICKET and list upcoming peak nights that are sold out or within a few tickets of it
    • For each night, read the held, comp, and staff-hold inventory sitting on every time slot
    • Note how many held tickets remain unclaimed close to the event and which slots have the most demand pressure
    • Do not release or unhold any inventory in FEARTICKET on your own. Leave every change for a person to apply

    Done when Held inventory and demand pressure are captured for each sold-out peak night and slot.

  3. 2
    Google Sheets - log the proposed release
    google.com
    WebRun in Google Sheets: log the proposed release
    WebRun logs the proposed release and buffer in Google Sheets.
    • Open the inventory-release planning sheet in Google Sheets
    • Log each sold-out night and slot with the held count and a proposed number safe to release
    • Leave a buffer for staff, press, and guest-list holds so those are never proposed for release
    • Show the extra revenue each proposed release could unlock at the slot's current price

    Done when A proposed release per slot, with a held-back buffer, is recorded in the sheet.

  4. 3
    Slack - ask you to approve the release
    slack.com
    WebRun in Slack: ask you to approve the release
    WebRun posts the release plan to Slack and waits for your approval.
    • Post the proposed release plan to your Slack channel, ranked by the nights closest to selling out
    • Show each slot's held count, the number proposed to release, and the revenue it could unlock
    • Ask you to approve, adjust, or skip. Only apply a release in FEARTICKET after you say yes

    Done when You have the release plan in Slack and can approve or adjust before any tickets go on sale.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.fearticket.com
ScheduleRuns automatically on this cadence
Every day at 1:00 PM
DeliveryHow each run's result reaches you
Release plan · Slack
OutputWhat each run produces - A per-slot proposal of how much held inventory is safe to release on sold-out peak nights, logged to Sheets and sent to Slack for approval.
Release plan
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 put tickets back on sale without me?

No. WebRun never releases or unholds inventory in FEARTICKET on its own. It proposes a per-slot release in Sheets and Slack, and you approve, adjust, or skip. Tickets go back on sale only after you apply the change yourself.

How does it avoid releasing staff or press holds?

WebRun always leaves a buffer for staff, press, and guest-list holds, so those are never counted in a proposed release. It only suggests unclaimed held tickets that are safe to sell as the night approaches.

How does it decide how much is safe to release?

WebRun looks at each slot's held count, how close the night is, and the demand pressure on that slot in FEARTICKET, then proposes a conservative number and shows the revenue it could unlock so you can judge each one.

Keep going

Related templates

FEARTICKET Automated Confirmation Emails
WebRun reads each new FEARTICKET order, builds a clear confirmation email with the guest's entry window and parking and check-in details, and queues it in Gmail for your box office to approve before it goes out.
FEARTICKET›Gmail›Slack
FEARTICKET Automated Arrival Reminders
A few hours before doors, WebRun pulls tonight's FEARTICKET time slots, drafts a short reminder text for each guest with their arrival window and check-in tips, and queues the batch in Twilio for a manager to approve before it sends.
FEARTICKET›Twilio›Slack
Automated Unsigned Waiver Worklist
Before doors, WebRun matches tonight's FEARTICKET orders against your signed waivers in DocuSign, builds a check-in worklist of who still needs to sign, and posts it to Slack so staff can catch them at the gate.
FEARTICKET›DocuSign›Slack

Put this on autopilot.

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

Deploy this workflow Talk to us