Ticket Monitor

Ticket Monitor watches a connected mailbox for tickets, gigs, or leads, keeps one task record per item so nothing is missed or double-handled, and drafts a reply for you to approve before it ever sends.

What it does

Ticket Monitor checks the connected mailbox on its schedule, or within about a minute when its duty is paired with an email trigger. For every new item it finds, it opens one task record and keeps that same record updated as the item moves along — a follow-up or re-sent email updates the existing record instead of spawning a second one. It drafts a reply for each item, but because sending mail is an external action, the draft is held under Ask-me-first: you approve it with one tap in the dashboard Approvals inbox or on WhatsApp, or edit it before it goes out. On a daily reconciliation duty, it walks its own task records and reports only counts it can actually back up — new, replied, pending approval, closed — rather than a rough guess.

Use cases

• Freelancer inbox — new gig inquiries get logged, screened against a rate floor you've set, and get a drafted reply waiting for one-tap approval.
• Local service business — leads from a contact-form mailbox get filtered by a distance limit before a dispatcher approves the reply.
• Small support inbox — incoming tickets each get one record, so the same customer emailing twice doesn't turn into two open items, and a daily count shows what's genuinely still open.

What to connect in Launchpad

Connect Email in Launchpad — Ticket Monitor needs a connected mailbox to have anything to watch. Pair its duty with an email trigger rather than relying only on a fixed schedule, so new mail gets picked up within about a minute instead of waiting for the next scheduled run.

Setting your criteria

Tell Ticket Monitor what matters for your work in an ordinary chat message — a minimum rate, a maximum travel distance, keywords that should auto-decline, or anything else you screen for. It applies those criteria to every new item going forward, and you can change them in chat at any time without redoing any setup.

Typical duties and schedule

1. Watch duty — fires from the email trigger (about a minute after new mail arrives) or on a fallback schedule; opens or updates one task record per item and screens it against your criteria.
2. Draft-reply step — happens inside the same run; the drafted reply is queued for Ask-me-first approval rather than sent automatically.
3. Daily reconciliation duty — once a day, walks the task records and posts a numbers-only summary of what's new, replied, pending, and closed.

Runs when: email trigger (about a minute) plus a daily reconciliation schedule by default. Duties run at most every 15 minutes if you add a scheduled fallback.

Plan minimum

Ticket Monitor requires a Growth plan or higher; email triggers are available on Growth and above. See pricing for full plan details.

Common questions

Does Ticket Monitor send replies automatically?
No. Every reply is an external action, so it defaults to Ask-me-first — it drafts the reply and waits for one tap of approval on WhatsApp or in the Approvals inbox before anything sends.

How fast does it notice a new email?
Pair its duty with an email trigger and it reacts within about a minute. On a schedule alone, it checks at whatever cadence you set, at most every 15 minutes.

What stops the same ticket from being handled twice?
Each incoming item gets one task record that Ticket Monitor updates in place, so a duplicate or follow-up email updates the existing record instead of creating a second one.

Can I set my own screening rules?
Yes. State your rate floor, distance limit, or decline keywords in chat, and Ticket Monitor keeps applying them until you change them.