# Is Intercom HIPAA Compliant? Expert Plans, BAAs, and Fin > Understand Intercom’s Expert-plan BAA, covered AI products including Fin, published pricing, and healthcare configuration questions. Canonical: https://gosummer.ai/blog/is-intercom-hipaa-compliant Published: 2026-10-25 | Updated: 2026-10-25 | Sources reviewed: 2026-10-21 Author and publisher: Summer AI ![Cobalt glass door and copper key protect a tied case folder, illustrating Intercom HIPAA access and BAA terms.](https://gosummer.ai/blog-art/is-intercom-hipaa-compliant-gemini-editorial-2026-10-21.jpg) ## The quick answer Intercom offers a BAA on Expert and lists Fin among covered AI products. Review your agreement and exact deployment. Intercom offers HIPAA support and a business associate agreement on its Expert plan. Its current help documentation says that sending electronic protected health information through Intercom requires a signed BAA. If you are evaluating “HIPAA Intercom” for a healthcare business, start with that plan and agreement. That answers the first buying question. The next question is whether the covered setup fits the way your support team works, including Fin, account access, outside integrations, and any voice service you enable. This guide is published by Summer AI, a telehealth support provider. Vendor terms were reviewed on October 21, 2026. The linked Intercom documents are the sources for its product claims. ## Where to find Intercom's BAA terms [Intercom's Contacts FAQs](https://www.intercom.com/help/en/articles/8827723-contacts-faqs) describe Expert eligibility and how to request the agreement. Ask Intercom to confirm the covered workspace and services in your proposed order. A procurement review should retain the signed agreement with the subscription details. Include the person responsible for the workspace so that security requirements carry through to installation. If a new team later enables an integration, they should know which review applies. Avoid using an older comparison article as the basis for approval. Plan names, prices, and AI coverage can change. Obtain the current terms directly and keep their effective date beside your decision. ## Does the BAA cover Fin AI? The same Intercom FAQ lists Fin AI Agent, Copilot, AI in the Inbox, and Phone AI including transcripts and Fin Voice among covered AI products. Confirm the exact products you intend to use against your agreement. It would be inaccurate to reject Intercom on a blanket claim that its BAA excludes Fin. A useful evaluation instead checks the deployment: which data Fin receives, what it retrieves, and what it may send to connected services. Ask your reviewer to walk through a representative support question with the proposed settings. Include a handoff to a human and an outside system lookup. That shows the scope of the service your team will operate. ## How much does the eligible plan cost? [Intercom's pricing page](https://www.intercom.com/pricing) currently lists Expert at $132 per seat per month under annual billing. Fin service pricing starts at $0.99 per outcome. Channels and add-ons can add charges. As an illustrative calculation, four Expert seats at the published annual-billing rate produce a $528 monthly equivalent for seats. This is arithmetic for the listed rate; your full commitment and invoice depend on the contract, usage, and selected services. Use the eligible plan when comparing healthcare costs. Comparing an entry-level plan with another vendor's healthcare configuration will give your finance team an incomplete budget. Our [Intercom cost comparison](https://gosummer.ai/blog/cheaper-intercom-alternative) includes a worksheet for that decision. ## Review the integrations that receive patient data A support workspace can send information to a CRM, an analytics destination, a workflow tool, or a vendor portal. An agreement with the inbox vendor does not establish what each outside service may do with that information. Map those connections before rollout. For each destination, name the business purpose, the data sent, and the person who maintains access. Ask the responsible reviewer to confirm the contractual arrangement for that destination. [HHS's business associate contract guidance](https://www.hhs.gov/hipaa/for-professionals/covered-entities/sample-business-associate-agreement-provisions/index.html) is a useful reference for the responsibilities involved. Apply it to your actual relationships rather than assuming that every app in a marketplace has the same coverage. A connection that only needs order status should not receive a full clinical conversation by default. Work with your technical team to send the information needed for the support task. ## Check the patient experience on a shared device Test the Messenger as a visitor, as a signed-in patient, and after logout. Ask what evidence establishes the account owner. A visitor entering another person's email address should not receive that person's order or conversation history. Use synthetic accounts with deliberately similar names. Include a patient with multiple purchases so you can see whether the answer refers to the correct order. Check previews and attachments as well as the main message body. The application should preserve a returning patient's conversation without exposing it to the next person using the browser. Your support team needs a clear sign-in recovery path for people who cannot access their account. ## Separate inbox capability from telehealth workflow fit Intercom provides a broad customer-service platform. Fin's [integration documentation](https://fin.ai/integrations) describes API and MCP connection options, so evaluate the connections you could configure for your own stack. For a telehealth business, the case may also involve a care provider, pharmacy, payment record, and a customer waiting on several answers. Ask the implementation team to show how staff can inspect the relevant source and follow unfinished work. Consider a fictional delayed order. The patient also asks whether a second charge is a duplicate. A good workflow checks the specific purchase and payment before proposing a financial correction. It preserves the outstanding pharmacy question if that part remains unresolved. If that is the work you need to improve, see our guide to [Intercom for telehealth](https://gosummer.ai/blog/intercom-for-telehealth). It covers the operational evaluation in more detail. ## Where Summer AI belongs in the evaluation Summer AI offers support built around telehealth operations, with a BAA available for every customer. Ask us to show the work your team needs to complete and the tools involved. Confirm the supported connections and commercial terms during that review. [Bring a synthetic case to a Summer AI demo](https://gosummer.ai/book). Include the evidence your staff would normally need and a question that requires follow-up. Compare how easily your team can understand the findings, review a proposed change, and check the result. ## Common procurement questions ### Can we use Essential or Advanced for PHI? Intercom's current public BAA guidance specifies Expert. Obtain written confirmation from Intercom for your intended arrangement before sending PHI. ### Is Intercom an EHR? Evaluate it as customer-service software. Your care platform remains responsible for the clinical records and workflows it owns. Define which information belongs in each system and how authorized staff reach it. ### Does HIPAA support eliminate our configuration work? Your organization still has to assess and operate its deployment. The [HHS Security Rule summary](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html) covers responsibilities beyond the purchase agreement, including risk analysis and safeguards. Use your privacy and security reviewers to apply those requirements to the planned support workflow. ## Connect with Summer AI MCP Use the [Intercom connection guide](https://gosummer.ai/docs/help-desk-connections#intercom) for setup and workflow checks. [Connect your MCP client](https://gosummer.ai/docs/mcp-clients) to inspect your company's configuration and arrange the required access. ## Compare the complete telehealth workflow. Review Summer AI’s BAA and support approach using the records and handoffs your operation needs. [See Summer AI in action](https://gosummer.ai/book) Written by Summer AI, the telehealth support provider discussed in this guide. Connection options can change; confirm current access with your vendor. ## Keep reading - [HIPAA Chatbot With a BAA: What to Check Before You Buy](https://gosummer.ai/blog/hipaa-chatbot-baa) - [Cheaper Intercom Alternatives for Healthcare Support](https://gosummer.ai/blog/cheaper-intercom-alternative) - [Intercom for Telehealth: Patient Support Beyond the Inbox](https://gosummer.ai/blog/intercom-for-telehealth)