.svg)
Is Zoomin being discontinued by Salesforce?
Not exactly — but the practical answer for customers is that you'll need to move. After Salesforce completed its roughly $430M acquisition of Zoomin in November 2024, it set an End of Renewals date of September 1, 2025 for Zoomin products. Salesforce's own wording is precise: this is "end of renewals, not end of life." Your existing contract is honored and supported through expiration — but when it expires, there's nothing to renew into.
A content-strategy consultancy that confirmed the End of Renewals directly with Zoomin summarized it bluntly: Zoomin customers will need to find another alternative. The standalone Zoomin you bought is being folded into the Salesforce platform as "Unified Knowledge," and the path Salesforce offers is either to commit further to its own stack or to wait for a future "agentic portal solution" that hasn't shipped. So while the technology lives on inside Salesforce, the standalone product you licensed is on a clear glide path to retirement — the only open question is your specific contract's expiry date, which for many customers lands in 2026.
This guide is for the service, support, and documentation leaders at doc-heavy enterprises — companies like the McAfee, Dell, and global-brand profile Zoomin served — who now have to decide where their self-service operation goes next. The decision isn't "do we panic," because nothing breaks tomorrow; it's "do we choose deliberately while our contract still runs, or do we default into the Salesforce platform path because the renewal lapsed and that was the path of least resistance." Those are very different outcomes, and the difference is mostly about timing.
📊 Quick Stats:
- Salesforce acquired Zoomin for roughly $430M in November 2024 and set an End of Renewals date of September 1, 2025 (Salesforce acquisition announcement, 2024)
- 74% of B2B buyers prefer to self-serve answers before contacting a vendor, making the documentation portal a primary revenue-adjacent asset (Forrester B2B Buying Study, 2024)
- Self-service plateaus at 25–35% on delivery-only documentation portals, versus 60–80% on platforms that close the support-to-content loop (Forrester Customer Self-Service Wave, 2025)
- Consumption-priced AI bills per task completed, so a successful high-volume self-service deployment costs more as it succeeds (Gartner, AI agent pricing analysis, 2025)
Decision context: Zoomin customers typically decide within the window before their contract expires — the months while the existing portal still runs are the leverage. Default into the Salesforce platform path and the choice is made by inertia; decide deliberately and the owned-foundation path stays open.
👉 Create your MatrixFlows workspace — Import your Zoomin documentation and stand up an owned customer portal while your contract still runs | Book a migration assessment
Was Zoomin a good documentation platform?
Yes — for years Zoomin was the best knowledge orchestration platform on the market, and an honest comparison has to start there. Its core capability was genuinely hard to replicate: ingest technical content from any source — manuals, API docs, support articles, PDFs, structured XML and DITA — and deliver it as one consistent, personalized layer of product answers wherever customers looked, whether a documentation portal, a support community, the service console, or inside the product itself. It was built for the modern reality that technical content is authored by developers and writers in structured formats, not the static-manual world older publishing tools assumed.
Zoomin also personalized well, surfacing the right content by role, product, and version through SSO and rule-based provisioning, with branding teams could control without IT. Its analytics turned content interactions into insight about gaps and behavior — which articles answered questions, which left customers searching, where the documentation needed work. Companies like Rocket Software, Imperva, Shiji, and Sony Interactive Entertainment used it to unify scattered content into a single answer experience. If you're a Zoomin customer, you didn't make a bad choice — you made a good one, and the ground moved under it when Salesforce acquired the company and repositioned the technology.
That distinction matters for how you evaluate alternatives. The question isn't "what went wrong with Zoomin" — nothing did; the product was excellent at what it did. The question is whether the capability you relied on, now that it serves the Salesforce platform rather than existing as a standalone product, is still something you want to depend on, or whether you'd rather own the equivalent capability outright. Being precise about what Zoomin did well — structured-content ingestion, personalization, multi-channel delivery, analytics — is also how you scope a replacement honestly rather than assuming any knowledge tool is a drop-in match.
What actually changed when Salesforce acquired Zoomin?
Salesforce didn't buy Zoomin to keep selling a standalone documentation platform; it bought Zoomin as a data-management capability to feed Data Cloud and Agentforce. Zoomin's technology now lives inside the Salesforce platform as "Unified Knowledge," pulling third-party content from SharePoint, Confluence, Google Drive, and the web into Salesforce so that Agentforce and Einstein can ground their answers in it. That's a legitimate and even powerful use of the technology — but notice what it means for you: the orchestration you relied on now exists primarily to fuel the Salesforce platform, and its stated future is to "standardize on a common Salesforce offering."
So the End of Renewals isn't an administrative footnote. It forces a strategic question into the open: do you want your customer-facing knowledge operation to become a feature inside Salesforce's platform — governed by Salesforce's roadmap and priced on Salesforce's consumption model — or do you want to own it? If you're already all-in on Salesforce, the platform path may be right, and the Service Cloud plus Experience Cloud plus Agentforce direction is a natural continuation of investments you've already made. But it should be a deliberate choice, not a default you back into because a renewal lapsed and the path of least resistance pointed at the CRM you already had.
What is Zoomin today, and who governs its roadmap?
Zoomin today is Salesforce Unified Knowledge — a data-management layer inside the Salesforce platform, not the standalone product you licensed. Why this matters: the roadmap for the capability you depend on is now set by Salesforce's platform priorities, not by a team building a standalone documentation product. The acquisition changed three things a documentation leader feels directly, and naming them plainly is the clearest way to see the choice.
Governance moved to the Salesforce platform roadmap
Your documentation roadmap now follows Salesforce's platform priorities rather than the needs of a standalone documentation product. When the orchestration exists to feed Data Cloud and Agentforce, the features that get built are the ones that serve the platform's agenda — and the standalone-portal capabilities you bought Zoomin for compete for attention against everything else on the CRM roadmap. When this matters: a doc team needs a portal change — a new personalization rule, a structural redesign — and finds the capability is now a configuration question inside Experience Cloud rather than a feature request to a documentation vendor. In MatrixFlows the roadmap serves the knowledge platform itself, so the portal stays a first-class product, not a downstream consumer of a CRM's priorities.
AI moved onto Agentforce and Einstein
Answers now route through Agentforce and Einstein on the Salesforce platform, rather than through something you own and can deploy independently. The AI capability is real, but it's platform-bound — to get it you commit to the Salesforce stack, and you deploy on the platform's terms rather than your own. When this matters: you want a grounded AI assistant on your public docs portal without adopting the full CRM platform to get it. On the Salesforce path that's Agentforce on the platform; in MatrixFlows the AI is grounded in a foundation you own and deploys to customers and partners independent of any CRM.
Economics moved to platform licensing plus consumption
The replacement path is priced through platform licensing plus Agentforce consumption — billed per task the AI completes — which makes your ongoing cost variable and tied to volume rather than predictable. When this matters: self-service succeeds and volume climbs, and the consumption meter turns that success into a rising bill — the better it works, the more it costs. In MatrixFlows the AI is included at a flat subscription with no per-action meter, so volume lowers your cost per resolved issue instead of raising the bill.
✅ Key Difference:
- MatrixFlows: A knowledge foundation you own | roadmap, AI, and cost stay yours
- Zoomin (Salesforce Unified Knowledge): A capability feeding a CRM | governance, AI, and pricing follow Salesforce
What should I look for in a Zoomin alternative?
Look for a unified, AI-ready knowledge foundation you own outright across customers, partners, and employees — not a feature inside a CRM you're being nudged to adopt. That's what MatrixFlows is built to be. Where Zoomin's capability now serves the Salesforce platform, MatrixFlows is a knowledge foundation where every interaction — a customer self-serving, a partner finding an answer, support resolving a ticket — feeds back into one foundation that you control, with the roadmap, pricing model, and data staying yours.
Three criteria should drive the evaluation:
- Ownership — does the platform exist to serve your knowledge operation, or to feed a larger vendor's CRM and AI strategy?
- Portal and search continuity — technical documentation often drives a large share of a doc-heavy company's organic traffic, so the alternative must preserve your URL structure, personalization, and search performance rather than force a rebuild.
- AI economics — is the AI grounded in a foundation you own at a predictable price, or metered per task inside someone else's platform?
Put plainly: Zoomin, now Salesforce Unified Knowledge, is knowledge orchestration absorbed into Data Cloud and Agentforce, with the external experience presuming you build on the Salesforce platform. MatrixFlows is a unified knowledge foundation you own, deploying customer help centers, partner portals, employee resources, and AI assistants from one source, independent of any CRM. For teams that depend on deep DITA or full component content management system authoring, that specific capability should be scoped honestly against your actual usage — which the FAQ below addresses directly.
How do I migrate off Zoomin without breaking my docs portal?
Migrate while your Zoomin contract still runs as a live fallback, so you move deliberately and once rather than scrambling after it expires. Technical product content can account for a large share of enterprise web traffic, so the migration has to preserve structure, URLs, and search continuity — not force a rebuild. MatrixFlows supports structured content migration designed to bring your content across via import and API while keeping your existing portal live during the transition.
The right first step is a migration assessment that maps your specific Zoomin footprint — content sources, portal structure, personalization rules, integrations, and whether you also use Salesforce elsewhere — to a concrete plan and timeline before you commit to anything. This matters more for Zoomin customers than for most, because Zoomin deployments tend to be content-heavy and SEO-sensitive: hundreds or thousands of structured articles, multiple products and versions, and a portal that ranks and drives traffic. The assessment exists to make sure none of that is lost in the move, and to sequence the migration so you can prove the new portal preserves rankings and search behavior on one product area before expanding to the rest. The rest of this guide walks through what moving looks like in practice — across audiences, the owned foundation, AI, the support loop, three-year cost, and representative outcomes.
👉 Book a migration assessment — Map your Zoomin footprint to a concrete plan before your contract expires | Start your free workspace
What does moving off Zoomin actually look like for a documentation team?
💬 Quick Answer: It looks like trading a portal you no longer control for a foundation you own — and the four scenarios below show where Zoomin customers feel the End of Renewals most. Each is a situation where "just move into Salesforce" turns out not to be the same product you originally bought, and where the difference between deciding deliberately and defaulting in becomes concrete. A documentation team's leverage is highest while the contract still runs; these scenarios are where that leverage is worth spending.
What happens to my customer documentation portal when my contract ends?
Why this matters: the documentation portal is often a doc-heavy company's single largest organic-traffic and self-service asset, so where it lives after the contract ends is a strategic decision, not a hosting detail.
📄 Comparison:
What Zoomin (Salesforce path) enables: your portal runs until your contract expires, then there's no standalone Zoomin to renew into. Your external documentation experience presumes you build on Experience Cloud and the future agentic portal, which means your customer-facing portal lives inside someone else's platform roadmap, priced and governed on Salesforce's terms.
What MatrixFlows enables: you stand up a customer help center on a foundation you own, with your branding, your structure, and your URLs preserved, deployable independent of any CRM commitment. Your roadmap, your search performance, and your customer experience aren't subject to a platform vendor's priorities.
When This Matters: a doc-heavy company whose portal drives a major share of organic traffic faces the choice of letting that asset become a configuration inside a CRM it never planned to standardize on, or keeping it on infrastructure it controls. Owning it is the difference between a portal that serves your roadmap and one that serves Salesforce's.
✅ Key Difference:
- MatrixFlows: Owned help center, your URLs preserved | the traffic asset stays yours
- Zoomin (Salesforce path): Experience Cloud + future agentic portal | the portal lives on Salesforce's terms
Can I get AI answers on my docs without buying the whole Salesforce stack?
Why this matters: AI answers are the point of a modern docs portal, but how they're priced decides whether scaling self-service saves money or costs more.
📄 Comparison:
What Zoomin (Salesforce path) enables: external AI answers route through Agentforce and Data Cloud on consumption pricing. Zoomin's AI is now Unified Knowledge feeding Agentforce — powerful, but platform-bound and priced per "Agentic Work Unit," so the cost scales with every task the AI completes.
What MatrixFlows enables: a conversational AI assistant grounded in your verified knowledge foundation deploys to customers and partners, cites sources, and escalates with full context — without an unpredictable consumption bill attached to every answer, and without requiring you to adopt a full CRM platform to get it.
When This Matters: a documentation portal serving high question volume on the consumption model turns a successful self-service deployment into a rising, variable bill — the better it works, the more it costs. On an owned foundation at a flat price, you can let self-service grow without watching a meter, which is the entire economic point of moving volume from humans to AI in the first place.
✅ Key Difference:
- MatrixFlows: AI grounded in your owned foundation, no per-action meter | scale lowers cost per answer
- Zoomin (Salesforce path): Agentforce per-task consumption | scale raises the bill
Will my content stay connected to its sources, or get pulled into a CRM?
Why this matters: where your content's center of gravity sits decides how hard it is to leave later — content consolidated into a CRM's data layer deepens lock-in over time.
📄 Comparison:
What Zoomin (Salesforce path) enables: Salesforce's framing is explicit that Zoomin's orchestration now pulls unstructured content into Data Cloud to fuel Agentforce. Zoomin's strength was orchestrating third-party sources like SharePoint, Confluence, and Jira — but going forward that ingestion increasingly presumes the destination is the Salesforce platform.
What MatrixFlows enables: your content lives in a vendor-neutral foundation you own, serving your portal, your AI, and your internal teams from one place you control, rather than being absorbed as fuel for one vendor's agents. Your knowledge can feed whatever you choose — including a Salesforce integration if you want one — without becoming a dependency of it.
When This Matters: when your content is consolidated into a CRM's data layer to power that CRM's AI, the practical effect over time is deeper lock-in — more of your stack assumes the CRM, and the cost and difficulty of an independent path rises. Keeping the foundation vendor-neutral preserves your optionality.
✅ Key Difference:
- MatrixFlows: Vendor-neutral foundation you own | optionality preserved
- Zoomin (Salesforce path): Content pulled into Data Cloud | content gravity moves into the CRM
How do I decide before my renewal deadline forces my hand?
Why this matters: the End of Renewals is dated, so waiting removes your fallback exactly when you most need one and pushes you into the default platform path under deadline pressure.
📄 Comparison:
What Zoomin (Salesforce path) enables: the renewal lapses, the standalone product disappears, and the route already teed up — the Salesforce platform — becomes the path of least resistance simply because it's in front of you.
What MatrixFlows enables: you migrate via import and API while Zoomin keeps running, stand up one experience first, prove it preserves your structure and search performance, then expand. The transition is deliberate and reversible, not a forced leap at the moment your contract lapses.
When This Matters: the cost of looking now is a few weeks of diligence and a parallel-run period; the cost of waiting is choosing under deadline pressure, from a weaker position, with the platform path as the only one still teed up. For a doc-heavy team, the parallel run is also how you de-risk the SEO migration — you confirm rankings hold on a slice of the portal before committing the whole thing.
✅ Key Difference:
- MatrixFlows: Deliberate, reversible parallel-run migration | you choose from strength
- Zoomin (Salesforce path): Decide at contract lapse | you choose from weakness
👉 Book a migration assessment — Sequence the move while your contract still gives you a fallback | View pricing
If Zoomin is discontinued, where can my Salesforce, Confluence, and product docs go?
💬 Quick Answer: They go into one owned knowledge foundation — the Matrix from MatrixFlows — that unifies content from Salesforce Knowledge, Confluence, SharePoint, and structured product docs and publishes it to your own portal, rather than feeding it into a CRM you don't control. You unify it in one owned workspace that every audience reads from, instead of an orchestration layer that now feeds Salesforce Data Cloud.
For a documentation or support leader at a doc-heavy tech enterprise, the daily problem is that product docs, API references, release notes, support articles, and structured XML or DITA content originate in different tools and have to be pulled together for delivery. Zoomin solved the delivery side of that well; the Matrix solves the ownership side, by being the place the knowledge actually lives rather than a layer that aggregates it for one destination.
Concretely, the Matrix ingests and unifies content from your existing sources and holds it in a foundation you control. It's collaborative by design — real-time editing, comments, review workflows, and version history with rollback — so technical writers, product managers, and support all contribute to one corpus. It's structured for both AI and humans, with content tagged by audience, product, version, and topic and explicit relationships between articles (prerequisites, version dependencies, related procedures) that keep a large library navigable. And it's open to role-based contribution with no per-seat gate. Where Zoomin unified content for delivery and now routes it into Salesforce Data Cloud, the Matrix keeps that same unified corpus vendor-neutral and yours.
How do I unify Salesforce Knowledge, Confluence, and API docs as one versioned source?
Why this matters: at documentation scale, the same fact entered in three systems and updated in one is the core failure mode — version dependencies and cross-references multiply the cost of drift into waves of tickets.
What MatrixFlows enables: you hold every type in the Matrix and let each audience's experience read the right slice, so a single edit propagates everywhere instead of drifting across separate systems. The spec is edited once and the docs portal, the in-product help, and the support reply all reflect it.
When This Matters: a multi-thousand-article corpus across products and versions stays coherent only when the relationships between articles are explicit and the source is singular. A wrong prerequisite or an out-of-date endpoint doesn't just confuse one reader — it generates a wave of tickets. Zoomin's analytics could tell you where content was failing; the Matrix is where you fix it once and have the fix appear everywhere.
✅ Key Difference:
- MatrixFlows: One versioned source, explicit relationships | edit once, correct everywhere
- Zoomin: Delivery layer over separate sources | drift fixed per system
How do I publish a docs portal and partner resource center without losing search rankings?
Why this matters: the personalized, multi-channel delivery Zoomin was known for has to survive the move, and for a doc-heavy enterprise the portal's search rankings are a revenue-adjacent asset that can't drop.
What MatrixFlows enables: you deploy each audience as an experience — the Flows from MatrixFlows — built on the same Matrix corpus, each with its own filters, permissions, and branding. One Flow publishes the public customer documentation portal, another a partner resource center behind login, another an internal engineering reference — all reading from the Matrix, so updating the underlying content once updates every destination.
Flows also do what a delivery portal alone cannot:
- Host grounded AI assistants trained on the complete corpus, deployable to the docs portal, a support community, or embedded in the product.
- Preserve URL structure and search performance a doc-heavy enterprise depends on, so the portal stays the organic-traffic asset it has become.
- Run transactional workflows — guided troubleshooting, version-specific setup, ticket-deflection paths — not just static article display.
When This Matters: a doc-heavy team migrating off Zoomin needs to prove rankings hold before committing the whole portal. The capability that made Zoomin valuable is reproduced here on infrastructure that stays yours, rather than presuming Experience Cloud and a future agentic portal as the delivery surface.
✅ Key Difference:
- MatrixFlows: Audience-specific Flows on one owned corpus | delivery plus AI, workflows, and SEO continuity
- Zoomin (Salesforce path): Delivery presuming Experience Cloud | the delivery surface isn't yours
How do I act on the doc-search-returned-nothing signal Zoomin only showed in analytics?
Why this matters: readers constantly tell you where the docs fall short — a confusing step, a missing API example, a feature request — but in a delivery-only world those signals end in an analytics report and the writing is still on you.
What MatrixFlows enables: it captures the signal as a tracked, deduplicated request straight from the docs portal — every Flow can capture "this didn't answer my question," documentation feedback, and feature requests, route them to the right owner, and reply to the reader once there's an answer. The feedback is captured in context — what the reader was viewing, what they searched, what the AI told them — so it becomes a tracked signal rather than a lost comment.
When This Matters: inbound, this tells your team exactly which articles to fix and which features readers keep asking for, straight from the portal. Outbound, you reply to the reader when the doc is updated or the feature ships, closing the loop. These land in the Conversations Inbox, and an answered request can become a documentation article in one click — so the next reader with that question finds it. In a Zoomin-plus-help-desk world, that loop stayed open.
✅ Key Difference:
- MatrixFlows: Feedback captured in context, routed, answered, published | the loop closes
- Zoomin: Search-returned-nothing visible in analytics only | the loop stays open
How does MatrixFlows AI compare to Zoomin's AI now that it is part of Agentforce?
Zoomin's AI is now platform-bound to Salesforce Agentforce and Einstein; MatrixFlows grounds AI in a foundation you own and deploys it to customers and partners through eight capabilities, with no per-action meter. The comparison is less about model quality — both can be capable — than about ownership and economics: whether your AI runs on a foundation you control at a predictable price, or as metered usage inside a CRM platform you are being steered to adopt. Here is what the MatrixFlows AI layer does, capability by capability, and how each compares to the Salesforce path Zoomin customers are now pointed toward.
Can AI answer on my docs by product and version, not a near-match?
MatrixFlows runs role-, product-, and version-aware personalization on a foundation you own — the same signature strength Zoomin had, except its version now feeds the CRM's agents rather than a portal you control. Surfacing the right content by who you are and which release you run was Zoomin's hallmark, and it was real; the shift is who that capability serves. In MatrixFlows, context-aware semantic search intersects intent with the audience, product, and version tags on each article and the user's permissions before ranking — which for a multi-product, multi-version corpus is the difference between a customer finding the exact answer for their release and being shown a near-match for a different version.
Can AI answer on my docs without Agentforce per-task pricing?
MatrixFlows completes tasks grounded in your foundation with no per-action meter, where on the Salesforce path transactional automation runs through Agentforce priced per task the AI completes. That meter is the structural point: every completed action is a billable event, so a successful, high-volume self-service deployment costs more precisely because it succeeds — scale works against you. In MatrixFlows the functional capability is comparable — walking a customer through a request, validating inputs, and submitting it in chat or voice — but the economic model is inverted: on an owned foundation at a flat price, volume lowers your cost per resolved issue rather than raising the bill, which is the entire point of self-service.
Can I author and maintain a versioned docs corpus in the platform, or only deliver it like Zoomin?
MatrixFlows adds the authoring-and-maintenance layer Zoomin never had — Zoomin excelled at delivering and analyzing content, but producing and maintaining it happened in your CCMS or editor. Four assistants handle the work a docs team actually does day to day: drafting and re-toning per audience, capturing decisions and surfacing gaps from calls, synthesizing across the corpus with citations, and flagging what has gone stale. Keeping hundreds or thousands of articles current across products and versions is that daily work, so an assistant layer aimed at it — rather than only at how finished content is presented — is where the time is saved.
How does a multi-product, multi-version DITA corpus stay organized after leaving Zoomin?
MatrixFlows maintains the taxonomy, version links, and prerequisite relationships automatically as content is created, where in Zoomin that structure came from the upstream DITA or CCMS source and was maintained by your team. Zoomin organized delivery well, but the relationships were manual work that strains at scale. Relationship mapping matters most for technical docs, where prerequisites, version dependencies, and related-procedure links are what make a corpus navigable — having the AI propose and maintain those connections is what keeps a multi-thousand-article library from degrading into a pile only full-text search can cross.
Can an assistant author and translate technical docs across every product version?
Yes — MatrixFlows drafts, re-tones, and translates in 100+ languages from one source, keeping technical terms consistent across versions, where in Zoomin localization was an upstream project per language per release. For the global, doc-heavy enterprises that were Zoomin's core customers, content was translated in a separate system, then ingested and delivered — a recurring cycle each release. In MatrixFlows translation is an operation on the single source rather than a parallel copy per language, so a source change retranslates everywhere and technical terms stay consistent, replacing a per-language, per-release localization workflow with one that maintains itself.
Can AI draft a support reply from the same docs Zoomin only published outward?
MatrixFlows drafts complete support replies grounded in the same docs that power the portal — real answers, not links — where Zoomin was a delivery layer that published content outward but did not draft an agent's reply. On Zoomin that meant a separate help desk and a human doing the search-and-rewrite by hand. In MatrixFlows the agent reviews, personalizes, and sends, dropping time-to-first-response, and because the drafted reply is grounded in the same foundation that powers the customer portal, the answer an agent sends matches what self-service would have shown — consistency built into the architecture rather than maintained by hand across separate systems. Every resolution can then feed back into the documentation.
Does a resolved ticket flow back into the docs, or stop at Zoomin's delivery layer?
In MatrixFlows a resolved conversation becomes a doc in one click; in Zoomin it stopped at the delivery layer. Zoomin published documentation outward while the tickets lived in a separate help desk, so a resolved issue never became a doc on its own and the loop between solving a problem and documenting it stayed open. MatrixFlows drafts the problem statement, solution steps, and related resources in the right style for the audience, which turns the support queue from a cost center into a source of coverage — the questions customers actually ask and the answers agents actually give become the next articles, so the portal grows toward real demand rather than toward what a content team guessed would be needed.
How do I find what is missing from my documentation?
MatrixFlows watches for questions the foundation cannot answer yet and auto-drafts the missing article, where Zoomin's analytics reported the gap and left the writing to you. Zoomin's reporting was a genuine strength — it told you what customers searched for and found nothing — but acting on it was a scheduled, usually quarterly, content project. MatrixFlows is the proactive complement: rather than flagging a search that found nothing and leaving you to write, the system flags the gap and has already drafted the fix from those conversations, so closing it is a review-and-publish task rather than a research-and-write one.
Where this nets out — what an owned foundation does that a delivery layer feeding a CRM does not:
- Serves every audience — customers, partners, and employees from one foundation, not a CRM-scoped path.
- No per-action meter — answering more questions does not raise the bill.
- Authors and maintains, not just delivers — drafting, re-toning, translating, and staleness flags built in.
- Turns support into docs — a resolved conversation becomes an article in one click.
- Closes its own gaps — missing articles are detected and drafted continuously.
Can I turn reader feedback and support tickets into documentation automatically?
Yes — MatrixFlows captures documentation feedback, unanswered searches, and support tickets in one place and turns them into published docs, where a delivery portal plus a separate help desk leaves those signals stranded. For a documentation or support leader at a doc-heavy enterprise, this is the loop that actually moves a self-service rate: every support conversation strengthens the documentation foundation rather than disappearing into a help desk. Conversations from customers and partners land in one queue with context: what self-service they tried, what they read, where they got stuck. AI drafts a grounded response; the agent reviews and sends, or escalates to your existing Salesforce or Zendesk with full history attached. Resolved conversations become articles in one click, so the documentation improves through use rather than sitting static between manual updates — which a delivery portal, however well it personalizes, cannot do on its own.
This is the capability gap that even an excellent orchestration-and-delivery platform left open. Zoomin was outstanding at taking content authored elsewhere and delivering it everywhere customers looked, with deep analytics on how that content performed. What it did not do — because it was not its job — was close the loop between the support conversations happening downstream and the documentation upstream. In a Zoomin-plus-help-desk world, a resolved ticket and the documentation it should improve live in different systems, and the manual work of turning one into the other rarely survives a busy week. On one foundation, the resolution and the article are the same object, so the portal compounds toward real customer demand automatically. For a documentation team measured on self-service rates, that loop is the mechanism that moves the number.
What does staying on the Salesforce path cost versus moving to MatrixFlows?
Illustratively, the Salesforce replacement path runs to roughly $418,000+ over three years for a ~2,000-employee doc operation, against roughly $105,000 for MatrixFlows at the same company size — because the Salesforce path bundles your portal, AI, and support into platform licensing plus per-task Agentforce costs. Zoomin's standalone pricing was never public (quote-only), so the comparison below models the path Salesforce now steers Zoomin customers toward. Every figure is illustrative and should be confirmed against your own Salesforce quote; the structure, not the precise total, is the point — a platform-plus-consumption model bills separately and variably for what an owned foundation includes at a flat rate.
How does the Salesforce Agentforce consumption model compare to MatrixFlows?
Zoomin never published standalone pricing; it was quote-only and negotiated per deployment, so there is no list price to compare against. The relevant comparison is therefore to the replacement path Salesforce now points customers toward: platform licensing for Service Cloud and Experience Cloud, plus Agentforce consumption charges billed per task the AI completes, plus Data Cloud for the knowledge unification Zoomin used to provide. That consumption component is the structurally important one — it makes the ongoing cost variable and volume-dependent, so a successful self-service deployment becomes more expensive as it succeeds. MatrixFlows uses predictable subscription pricing with AI included and no per-action meter, so you can model your cost in advance and let volume grow without watching a meter. It also isn't priced per user: every person in your organization gets access, and there are no per-resolution or per-action fees and no charges for the end users you serve — customers, partners, or employees — so reaching more audiences never adds a line item.
What does the Salesforce replacement path cost over three years versus MatrixFlows?
We compare like for like: a roughly 2,000-employee, multi-product technology company — the doc-heavy buyer that actually runs Zoomin — not a 10-seat team. For that buyer the Salesforce replacement path over three years runs roughly: Service Cloud licensing for the support/agent layer at ~$150/user/mo × 40 users × 36 months ≈ $216,000; Experience Cloud for the customer portal (per-login or per-member pricing) at ~$1,500/mo × 36 ≈ $54,000; Agentforce consumption (per Agentic Work Unit / per resolution), highly variable, modeled at ~$2,000/mo × 36 ≈ $72,000; Data Cloud for knowledge unification at ~$1,000/mo × 36 ≈ $36,000; and implementation and integration services ~$40,000+ one-time — an illustrative three-year total around $418,000+, with the consumption line as the largest and least predictable variable. The same multi-audience scope on MatrixFlows, for a company that size, is the Platform plan at $35,000/year (~$105,000 over three years) with unlimited contributors, AI included with no per-action meter, customer, partner and employee audiences from one foundation, and Conversations Inbox built in — roughly $105,000 vs $418,000+, about a quarter of the cost. Smaller teams land lower (the External plan starts at $12,000/year), but even at the Platform tier the gap is wide. Confirm every Salesforce figure against your actual quote, since consumption pricing varies widely by usage; the architecture, not the discount, is the point.
Past Agentforce consumption, what does leaving the Salesforce path save operationally?
MatrixFlows teams cut manual content-management overhead 60–70% and move self-service from the 25–35% range toward 60–80% within six months — operational savings that compound on top of removing the per-task consumption meter. Teams that unify documentation and support typically move self-service from the 25–35% range common with disconnected systems toward 60–80% within six months, cutting contact volume and freeing the documentation team from firefighting to higher-value work. MatrixFlows verified outcomes include 60–80% self-service within six months, a 70% reduction in article-creation time, and a 60–70% reduction in manual content-management overhead. For a doc-heavy enterprise, the content-overhead reduction is often the most valuable line, because maintaining a large structured corpus across products, versions, and languages is exactly where these teams spend most of their time today.
What does switching off Zoomin look like in practice?
Teams typically migrate their documentation portal on their own timeline before contract expiry and come out owning a foundation rather than renting one — the representative scenarios below show the pattern (composites with directional figures, not named customer case studies).
A high-tech documentation team facing End of Renewals
A software company ran a large Zoomin documentation portal with hundreds of structured articles across multiple products, then received the End of Renewals notice. Rather than default into the Salesforce platform path, the team migrated to a MatrixFlows foundation while Zoomin ran as a fallback, preserving URL structure and personalization rules and validating rankings on one product area before moving the rest. Illustrative six-month results: the customer documentation portal moved without a ranking drop, AI self-service answers deployed without per-action metering, and the team gained an authoring-and-gap-detection layer the delivery portal never had — so coverage began improving through use rather than only through scheduled content sprints.
A multi-brand enterprise consolidating scattered docs
An enterprise serving several product brands had documentation spread across portals and shared drives, unified only at the delivery layer by Zoomin. Moving to one owned foundation, the team deployed a branded portal per audience from a single source, so a product-spec change propagated everywhere at once instead of being reconciled by hand across brands. Illustrative outcomes: article-creation time down about 70%, content-management overhead down sharply, and a measurable rise in self-service as the foundation improved through support resolutions. The consolidation also removed the quiet risk of brand-to-brand drift, where the same component carried different documented specs in different places.
A global documentation operation escaping per-task AI costs
A doc-heavy enterprise serving customers in a dozen languages had begun down the Agentforce path for AI answers and watched the projected consumption cost climb with every modeled increase in self-service volume — the more the AI worked, the more it would cost. Moving the documentation foundation and its AI assistant to MatrixFlows, the team grounded answers in their owned corpus with translation handled from one English source, at a flat subscription rather than a per-task meter. Illustrative outcomes: AI self-service deployed across all languages without a consumption line item, translation cost effectively eliminated as a separate spend, and a self-service rate the team could grow aggressively precisely because growing it no longer raised the bill. The decision came down to wanting scale to lower cost per resolution, not raise it.
What is the common pattern among teams leaving Zoomin?
None of these moves required ripping out the existing CRM or help desk — each built the owned knowledge foundation that the rest of the stack could draw from, and each used the End of Renewals as the reason to decide deliberately rather than default into a platform path. That is the architectural difference: Zoomin's orchestration now serves the Salesforce platform; MatrixFlows is the knowledge foundation you own and deploy to every audience on your own terms. The teams that come out ahead treated the dated deadline not as a crisis but as a prompt — using the months while their contract still ran to migrate on their own schedule, preserve their SEO, and land on a foundation whose roadmap and cost they control.
Decide before your contract expires, not after. Every MatrixFlows plan includes the full Matrix knowledge foundation, AI assistants, and multi-audience access controls. Import your Zoomin documentation and see what an owned, multi-audience foundation looks like in practice — while your current contract still gives you a working fallback and the time to choose deliberately.
Ready to own your knowledge operation instead of renting a slice of a platform? Book a personalized demo. We'll walk through your specific situation — preserving your portal structure and URLs, grounding AI without per-action metering, and migrating off Zoomin before your renewal lapses.
.svg)
.svg)
