Automating Help Scout Workflows: From New Conversation to Resolution

A practical field guide from Automation Ace.

Short answer: in Help Scout, use automatic workflows to tag, assign, and prioritize new conversations the moment they arrive; saved replies and AI drafts for fast first responses; manual workflows to handle common cases in one click; time-based workflows to follow up on waiting conversations; satisfaction ratings to close the loop; and integrations or webhooks to push escalations, bugs, and customer data to the rest of your tools.

Help Scout is built to keep email support simple. That simplicity is a strength, as long as the repetitive work around each conversation is automated. This guide follows a conversation from the moment it arrives to the moment it is resolved and shows what to automate at each stage.

Short answer

1. Deflect common questions with Docs and Beacon.
2. Triage new conversations with automatic workflows: tags, assignment, priority.
3. Reply faster with saved replies and AI drafts; watch response targets.
4. Package common multi-step actions as manual workflows.
5. Follow up on pending conversations automatically.
6. Close with outcome tags, act on satisfaction ratings, and review trends weekly.

What Help Scout offers

Help Scout is a help desk for small and growing teams, centered on a shared inbox. Based on its documentation at the time of writing, it includes:

• Inboxes and conversations with assignment, statuses (active, pending, closed), tags, notes, and mentions.
• Saved replies for consistent answers to common questions.
• Workflows, automatic and manual, built from conditions and actions.
• Docs for a knowledge base and Beacon, a website widget for help articles, contact forms, and chat.
• AI features such as AI drafts and summaries, and AI Answers as a paid add-on.
• Satisfaction ratings and reports.
• Integrations, plus an API and webhooks, and a Zapier app.

Workflow limits, advanced conditions, SLA policies, and AI features vary by plan, so confirm what your plan includes.

The conversation lifecycle

How Help Scout workflows work

• Automatic workflows run in the background and act on conversations that match their conditions, including existing conversations when you create them.
• Manual workflows run when a teammate applies them, performing all their actions at once.
• Conditions can be combined with AND or OR logic, using things like subject and body text, customer details, mailbox, status, tags, and attachments.
• Actions include adding or removing tags, assigning, changing status, sending a saved reply, adding a note, and moving conversations.
• Each workflow runs once per conversation, which prevents loops but means a workflow will not re-fire on the same conversation later. Design with that in mind.

Here is how a few common workflows look in plain language:

AUTOMATIC WORKFLOW: Billing triage
When:  ALL of
       - Status is Active
       - Subject or body contains: invoice, refund, charge, receipt, billing
Then:  - Add tag: billing
       - Assign to: Billing team member (or move to Billing folder/mailbox)

AUTOMATIC WORKFLOW: VIP routing
When:  ANY of
       - Customer email domain is: bigclient.com
       - Customer has tag/property: vip
Then:  - Add tag: vip
       - Assign to: Account owner
       - (Optional) Send a note to the team

MANUAL WORKFLOW: Refund approved
Then:  - Send saved reply: "Refund processed"
       - Add tag: refund-approved
       - Remove tag: billing
       - Change status: Closed

Stage 0: Answer questions before they become conversations

The cheapest conversation is the one that never needs a reply. Publish clear Docs articles for your top questions, and use Beacon on your site and in your app so customers see suggested articles before they write in. If you use AI Answers, it draws on the same Docs content, so better Docs means better answers. Review the questions AI could not answer and turn them into new articles.

Stage 1: Triage new conversations automatically

• Tag by topic: keywords in the subject or body (billing, bug, cancel, shipping) add a tag.
• Assign by topic or customer: billing to the billing owner, VIP domains to their account manager.
• Separate by source: conversations from Beacon, a contact form, or a specific address can get their own tags and routing.
• Flag urgency: words like down, outage, urgent, or cancel add an urgent tag and notify a lead.
• Filter noise: auto-tag and close known notification senders or spam patterns.

Keyword rules cover most cases. For messages that need understanding rather than matching, add AI classification through an integration; see AI email triage automation and support ticket triage.

Stage 2: Faster, consistent first responses

• Auto-reply to acknowledge receipt and set expectations, especially outside business hours.
• Saved replies for your top 20 questions, written in your voice and reviewed quarterly.
• AI drafts to give agents a starting point, edited before sending.
• Response targets: use SLA policies where your plan includes them, or a scheduled check that alerts a lead when urgent conversations wait too long.

Stage 3: Collaborate and handle common cases in one click

• Notes and mentions keep internal discussion on the conversation instead of in Slack.
• Summaries help when a conversation changes hands.
• Manual workflows package multi-step handling: “Refund approved,” “Escalate to engineering,” “Send to sales.” Each one sends the right saved reply, adjusts tags, reassigns, and sets status in one click, so every agent handles the case the same way.

Stage 4: Follow up on waiting conversations

Pending conversations are easy to forget. Time-based conditions in automatic workflows can send a check-in and later close quiet conversations:

AUTOMATIC WORKFLOW: Pending follow-up
When:  ALL of
       - Status is Pending
       - Last customer reply was more than 3 days ago   (time-based condition)
       - Tag is not: no-follow-up
