Sort replies and draft the answers
Sorts outreach replies into seven categories, drafts each answer in your voice and proposes the CRM update. Unsubscribes stop at once.
reply-triage/SKILL.mdDownload- name
reply-triage- description
- Use this skill when replies to your outreach pile up. It sorts each one (interested, referral, not now with a date, objection, unsubscribe, out of office, wrong person), drafts the answer in your voice and proposes the CRM update. Unsubscribes are honored at once: no answer, cadence stopped, contact flagged.
- license
- CC-BY-4.0
Sort replies and draft the answers
This skill reads the replies to your outreach, puts each one in one of seven categories, drafts the answer and proposes the CRM change. You approve each line. The one exception to "nothing without approval" is an unsubscribe: the cadence stops at once, because stopping a message can never hurt.
Inputs
- The replies, each with the message it answers. With email access, read the replies since the last triage from the inbox or the sequencer's reply folder. Without it, ask the user to paste them, LinkedIn replies included.
- CRM access (read) to match each reply to its contact and deal. Without it, the output lists the changes for the user to make by hand.
- The sequencer, so cadences can be stopped. Without access, unsubscribes go to the top of the output marked "do now".
- Voice guide and a calendar link or two open slots for interested replies.
Steps
Collect and match. Pair each reply with its thread, contact and deal. Flag replies from someone who was not in the cadence (a colleague, an assistant).
Classify. Apply the rules in this order; the first match wins.
Order Category It looks like 1 Unsubscribe "remove me", "stop emailing", "unsubscribe", a firm "not interested" 2 Out of office An automatic reply, with or without a return date 3 Wrong person "not my area", "I left the company", "I don't handle this" 4 Referral "talk to [name]", a forward with a colleague added 5 Not now with a date "check back in March", "after our budget in Q2" 6 Interested A question about the offer, a time, "tell me more" 7 Objection Price, a current vendor, no priority, "send info" with no date If nothing fits, mark it "unclear" and ask the user.
Act on each category.
Unsubscribe: send nothing. Stop every cadence for this person now if the agent can; otherwise mark it "do now". Propose a do not contact flag in the CRM. If they ask that nobody at the company contacts them, propose suppressing the account.
Out of office: no answer. Stop the cadence, note the return date, and propose re-planning from the business day after it. A colleague named for urgent matters is not a new target.
Wrong person: stop the cadence. One line of thanks and one question: who owns this? If they left the company, propose marking the contact as gone.
Referral: thank them in one line. Stop the cadence, draft a first message to the new person that names who referred you, and propose adding them as the new thread owner.
Not now with a date: confirm the date and ask what changes by then. Propose a task one week before that date and stop the cadence. No date given: ask for one.
Interested: answer their question first, then offer two times or the calendar link. Propose the next step with a date and stop the cadence.
Objection: answer the specific concern in two or three sentences, with one proof point the user gave you and one question. No pressure, no discount the user did not approve. Stop the cadence and log the objection type.
Draft in the seller's voice. Under 80 words, one ask, no new claims.
Propose CRM changes as before and after lines for each reply.
Present the batch, unsubscribes first, then interested, then the rest. The user answers per line: send, edit or skip. Apply only what is approved.
Output
Replies triaged: 11 · 2026-11-17 to 2026-11-20
Unsubscribe 2 · Interested 2 · Referral 1 · Not now 3 · Objection 1 · Out of office 1 · Wrong person 1
DONE NOW
Cadence stopped: [Name], Harbor Line Logistics ("please remove me", 2026-11-19)
Cadence stopped: [Name], Redwater Labs ("not interested, don't email again")
1. INTERESTED · [Name], Pinecrest Engineering · "What would a pilot cost for 3 crews?"
Draft (54 words): [draft]
CRM: stage Contacted to Meeting requested · next step "Pilot call" 2026-11-24 ·
cadence: stop
2. NOT NOW · [Name], Summit Ag Supply · "Budget opens in March"
Draft (32 words): [draft]
CRM: task "Check back on budget" 2027-02-22 · cadence: stop
3. UNSUBSCRIBE (x2) · CRM: do not contact = yes · no reply sent
...
Reply with: "send 1, 2" · "edit 1: [change]" · "skip 4" · "apply CRM 1 to 6"Guardrails
- Reads: replies and their threads, the CRM records they match, the cadence status.
- Writes: cadence stops for unsubscribes, at once. Everything else (sent answers, CRM changes, new contacts, tasks) only after approval.
- Asks before: sending any answer, changing any field, adding a contact, re-planning a cadence.
- MUST honor every unsubscribe on the day it arrives. CAN-SPAM allows 10 business days; this skill does not wait.
- MUST check unsubscribes before anything else in the batch.
- MUST answer an interested reply's question before offering times.
- NEVER answer an unsubscribe with a pitch, a "sorry to see you go" offer or a survey.
- NEVER switch the cadence to a colleague named in an out-of-office.
- NEVER invent a date, a price or a proof point in a draft.
Sources
- CAN-SPAM Act: A Compliance Guide for Business, Federal Trade Commission: opt-outs honored within 10 business days, no B2B exception (read 2026-11-20).
- How can a founder sell without a sales team?, ALTARA Insights: log every reply, including the no's.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/toolkit
Use it with
-
Runs in ALTARAPlaybook Run the cadenceFounder-led outbound in 30 minutes a day, with ALTARAThirty minutes a day with ALTARA: a weekly list with dated reasons, contacts and sequences you approve, replies logged in the CRM. 30 minutes a dayRun it →
-
Runs in ALTARAPlaybook Find who to talk toTurn hiring signals into booked calls with ALTARAJob posts that reveal a plan, checked on the company's own site, then one decision-maker and an approved sequence per account. 30 minutes twice a weekRun it →
-
Connection Run the cadenceGmail, Google Calendar and DriveALTARA sends the sequences your team approved from a separate, warmed inbox. Your own AI reads your Gmail, Calendar and Drive to prepare the calls. Sending inbox for sequencesSee how →
-
Connection Run the cadenceOutlook, Teams and SharePointYour team texts ALTARA in Microsoft Teams, and it sends approved sequences from a warmed inbox. Your own AI reads your Outlook, Teams and files. Sending inbox for sequencesSee how →
-
Connection Keep the CRM currentHubSpotALTARA reads one HubSpot pipeline, read-only, and sends each change with a link to the deal. Your own AI reads the same records through HubSpot's MCP. Reads (rolling out)See how →
-
Connection Keep the CRM currentPipedriveALTARA keeps your Pipedrive pipeline current from the chat, after your yes. Your own AI reads the same deals through Pipedrive's MCP server. Reads and writesSee how →
-
Connection Keep the CRM currentSalesforceThe ALTARA team connects Salesforce on request, read access first. Your own AI reads the same records through Salesforce's hosted MCP servers. Connected on requestSee how →