Help Scout alternative: when Chatwoot fits better than Help Scout
Choose Chatwoot over Help Scout when your support team needs more than email in one inbox and the conversations must stay in your own environment. Picture a team that adds a website live chat widget, Facebook, Instagram, WhatsApp or SMS next to its email queue and wants every thread, contact and report on servers it controls. Help Scout fits teams that want a managed shared inbox, Docs and Beacon with no servers to run. Chatwoot fits teams that need an omnichannel inbox, a Help Center portal and self-hosting, and that accept the operating work that comes with it. Its README lists the channels it supports in one inbox, including website live chat, email, Facebook, Instagram, WhatsApp, Telegram and SMS, so confirm each channel you need against the current release before you commit.
Start with the channel mix and the data residency rule, because these two usually settle the question. If your customers arrive mainly by email and you need no social or messaging channels, a self-hosted FreeScout install may cover the work with less to run. If you need the messaging channels and the conversation history must not leave your infrastructure, Chatwoot is the more direct fit. Next, check which paid self-hosted features you actually need. The Enterprise Edition is the tier that adds SSO with SAML, and the Premium Support tier adds Captain AI, voice calls and custom branding. Confirm current prices on the Chatwoot self-hosted plans page and ask whether any feature you need sits in the enterprise/ directory, which carries its own license.
Finally, test your appetite to operate the stack. Chatwoot runs on Ruby on Rails, PostgreSQL and Redis, requires Ruby 3.2 or later, and supports only PostgreSQL as its database. Sidekiq can use more than 1 GB of memory on a busy server, so size the host from the official requirements before you pick a plan. Your team needs people who can patch Rails, tune background jobs, back up PostgreSQL and monitor Redis, or a partner who will do it under a written scope. If that capacity is not available, Help Scout's managed model may cost less to run even when its per-user fees are higher.
Which platform fits which buyer situation
This table matches common buyer situations with the platform that fits better and the reason, based on the capabilities and self-hosting requirements documented for each product. Read each row against your own channels, data rules and identity setup, because a single gap such as SAML SSO can decide the choice. Chatwoot is the stronger fit where live chat and social channels matter, while email-only teams may find less to gain from switching.
| Buyer situation | Better fit | Reason |
|---|---|---|
| Email-only support on shared inboxes | Neither is automatically better; confirm with FreeScout | Chatwoot's advantages are its omnichannel inbox and widget, which email-only teams may not use. Compare shared inbox and Docs needs with the FreeScout page before deciding. |
| Live chat widget on your website | Chatwoot | Chatwoot's README lists a website live chat widget in the same inbox as email, so chat and email conversations sit together. |
| Facebook, Instagram, WhatsApp or other messaging channels | Chatwoot | Chatwoot's README lists Facebook, Instagram, Twitter, WhatsApp, Telegram, Line and SMS channels in one inbox. Confirm that each channel's connection setup meets your requirements. |
| Public help center or knowledge base portal | Chatwoot, if a portal is enough | Chatwoot includes a Help Center portal for articles, FAQs and guides. Confirm its layout and feature depth against your current Help Scout Docs usage. |
| Data must stay in your own environment | Either, self-hosted | Both run in your infrastructure. Chatwoot requires PostgreSQL and Redis 7.0 or higher, so plan for those data stores and their backups. |
| SAML SSO is a requirement | Chatwoot, on a paid plan | Chatwoot lists SSO with SAML on its Enterprise Edition plan, not on Community Edition. Check the current plan price on Chatwoot's pricing page before budgeting. |
| AI-assisted replies are wanted | Chatwoot, on a paid plan | Captain, Chatwoot's AI agent, is listed on the Premium Support plan. Confirm which AI providers and data flows apply in your environment. |
| Small team with limited Linux operations | Confirm with an implementation partner | Chatwoot officially supports only Ubuntu 20.04 and needs Ruby 3.2 or later, so operating-system and runtime work is a real cost to plan for. |
Chatwoot editions: what the free code covers and what SSO and AI cost
Chatwoot's core code is available under the MIT Expat license, which is a permissive license that lets you run, modify and redistribute the software in your own environment. The exception is the content in the enterprise/ directory, which is licensed under a separate license file in that directory. Treat that split as the starting point for any license review, because the boundary between free and paid code is set by the repository layout, not by the plan name on the pricing page. Third-party components that Chatwoot depends on keep their own licenses, so an audit of the full stack must include them.
- Core code: The MIT Expat license covers the main repository outside enterprise/.
- Enterprise directory: Code under enterprise/ follows its own license file, which you should read in full.
- Third-party components: Libraries and integrations keep their original licenses.
- Forks and modifications: Your right to change the code depends on which license applies to the files you change.
- Version pinning: Record the release tag you deploy so the license text you reviewed matches the code in production.
Ask your legal or compliance team to confirm how the enterprise/ license applies to the features you plan to use, and to review the license of every third-party component in your deployment.
The Community Edition is listed at $0 and free forever on Chatwoot's self-hosted plans page. It gives you the omnichannel inbox, the Help Center portal, automation, teams, canned responses, private notes and reporting described in the project README. Your cost on this tier is infrastructure, email configuration and the staff time to operate it, not a license fee. Teams that only need shared conversations across channels can often start here and decide later whether paid features are worth the cost.
- Omnichannel inbox: Website live chat, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line and SMS are listed in one inbox.
- Help Center portal: Articles, FAQs and guides are included in the free tier according to the README.
- Workflow tools: Auto-assignment, business hours, automation, teams, labels and canned responses are listed.
- Reporting: Conversation, agent, inbox, team and CSAT reports are part of the README feature list.
- Costs you still carry: Servers, PostgreSQL, Redis, backups, upgrades and monitoring are your responsibility.
Confirm on the pricing page which features are included at the Community tier, because the README and the plan comparison can differ as the product changes.
The Premium Support plan is listed at $19 per agent per month. According to the pricing page, it adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions, and priority support. The cost scales with the number of agents, so a team that grows its roster pays more each month, while one-time setup and hosting costs stay in place regardless of tier. Captain is an AI agent that automates responses to common queries, so the AI features carry their own data handling questions that you should review before turning them on.
- Per-agent pricing: The $19 figure applies per agent per month, so multiply it by your agent count to estimate the recurring license line.
- Captain AI: Automated answers to common queries are included at this tier according to the plans page.
- Roles and permissions: Role-based access is part of this tier, which matters if you separate duties between agents and administrators.
- Branding and voice: Custom branding and voice calls are listed at this level.
- Data flow for AI: Confirm where prompts and conversation content go when Captain runs, and whether a self-hosted deployment keeps that data in your environment.
Ask the vendor to confirm in writing which Captain features, roles and support terms come with this plan, and whether they change with the agent count you expect.
The Enterprise Edition is listed at $99 per agent per month and adds SSO with SAML and SLA policies on the self-hosted plans page. For a team with an existing identity provider, SAML single sign-on is often the deciding feature because it lets you enforce your own login policy and remove local accounts. SLA policies describe the support commitments the vendor makes, so compare them against your internal severity targets. At this price point, the per-agent cost is the largest recurring line, so model it against the number of people who actually need an agent seat.
- SAML SSO: Single sign-on with SAML is included at this tier according to the plans page.
- SLA policies: Support commitments are listed, so read the terms for response scope and exclusions.
- Identity integration: Confirm which identity providers you need and whether the SAML setup matches them.
- Seat planning: Count agents who need full access versus occasional users, since each paid seat is billed monthly.
- Exit terms: Check the notice period and how seat changes are billed before you commit.
Before buying, request the current plan matrix and the signed terms, and confirm whether SSO, SLA and AI features are billed per agent, per instance or both.
The plan names, prices and feature lists on Chatwoot's self-hosted plans page are the reference for buying decisions, and they can change between releases. The code license and the plan entitlements are separate questions, so one does not answer the other. Before purchase, write down the features your team must have on day one, then match each one to a tier and a line in the vendor's current terms. Ask for the answers in writing, because a verbal confirmation will not help you in an audit or a renewal.
- Current plan matrix: Compare the Community, Premium Support and Enterprise feature lists on the live pricing page on the day you buy.
- Release version: Note the Chatwoot release you plan to run, since features are tied to versions.
- Third-party integrations: Confirm the licenses and terms of Slack, Dialogflow, Shopify, Google Translate and Linear connectors you intend to use.
- Billing basis: Confirm how agents are counted, including part-time or shared accounts.
- Support boundaries: Ask what the support plan covers for your self-hosted environment, and what remains your responsibility.
A written quote that lists each feature against its plan, with the license file cited, gives your compliance and procurement teams something concrete to review.
Where conversations live and who controls them
Help Scout runs as a vendor-hosted cloud service, so your conversations sit in its environment under its operating model. Chatwoot moves that control to your own virtual machine, container platform or chosen cloud, which also moves the security, patching and evidence work onto your team or your implementation partner.
Vendor cloud versus your own hosting
Help Scout stores conversations, Docs and customer records in its hosted service, so data location and access controls are set by the vendor and its contract. Chatwoot can be installed on a Linux VM with the installation script, on Docker, or on Kubernetes with a Helm chart, and Chatwoot documents guides for AWS, Azure, DigitalOcean, Google Cloud and Heroku. Confirm which region and provider will hold the database, uploaded attachments and backups before you choose a target.
Database and cache placement
Chatwoot supports only PostgreSQL as its database and recommends Redis 7.0 or higher, so both stores hold every conversation and contact record you move onto it. Decide whether they run as managed services in your cloud account or on the same host as the application, and who holds the keys and snapshots. Ask your team which tier owns restore testing.
Single sign-on through SAML
Help Scout's identity options depend on its plan, so confirm current SSO terms with the vendor before relying on them for agent access. In Chatwoot, SSO with SAML is part of the Enterprise Edition, listed at $99 per agent per month on Chatwoot's self-hosted plans page, while Premium Support does not include it. Check that your identity provider can issue the attributes Chatwoot needs for agent roles and team membership.
Licensing of the code you run
Chatwoot's code is MIT Expat licensed except the enterprise/ directory, which falls under its own license, and third-party components keep their licenses. Paid Enterprise features therefore need a separate license review before you modify or redistribute the build. Ask counsel to confirm which directories your deployment includes and whether any bundled components add obligations.
Compliance evidence and auditor roles
Hosting conversations yourself means your organization, not the vendor, must produce the access logs, change records, backup evidence and vendor assessments that an auditor will sample. DeployOpen can plan and document these controls and prepare the evidence, but it does not issue audit reports, attestations or certifications, and independent auditors make that determination. Agree in writing which controls the implementation scope covers and which remain with your team.
Upgrade and patch responsibility
On Help Scout, the vendor applies platform updates to its service. On self-hosted Chatwoot, your team or implementation partner must track the releases on Chatwoot's GitHub releases page, test them against your Ruby, Node.js and PostgreSQL versions, and schedule the downtime. Set an owner and a review cadence for upgrades before go-live, because a missed patch becomes your exposure.
What running Chatwoot requires from your infrastructure
Running Chatwoot yourself means choosing an installation path and then owning the full stack beneath it. Chatwoot documents a Linux VM installation script, Docker, and Kubernetes with a Helm chart for larger high-availability deployments, plus guides for AWS, Azure, DigitalOcean, Google Cloud and Heroku. For a single team, a VM or Docker host is the simplest starting point, while the Helm path suits platform teams that already operate Kubernetes and need redundancy. Decide early which path your operations team will support, because the upgrade and backup routines differ between them.
The stack is strict and should be checked before anyone provisions servers. Chatwoot requires Ruby 3.2 or later, recommends Node.js 20.x, supports only PostgreSQL as its database, and recommends Redis 7.0 or higher. Ubuntu 20.04 is the only officially supported Linux distribution, so an organization standardized on another distribution should confirm with Chatwoot how its environment will be supported before committing. Sizing is set out in the deployment requirements: at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000, plus at least 1 GB of swap.
Plan memory above the minimum for a busy server. The requirements page notes that Sidekiq, the background job processor, can use more than 1 GB of memory on a very active server, so a host sized only to the table can swap under peak load. Ask your platform team to load-test with realistic email and chat volume before go-live, and confirm the sizing against your own peak rather than average conversation counts. Budget for the operating staff who will patch Ruby, Node, PostgreSQL and Redis on a recurring schedule, since that maintenance is the largest ongoing cost of self-hosting.
Cost components: Help Scout subscriptions versus running Chatwoot
Help Scout bills a recurring subscription for the software and hosting. Running Chatwoot moves most of that spend to infrastructure, database operations, email setup and staff time, plus any paid Chatwoot edition you choose. Request the current Help Scout quote and confirm plan terms before you compare totals.
Help Scout per-user subscription
Help Scout charges recurring fees by user and plan tier, and some features such as HIPAA compliance sit on higher tiers or add-ons. Ask for a written quote covering every seat you need, every add-on and the contract term. Confirm whether price changes apply at renewal and whether data export is included.
Chatwoot Community Edition license
The Community Edition carries no license fee. Its code is MIT licensed, apart from the enterprise/ directory and third-party components. The license cost is zero, so your spend shifts to hosting, operations and staff time. Confirm that the features you need sit in the Community Edition before you assume zero software cost.
Paid Chatwoot editions per agent
If you need Captain AI, SSO with SAML, SLA policies or priority support, Chatwoot's self-hosted plans are priced per agent per month. Those fees recur for every agent on the plan. Check the current plans page for each tier, and limit paid seats to the agents who need the features.
Servers, swap and sizing
Chatwoot's requirements scale with conversation volume, and the vendor recommends at least 1 GB of swap. Hardware or cloud instances recur monthly, and an active Sidekiq process can use more than 1 GB of memory. Size for your peak daily conversation count and ask your cloud or data center team to price the instance.
PostgreSQL, Redis and their operation
Chatwoot needs PostgreSQL as its only supported database and Redis 7.0 or higher. Managed services carry recurring fees, while self-run instances add patching, monitoring and backup time. Decide early whether your team will run these components or buy them as a managed service, because that choice drives most of the operations cost.
Email deliverability and backups
Email is the core channel for support, so sending and receiving domains, SPF, DKIM and DMARC records, and a mail provider are recurring costs and setup work that Help Scout largely handles for you. Backups of the database and attachments also recur. Budget for monitoring, restore testing and retention storage.
Upgrades and staff time
Each Chatwoot release needs a test, a staging update and a rollout window, and the Community Edition gives you no vendor-managed upgrade. Staff time for upgrades, on-call support and user administration is usually the largest recurring cost. Estimate hours per month from your own team, not from a generic figure.
DeployOpen implementation fees
If you scope implementation, hardening, backups, upgrades or support with DeployOpen, those fees follow the written scope and are one-time for setup and recurring for retainers. DeployOpen does not publish prices, so request a quote that lists each deliverable, the environment and the timeline.
How a move from Help Scout to Chatwoot is structured
The sequence moves channels, past conversations and team routing in stages so that each part is proven in a pilot before the old inbox stops receiving mail. Each stage ends with a check that tells you whether to continue.
Confirm channel and inbox scope
Before any installation, list every Help Scout mailbox, the Docs site, the Beacon widget and any connected channels, and mark which ones Chatwoot will carry: email, website live chat, Facebook, Instagram, WhatsApp or others. Owners of each mailbox should sign off on the list, and anything you will not move, such as Docs content or Beacon forms, should be recorded with its replacement. The check is a signed scope sheet that names every inbox and its target in Chatwoot.
Stand up the Chatwoot environment
Your platform or infrastructure team installs Chatwoot in your own cloud account or data center, using the Linux VM script, Docker, or Kubernetes with the Helm chart if you need high availability. Confirm the stack against the deployment requirements: Ruby 3.2 or later, Node.js 20.x, PostgreSQL as the only supported database, Redis 7.0 or higher, and the officially supported Ubuntu release. Size the servers to your expected conversation volume using the published CPU and memory guidance. The check is a working login, a tested backup and a documented restore.
Connect email and channels
Create each inbox in Chatwoot and connect it to its channel. Email requires DNS and forwarding changes that your mail administrator must make and test, and each social or messaging channel needs its own authorization with the provider. Treat channel reconnection as a separate task for each channel, because each provider has its own approval, permissions and verification steps. The check is a test message received and replied to through each inbox from outside the company.
Export past conversations and customers
Pull conversations, threads, attachments and customer records out of Help Scout. Confirm the export method, the scopes your OAuth application needs and the rate limits for your plan in the Help Scout API documentation before writing any script, since limits determine how long a large export takes. Store the exported data in your own environment, then load it into Chatwoot or a staging copy. The check is a row count and a sample of threads and attachments compared against Help Scout.
Rebuild teams, routing and canned responses
Recreate agents, teams, labels, business hours, auto-assignment rules, automations, canned responses and private note conventions in Chatwoot. Agent roles and permissions should follow your access policy, and some advanced controls sit in paid tiers, so check which ones you need against the self-hosted plans page. Compare each rule with its Help Scout original and mark any that do not carry over. The check is a signed list of rebuilt rules with the gaps you accepted.
Pilot with one inbox
Run one low-risk inbox in Chatwoot while the rest stay on Help Scout. Agents handle live traffic, the team reviews response times, assignment behavior, notifications and the help center or CSAT reports, and customers confirm that replies arrive with the correct sender and threading. Record every defect and fix it before expanding. The check is a pilot review that signs off the routing and notification behavior for the next inboxes.
Cut over and retire forwarding
Move the remaining inboxes in batches, switch DNS and forwarding records for each, and keep Help Scout read-only for reference while you confirm that no new mail arrives there. Update the website widget, links from Docs and any saved customer-facing references to the new help center. Retire Help Scout only after your records retention obligations are met and the data copy is verified. The check is a forwarding audit showing that no channel still delivers to Help Scout.
Questions buyers ask before switching from Help Scout to Chatwoot
What does a switch from Help Scout to self-hosted Chatwoot cost?
The software license is free under the Community Edition, so the cost is made up of infrastructure, your team's time, a support decision and migration work. Hosting is a recurring cost that depends on your conversation volume: Chatwoot's requirements page recommends at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000, plus at least 1 GB of swap. Paid Chatwoot plans are billed per agent per month, so the agent count drives that line. Ask any implementation partner for a fixed-scope quote that separates one-time work (installation, mailbox setup, migration, hardening) from recurring work (hosting, backups, upgrades, support).
How long does a Chatwoot migration take?
Duration depends on your environment, not on a fixed figure. The main variables are how many shared inboxes, channels and agents you run, whether you connect live chat, social channels or only email, how much history you move, and whether your email routing and deliverability can be changed without disruption. Your infrastructure choices matter too, including whether you deploy on a Linux VM, with Docker, or on Kubernetes with the Helm chart for high availability. Ask for a written timeline tied to a defined scope, and confirm how your current Help Scout export will be handled before work begins.
Can our team self-host Chatwoot without an outside partner?
A technically capable team can install Chatwoot, but the requirements are specific. Chatwoot requires Ruby 3.2 or later, recommends Node.js 20.x, supports only PostgreSQL as its database, recommends Redis 7.0 or higher, and lists Ubuntu 20.04 as the only officially supported Linux distribution. Your team also needs to own email routing, TLS, backups, upgrades, monitoring and sizing, and Sidekiq can use more than 1 GB of memory on a very active server. Decide early which of these you will run internally and which you want covered under a fixed-scope engagement or a support retainer.
Do SSO and AI features require a paid Chatwoot plan?
Yes, both are paid features in the self-hosted plans. The Community Edition is listed at $0 and free forever. Premium Support is listed at $19 per agent per month and adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions and priority support. Enterprise Edition is listed at $99 per agent per month and adds SSO with SAML and SLA policies. Confirm current prices and included features on Chatwoot's self-hosted plans page before budgeting, because plan contents can change. Also confirm whether your identity provider needs SAML specifically.
What happens to Help Scout Docs when we move to Chatwoot?
Chatwoot includes a Help Center portal for articles, FAQs and guides, so it can replace Help Scout Docs for many teams. Moving content is a separate task from moving conversations: you need to export articles and collections, re-create categories and structure, and update links that your support widget or website uses. Check whether your public Docs URLs will still resolve after cutover, and plan redirects where needed. Ask your provider to list every place Docs links appear, since a broken article link is often the first visible problem after a switch.
Will we keep our past conversation history after moving to Chatwoot?
Past history can be moved, but it needs a deliberate plan. Export conversations, threads, attachments and customers from Help Scout through its Inbox API within your plan's rate limits, then decide what to import into Chatwoot and what to archive separately. The CSV or Excel reporting export is not a full record of threads and attachments, so do not rely on it as your only copy. Confirm with your provider how attachments, contact identities and timestamps will map, and whether you need a read-only archive of older conversations for legal or audit reasons.
What should we check for email and data protection before cutover?
Email routing and deliverability decide whether customers actually reach the new inbox. Confirm how your domain's mail records, forwarding rules and sending addresses change, and test replies in both directions before you retire the old setup. On the security side, self-hosting moves responsibility for access control, encryption, backups and logging into your environment. If you handle regulated data, map those controls to your own obligations. DeployOpen prepares systems, controls and evidence for compliance assessments, but independent auditors and certification bodies issue any audit report or certification.
What changes for your support team after the move
Agents will work in one Chatwoot inbox that gathers the website live chat widget, email and any social or messaging channels you connect, so the first daily change is that conversations arrive from more places than they did in Help Scout. Before cutover, decide how each channel routes: which inbox or team owns it, whether auto-assignment by agent availability applies, and when auto-responders and business hours fire. Test these settings with a few agents on a staging instance, because a misrouted channel is easier to fix before the team depends on it. Confirm which channels your organization actually needs, since each one you enable adds setup and monitoring work.
Help Center content does not move into the same place as the shared inbox. Chatwoot's Help Center portal publishes articles, FAQs and guides, but the articles, collections and redirects from your Help Scout Docs site need to be rebuilt or imported and then checked, including links already embedded in the support widget or emails. Reporting also changes. Chatwoot's conversation, agent, inbox, team and CSAT reports will replace the figures your managers read today, so agree on which metrics matter and compare a few weeks of Chatwoot numbers against Help Scout reports before retiring the old dashboards. Admins will also own patching, upgrades, backups and monitoring of the Ruby, PostgreSQL and Redis services, which Help Scout handles for you today. Ask whether your team has a named person and a runbook for those tasks.
Help Scout's managed model remains the better fit when a small team has no operations capacity to run a Rails application, a PostgreSQL database and a Redis service, or when no one will own on-call response for a support outage. Self-hosting also brings email deliverability work that the vendor currently absorbs. If those conditions describe your team, keep Help Scout or compare hosted options before committing, and treat the move as a staffing decision as much as a software one. Teams that do proceed should write down an owner for each component and rehearse a restore before go-live.
How DeployOpen evaluates, implements and migrates Chatwoot
DeployOpen is a Chainscore Labs company that plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside the client's own infrastructure. For a Help Scout to Chatwoot move, we start by confirming which channels, mailboxes and Help Center content the team actually needs, then plan the deployment in your cloud account, data center or air-gapped network.
How we scope
- Inventory which Help Scout mailboxes, live chat widgets and Docs collections must move, and which channels Chatwoot must add
- Confirm whether SSO with SAML is needed, since it sits in the Enterprise Edition rather than Community Edition
- Record PostgreSQL, Redis, Ruby and Node.js versions against Chatwoot's published requirements before any build work
- Document the scope in writing, with deliverables and timelines agreed before work starts, as engagements are fixed-scope
How we build
- Size the host against Chatwoot's published guidance for your expected daily conversation volume, including swap and Sidekiq memory
- Deploy with the installation method your team can operate, such as a Linux VM, Docker or Kubernetes with the Helm chart
- Configure email inbound and outbound routing, SPF, DKIM and DMARC records, and each channel integration in scope
- Test conversation routing, auto-assignment, business hours, CSAT and Help Center publishing against your real workflows
How we hand over
- Deliver architecture notes, configuration records, runbooks and backup and restore procedures in documents your team keeps
- Walk administrators through agent roles, inboxes, teams, canned responses and automations in a live session
- Provide a migration plan for past conversations and attachments, stating what is exported from Help Scout and what is rebuilt
- Provide control and evidence material for your compliance team, noting that auditors and certification bodies issue any assessment
How we support
- Upgrades, patching and backups can run under a retainer agreed in writing after handover
- Security testing of the deployed Chatwoot instance and its integrations is available as a separate scoped engagement
- Ask any provider to confirm which Chatwoot release line and license edition the quote assumes before signing
- Ask for the support scope, response expectations and change process in writing so ownership is clear after go-live