Then:  - Send saved reply: "Just checking in"
       - Add tag: followed-up

AUTOMATIC WORKFLOW: Close after follow-up
When:  ALL of
       - Status is Pending
       - Tag is: followed-up
       - Last customer reply was more than 7 days ago
Then:  - Change status: Closed

Because each workflow runs once per conversation, use tags (like followed-up) to chain stages, and give agents a no-follow-up tag for conversations that should never be nudged. Check which time-based conditions your plan supports.

Stage 5: Resolve and learn from ratings

• Outcome tags (answered, bug-reported, refund, feature-request) make reports meaningful.
• Satisfaction ratings after replies show how customers felt.
• Act on low ratings: alert the team lead, reopen or follow up, and review the conversation in your weekly meeting.
• Feed retention: repeated issues or cancellation language on a key account should reach the account manager; see customer renewal and retention automation.

Stage 6: Turn conversations into improvements

Once a week, pull tag counts and a sample of conversations, and have AI summarize the top themes, new issues, and questions your Docs do not answer. A person reviews it and turns it into actions: new Docs articles, saved reply updates, product feedback, and workflow tweaks. Send it as a single digest rather than many alerts; see sending a digest instead of many notifications.

Connect Help Scout to the rest of your stack

Help Scout offers native integrations, an API, and webhooks for events such as new or updated conversations, plus a Zapier app; check the current list of events, triggers, and actions when you build. Receive webhooks with Webhooks by Zapier or your own endpoint, search before creating records elsewhere, and protect against loops; see why Zapier creates duplicate records and Slack notification best practices.

Where AI fits

• Good uses: answering from Docs for simple questions, drafting replies for agents to edit, summarizing long threads, classifying messages that keyword rules miss, and summarizing weekly themes.
• Keep human: refunds and billing exceptions, complaints, legal or security issues, and any reply where being wrong is costly.

Set limits and review steps for AI that talks to customers; see AI guardrails and Human in the Loop. For AI that handles a whole support role, see building an AI support teammate.

Guardrails

• Avoid overlapping workflows that tag or assign the same conversation differently; document what each one does.
• Remember workflows run once per conversation; use tags to chain steps.
• Never auto-close active customers: follow-up workflows should only act on pending conversations without new replies.
• Keep tags tidy: a short, agreed list beats hundreds of one-offs.
• Protect data: do not send full conversations to tools that do not need them, and ask customers not to email sensitive data.
• Review automation quarterly as products, policies, and teams change; see automation documentation and handoff.

Metrics to track

• First response time and resolution time, overall and by tag.
• Replies per conversation, a proxy for clarity.
• Share answered from Docs or AI without an agent.
• Satisfaction ratings by tag and agent.
• Untagged or unassigned conversations, a sign triage rules need work.
• Top tags over time, to spot product issues early.

Record a baseline first; see defining success metrics before you automate.

A practical rollout order

1. Week 1: agree on tags, write saved replies for your top questions, and set up auto-replies.
2. Week 2: add automatic triage workflows for topics, VIPs, and urgency.
3. Week 3: add manual workflows for common cases and pending follow-ups.
4. Week 4: connect Slack escalations, bug tracking, and CRM context.
5. Then: Docs and Beacon improvements, AI drafts and answers, rating follow-ups, and weekly theme summaries.

Using another support channel too? See routing texts with Textline and DM support with Manychat. New to the tool? Explore Help Scout and start with tags and saved replies. Automation Ace can help design and build Help Scout workflows and integrations.

Frequently asked questions

How do I automate workflows in Help Scout?

Use automatic workflows to tag, assign, and prioritize conversations based on conditions such as subject or body text, customer details, mailbox, status, and tags; manual workflows to run common multi-step actions in one click; saved replies and AI drafts for responses; and integrations, the API, webhooks, or Zapier to connect other tools.

What is the difference between automatic and manual workflows in Help Scout?

Automatic workflows run in the background on conversations that match their conditions. Manual workflows run only when a teammate applies them, performing all of their actions at once. Both are built from actions such as tagging, assigning, changing status, and sending saved replies.

Why did my Help Scout workflow not run again on the same conversation?

Help Scout runs a workflow only once per conversation to prevent loops. To build multi-stage automation, use tags to mark that a stage happened and create a separate workflow for the next stage.

How do I follow up automatically on pending conversations in Help Scout?

Create an automatic workflow for pending conversations with no customer reply for a set number of days that sends a check-in saved reply and adds a followed-up tag, then a second workflow that closes followed-up conversations after more time passes, where your plan supports time-based conditions.

Does Help Scout integrate with Zapier?

Yes. Help Scout has a Zapier app as well as native integrations, an API, and webhooks. Check Zapier and Help Scout for the current triggers, actions, and webhook events.

Can Help Scout use AI to answer customers?

Help Scout offers AI features such as AI drafts and summaries, and AI Answers as a paid add-on that answers from your Docs content. Keep Docs current, review unanswered questions, and keep sensitive cases with people.

How should I route VIP customers in Help Scout?

Create an automatic workflow that matches VIP email domains or a customer property, adds a vip tag, and assigns the conversation to the account owner, with an optional note or Slack alert through an integration.