Most channel teams still ask partners to log in to a portal before a deal counts. I think that requirement now costs more pipeline than it protects, and the partner software released this week shows a way to drop it while keeping the controls that made the portal worth having.
What shipped this week
On November 12, ZINFI Technologies launched what it calls omnichannel and headless partner management in its Unified Partner Management platform. Channel partners and partner teams can now ask about, update and collaborate on Registered Deals from the partner portal, Slack, Microsoft Teams and Claude, through one assistant that works under the same permissions as the portal. It extends an MCP server ZINFI opened in early access on August 24, 2026.
The reason ZINFI gives is about where partners spend their day. Its release says that in ZINFI discovery conversations, channel and partner program leaders routinely report that deal registration sits in spreadsheets, because updating a portal is one more place to go. That is a vendor’s account of its own sales calls, so I treat it as a reported pattern; the release gives no figure for how common it is.
Advertisement
Sugata Sanyal, Founder and CEO of ZINFI Technologies, said, “Channel partners don’t live in vendor portals anymore; they work in Slack, Microsoft Teams and their own AI assistants.”
The same day, Mindmatrix announced a partnership with the experience strategy firm Bodine and Co. to pair its GTM Operating System, introduced in October 2026, with Bodine and Co.’s Partner Experience services. Vaughn Mordecai, Chief Revenue Officer at Mindmatrix, said, “Partner programs stall when strategy and technology pull in different directions.” Two vendors in one day framed partner pipeline as a problem of where the work happens.
The case for keeping registration in the portal
The strongest argument against my position comes from channel managers. Deal registration exists to settle conflict: two resellers working the same account, a partner and a direct rep chasing the same buyer. A portal form forces the fields, the timestamps and the review into one place. Let partners register deals by typing a sentence into a chat window and you invite vague submissions, duplicate claims and arguments about who registered first.
Why I still think the portal requirement should go
The answer is in how ZINFI scoped the chat side, and it is the design I would ask any partner platform to match.
First, approval never left the portal. ZINFI’s release says approvals, rejections and status changes are portal-only, and only deals in Design for Submission or Ready for Submission can be edited from chat. The conflict decision still happens in one place, by the same people.
Second, a change from chat does not save on its own. Every change requested from chat is a proposal that works once, expires after 10 minutes and saves only when the same person confirms it in the same conversation.
Third, the fields are fenced. Lead source, expected close date, sales stage and amount can change from chat, and the release says the server refuses any other field. A partner sees only its own company’s deals.
Fourth, the record stays whole. Every confirmed change is recorded once in the deal’s Activity with the person, the time, the channel and the before and after values. That timestamp is what a channel manager needs to settle a first-to-register dispute, and it is captured whether the partner typed in Teams or clicked in the portal.
With those four controls in place, the portal login stops doing any governance work. It only adds a step between a partner learning about a deal and our system knowing about it, and every day a deal sits in a reseller’s spreadsheet is a day it is missing from the channel forecast.
What I would ask channel leaders to do
Start by counting how many deals reach your program late. Compare the date each registered deal was created with the earliest activity date the partner reports for it. A long gap means partners are working deals before they tell you, and that is pipeline your forecast cannot see.
Then accept registrations from the tools partners already use, on four conditions you can put in the requirements for any vendor: approvals stay in one system, chat edits need a named person’s confirmation, the editable fields are listed, and every change carries a before and after value in the deal history. If a platform cannot meet all four, keep the portal form.
Finally, watch the four fields chat can change. Sales stage, amount and expected close date feed the channel forecast directly, so give RevOps a weekly report of chat-made changes to them, filtered by partner.
I have argued for giving channel partners the certifications your own sellers hold on the same logic: partners perform like the direct team when they get the same access. Microsoft, HubSpot and Salesforce have each shipped MCP servers that let AI agents reach CRM data, and Salesforce has said half of Slack messages now come from apps and agents. Partner deal data is moving into the same assistants and chat tools.
Source: ZINFI Technologies
