サポートチームの生産性を決定的に左右するのは「人が判断しなくてもいいことを、正確に自動化できているか」だ。チケットのルーティング・SLA アラート・CSAT 送付・再オープン制御——これらを手動でやっている限り、チームの規模が増えるほど運用コストが線形に増え続ける。In this chapter, we will systematically explain the basic structure of Service Hub automation, 10 workflows that you should set up right now to prevent cancellations, manage quality, and improve customer experience, including the setup steps.。
All HubSpot workflows areTrigger → Filter → ActionIt consists of three elements: Once you understand this structure, you can design any complex automation by breaking it down into three questions: ``What is the starting point?'' ``Under what conditions?'' and ``What should we do?''
| Workflow type | origin object | Main uses | Analysis cadence and translation into improvement actions |
|---|---|---|---|
| Not everyone needs to see every KPI. Management doesn't need to check ticket numbers every day, and agents don't need to track NRR (net revenue retention rate). | Ticket | Automation starting from ticket creation, update, and stage change | Routing/SLA alert/CSAT sending/close notification/reopening control |
| contact base | Contact | Automation based on changes in customer properties and feedback scores | NPS Detractor Follow-up/Onboarding Sequence/Cancellation Risk Alert |
| company base | Company | Automation based on account health changes and update schedules | Health deterioration alert, update date reminder, automatic task creation in CSM |
Service Hub's automation is extremely powerful, but if you increase it unchecked, you'll end up in a situation where no one knows why this email arrived, or workflows collide and you get double notifications.Create a ledger (spreadsheet) that lists all workflows, and record the owner, purpose, and last confirmation date of each workflow.Establishing operational rules at the beginning improves long-term maintainability.
If you manually decide who should handle tickets when they arrive, your manager's first job in the morning will be to allocate tickets.Automatic routing is a system that automatically assigns tickets to the correct person/team based on their attributes.is. Properly designed routing can dramatically reduce FRT (first reply time).
| pattern | structure | optimal case | Points to note |
|---|---|---|---|
| round robin | Automatically assigned to the contact list in order. Distribute evenly as A→B→C→A→... | Generic support team with multiple agents with the same skills | An operational rule is required to remove agents who are on vacation or away from the list. |
| skill base | Assign by matching the ticket category, language used, product line with the skill tag of the person in charge. | A team divided into specialized areas such as technology, billing, and usage. | Regular review of skill tags. Always update when agent skills change |
| plan base | Branch teams and rep groups based on customer contract plans (Enterprise/Pro/Starter) | A system in which Enterprise customers are handled by a dedicated person, and Pro and below are handled by a common team. | Company property “Plan” must be kept up to date |
| Responsible CSM priority | Refer to the “Assigned CSM” property of a contact/company and route to the same CSM | High-touch CS model with a person-in-charge system. Enterprise compatible with a focus on continuing relationships with customers | Be sure to set up a fallback destination when your CSM is unavailable |
With the December 2025 update,When a customer replies to a closed ticket, you can control whether to reopen the ticket or create a new ticket using workflow.It became like that. Previously, the only behavior available was ``automatically reopen a closed ticket when a reply is received,'' which caused problems with resolved tickets being reopened by mistake, contaminating metrics.
If a ticket is reopened with a thank you email, the TTR (time to resolution) measurement goes haywire and the number of cases handled by agents increases.Properly setting reopening controls protects the accuracy of your team's metrics and prevents unreasonable workloads.It is directly connected to this. For portals that have applied updates from December 2025 onwards, we recommend changing the settings as soon as possible.
When we introduced Service Hub, we carefully selected the workflows that should be set up first. Categorized into three categories: cancellation prevention, quality control, and customer experience improvementThe 10 workflows were selected based on the balance between low setup time and large returns.That's what I did.
ワークフローは「設定したら終わり」ではない。ビジネスの変化・プロパティ名の変更・チーム構成の変更によって、かつて正しく動いていたワークフローが「誰にも知られず静かに間違った動作をしている」状態になる。定期的な棚卸しと品質確認を運用サイクルに組み込むことが、自動化の長期的な価値を保つ唯一の方法だ。
台帳に記録すべき項目は①ワークフロー名 ②目的（1文）③トリガー ④主な対象顧客セグメント ⑤アクションの概要 ⑥オーナー（氏名）⑦最終更新日 ⑧ステータス（有効/無効）——この8項目を Google スプレッドシートで管理するだけで、「このワークフローは何をしているのか」という問いに誰でも30秒で答えられる状態が維持できる。HubSpot の「ワークフロー名」欄にも「目的：〇〇（作成者：名前 / 更新日：YYYY-MM）」のように記入しておくと、台帳と HubSpot の両方から確認できて便利だ。
この3要素の構造を理解すれば、どんな複雑な要件も設計できる。新しいワークフローを作る前に「何をきっかけに・どの条件のとき・何をするか」の3問に答えるだけでよい。
チームの体制に合ったパターンを選ぶ。多くのチームはラウンドロビン＋プランベースの組み合わせから始めるのが実用的。休暇中の担当者を自動的に除外する仕組みをセットで設定する。
クローズから72時間以内→再オープン、72時間以降→新規チケット作成の設定を早急に行う。これによりメトリクスの精度が上がり、エージェントへの不当な負荷も解消される。
①自動ルーティング→②受付確認メール→③CSAT 送付→④CSAT 低スコア対応→⑤SLA アラートの順で設定する。最初の5本が完成した段階でチームのサポート品質が大幅に向上する。
全ワークフローの名前・目的・オーナー・更新日を台帳で管理する。四半期ごとに不要なワークフローを無効化し、チーム変更・プロパティ変更は発生時に即時反映することで「静かに誤動作するワークフロー」を防ぐ。
高スコアの顧客を放置すると「熱量が冷める」。推奨者への感謝メール→レビュー依頼→事例取材打診の3ステップを自動化することで、CSAT・NPS 取得コストに対するリターンが最大化される。