# Work the Mailshake Lead Catcher queue from one triage board > A daily triage board for your Mailshake reply queue, with aging, per-rep filters, an AI reply drafter, and one-click push to HubSpot. - Workflow type: app - Services: Mailshake, HubSpot - Categories: Sales - Published: 2026-08-31 ## What it does - Opens to a board of every open lead in Mailshake Lead Catcher, grouped by campaign, showing the prospect, their reply, and how many days it has been sitting unanswered. - Filters by status and by assignee so each rep sees only their own leads, and sorts the oldest replies to the top so nothing rots at the bottom of the queue. - A Draft a reply button sends a background assistant to research the prospect's company and read the sequence they were sent, then writes a tailored reply into the app for the rep to edit and copy. It never sends anything on its own. - Close, ignore, or reopen a lead straight from the detail pane, and push the prospect into HubSpot with the reply text and the research brief attached as a note. ## What you'll need - A Mailshake account with Lead Catcher enabled and at least one campaign collecting replies - A HubSpot login for the Send to CRM button, which works on the free CRM tier - The assignee names your team uses in Mailshake, if you want each rep to land on their own filtered view ## Prompt I want an app my SDRs open every morning to work our Mailshake Lead Catcher queue, instead of clicking through Mailshake's own lead screen. This is a workbench for people, not an unattended automation. The rep decides everything, and the only thing that runs by itself is a background agent that researches and drafts when a rep explicitly asks for it. The main surface is a triage board of open leads grouped by campaign. Each row shows the prospect (name, email, and title or company where we have it), the campaign they came from, a snippet of their reply text, and the number of days since they replied, so nothing rots at the bottom of the queue. Sort within each campaign group by days since reply, oldest first, and visually flag anything past a staleness threshold that defaults to 3 days. Put a count of open leads in each campaign group header. Above the board, give me filters for lead status and for assignee. Mailshake's List Leads operation supports status and assignee filters natively, so pass those through to the API rather than pulling everything and filtering client side. Lead Catcher exposes Open, Won, Lost, Ignored, and Forwarded states, and the board defaults to Open. The assignee filter should default to the logged-in rep wherever we can match them to a Mailshake assignee, with an All reps option, so each rep sees just their own queue but can still look at the whole board when covering for someone. Handlers read from Mailshake. Use List Leads for the queue itself, List Campaigns to resolve campaign names for the grouping, List Replies Activity to pull the actual reply bodies and timestamps, and List Recipients for the prospect's full send and open history on that campaign. One important nuance: Mailshake's reply activity includes bounces and auto-replies, so filter those out before anything reaches the board. An out of office is not a lead worth a rep's morning. Clicking a row opens a detail pane with the full reply text rather than the snippet, the prospect's details, the campaign, and the send and open history from List Recipients, so the rep can see exactly what the prospect received and engaged with before they replied. The detail pane has a Draft a reply button that kicks off a background agent. The agent researches the prospect's company on the web, reads their reply text and the sequence they were sent, and writes a tailored response. The draft lands back in the app stored against that lead, so it appears in the detail pane when it finishes and the rep can copy and edit it. The agent must never send anything: no Mailshake send, no email, drafting only. Persist both the draft and the research brief the agent produced so they survive a reload and are still there tomorrow, and show a clear pending state on the row and in the pane while the agent is working. From the same pane, the rep dispositions the lead with Close Lead, Ignore Lead, or Reopen Lead. These write back to Mailshake, and the board should refresh that lead's state right after the call so the queue immediately reflects reality. Also in the detail pane, a Send to CRM button pushes the lead into HubSpot. Use Search Contacts to look for an existing contact by the prospect's email address, and if there is no match, use Create Contact with the details we have from Mailshake. Either way, then use Create Note associated with that contact, containing the prospect's reply text and the agent's research brief if one has been generated. Tell the rep which contact was matched or created, and mark the lead on the board as already pushed so nobody double files it. Persist per-lead app state: the generated draft, the research brief, whether it has been sent to CRM, and any note the rep types for themselves. Everything else is read live from Mailshake so the board never drifts from the real queue. ## How to customize - Change how the board groups leads: by campaign, by assignee, or purely by how long they have been waiting - Set the number of days after which a lead gets flagged as stale, and pick the filters each rep lands on by default - Tune the tone, length, and talking points the assistant uses when it drafts a reply ## FAQ ### Does this send emails to prospects for me? No. The assistant only writes a draft into the app for the rep to read, edit, and copy. Sending stays a human decision, made from wherever your team normally replies. ### Will this work with the free version of HubSpot? Yes. The Send to CRM button creates or matches a contact and attaches a note, and both are available on HubSpot's free CRM. ### Do bounces and out-of-office messages clutter up the queue? No. Mailshake's reply activity includes bounces and auto-replies, and the board filters them out so reps only see replies from real people. ### Can each rep see just their own leads? Yes. There is an assignee filter that defaults to the logged-in rep, plus an option to view every rep's leads when someone is covering for a teammate. ### If I close a lead here, does it update in Mailshake? Yes. Closing, ignoring, and reopening all write straight back to Lead Catcher, so your Mailshake account stays the source of truth. ### How is this different from letting an automation handle replies? This is a workbench your reps open and work in, not a background job. The rep decides every disposition and every reply. The assistant only researches and drafts when someone asks it to. Use this prompt in General Input: https://www.generalinput.com/prompts/work-the-mailshake-lead-catcher-queue-from-one-triage-board