Skip to main content
September is the month money started moving. Introw Pay pays every partner from one invoice, commission plans read a CSV or Excel file, and partners set up how they get paid in your portal. Workflows write with the data of each run, announcements get categories, Salesforce gets the partner panel HubSpot already had, and partners can update many deals at once.
Commissions were the last part of the program that still grew with headcount: Introw worked out what partners earned, and finance spent the week paying it one transfer at a time. Introw Pay and file imports remove that week, which is the low total cost of ownership bet applied to the money itself.

Pay every partner from one invoice with Introw Pay

On a payout batch, choose Pay now and Introw issues one invoice to your company, with a line per partner. You pay it once by bank transfer, and Introw Pay sends each partner their share in their own currency, moves the payout to Paid and emails them the statement. Partners verify themselves and their bank account in your portal, so your team never collects bank details. Anyone not ready yet stays in the batch for the next run, and Remind to set up payouts nudges them.
Commission lines from the CRM, billing, a file upload, certificates, journeys and workflows flow into one Introw Pay invoice, which pays four partners in their own currency, each marked Paid

Commission from every source lands on one invoice, and Introw Pay pays each partner in their own currency.

Every payment in and out is a row on the new Payments tab. Finance pays one supplier invoice a cycle instead of hundreds of transfers, which is the low total cost of ownership bet, and verification per partner is what keeps it enterprise-grade at five hundred partners. Switch it on in Payout Settings (company currency in EUR or USD, billing info complete); Manual invoicing stays as it was. Introw Pay is included in every plan, with a fee on the transactions it processes and nothing extra on your subscription. See Introw Pay, Pay a payout cycle with Introw Pay, and Get partners ready to be paid.

Pay commission on revenue that never reaches your CRM

Distributor sell-through, marketplace statements and usage exports arrive as files, so they were paid by hand. A commission plan can now use File upload as its data source: map the columns of one sample CSV or Excel file once, and every later file follows that mapping. Each row pays the full amount, a percentage or a fixed fee, with your usual rate targeting and caps.
The import detail for distributor-sell-through-september.csv: 6 rows in the file, 4 commission lines, 2 on hold, status Import complete, and the On hold tab listing two rows with No partner match.

An imported file in detail: 4 rows became commission lines, and 2 rows are on hold with the reason next to each.

Each period is an upload on the Imports tab. Introw holds the rows that need a person, such as no partner match or no rate that applies, and you assign or skip them. Re-uploading is safe, a row whose figures changed is flagged instead of overwritten, negative rows reverse as credits, and every line keeps the file and row it came from. Paying file revenue on the same rules as CRM revenue, with no spreadsheet math, is the low total cost of ownership bet. See Import commissions from a file and Commission plans.

The commission statement, rebuilt

Every row on the statement now prints its calculation, such as EUR 4,200.00 x 10%, whether the line came from a plan, a file, a manual adjustment or the API. The statement opens with your logo, the period and an Invoice to block with your VAT number, closes on Amount to be invoiced, and leaves out declined and postponed lines.
A commission statement PDF with the logo and, beside it, an Invoice to block with address and VAT number, then the period Jun 4 to Jul 5, 2026, For UnitedHealth Group, and lines such as USD 19,359.04 x 10% = USD 1,935.90.

The rebuilt statement: your Invoice to block with your VAT number beside the logo, the partner it is for, and the calculation on every line.

The Statement note now takes Markdown, with headings, lists and clickable links. When finance has its own document, Upload your own serves that PDF everywhere the generated one went. A partner who can check the numbers themselves does not email you about them, which is the low total cost of ownership bet. See Payouts.

Choose what partners see in the Commissions section

The Commissions section in your portal now has a Configure panel: rename, remove or reorder the columns partners see per payout and per commission item, such as “Deal” instead of Commission item.
The Configure panel on a Commissions section: a Payouts table list with Amount, Owner, Period, Status, PO Number, Invoice link and Commission statement, and a Payout details list starting with Commission item.

Configure the columns partners see: rename, remove and reorder the payouts table and the commission items inside a payout.

Every payout also gets a Download statement column, which sections you never configured show straight away. Speaking your program’s language on the page partners open most, without a ticket, is the low total cost of ownership bet. See Choose what partners see in the Commissions section and Payouts.

Payout setup gets its own portal section

With Introw Pay on, add a Payout setup section from Smart sections. Partners work through Business details, Payout method and Verification, and once verified the card shows the account they are paid to.
A partner portal preview with the Commissions totals over a payouts table reading Payout amount, Owner, Period, Status, Invoice link and Commission statement, and the Payout setup card under it with Business details and Payout method marked To do.

The partner's Payouts tab: the commission table with the columns you named, and their own payout setup under it.

It stays hidden on manual invoicing. Partners finish setup in the portal they already use, which is the work where you already are bet. See Get partners ready to be paid.

Build a whole payout over the API

The commission API can now build payouts. Open a batch for a period with POST /api/v1/payout-batches, add a partner’s payout with POST /api/v1/payouts, attach lines with POST /api/v1/commission-lines, and render the statement with POST /api/v1/payouts/{id}/statement. Open the batch first, so ten partners stay one run instead of ten.
Build a payout over the API
A finance stack that owns the period, the partners and the amounts can run the whole cycle without opening Introw, which is the work where you already are bet. See Feed your finance stack from Introw and Commissions over the API.

Workflows write with the data of the run they are in

Any text a workflow step writes now takes variables: the CRM note, the task, the commission description, the email subject and body, and the chat message. Type { and pick a value, such as the partner’s name, the journey they finished or the amount an earlier step booked.
A workflow that gives a commission when a journey is completed, with its Send an email step addressed to the partner champion and a subject and body filled with Partner name, Journey name, Today, Formatted amount and In 7 days variables

One email step that names the partner, the journey they finished and what they earned, written once for every run.

Values are grouped From trigger, From actions and Always available, and a workflow that points at a value it can no longer reach cannot be switched on. A thank-you note that names the partner and what they earned, written without a developer, is the low total cost of ownership bet. See Personalize workflow steps with variables and Workflows.

A portal feed per topic with announcement categories

An announcement now carries Categories, such as Product releases or Events and webinars. Each announcements section shows only the categories you keep under Filter by category, so a Home tab can carry a product feed next to an events feed, and the commissions tab only the incentives.
The Configure announcements sheet in the experience builder with Filter by category on, only Product releases ticked, and the Author and date toggles below.

Filter by category on an announcements section, narrowed to Product releases, with Show author and Show timestamp under Author and date.

A category you add later never lands in a filtered feed by accident, and sections published before this keep showing everything. The list gets a Categories column and filter, and Show author and Show timestamp decide per section what partners see. Shaping the feed in the builder rather than in a ticket is the low total cost of ownership bet. See The announcements section in the portal and Send an announcement.

Work with partners from inside Salesforce

The Introw collaboration panel now sits on Salesforce Opportunity and Case pages, as the Introw card already did on HubSpot deals. It lists every partner on the record with their tier, champion and contacts, and Ask AI, Collaborate and Share opportunity open Introw on top of the record. An AE answers a partner there and then, with no second tab and no Introw login.
A Salesforce opportunity with the Introw collaboration panel in the record layout, showing the partner and their Gold tier, the team and the partner collaborators, and Ask AI, Collaborate, View portal and Share opportunity

The Introw collaboration panel on an Opportunity: the partner and their tier, who is on the deal from both sides, and the actions a rep takes without leaving the record.

It loads for users with the Introw Collaboration User permission set, and ships in IntrowPRM 1.15.0 on Salesforce AgentExchange, with ready-made record pages. Older orgs see Install update on the Salesforce integration page. The same partner view in either CRM is the CRM-native bet. See Collaborate from Salesforce opportunities and cases and Embed Introw in Salesforce.

A deal property that shows only when it matters

Each property on a shared pipeline can now have visibility conditions, set with Configure visibility next to Show on card. A discount field appears only once a deal reaches negotiation, and a loss reason only on Closed lost. It applies on the portal card, the deal, the table view and the HubSpot partner card.
The Property visibility dialog on a shared pipeline, reading Show Annual contract value when Deal Stage is any of Contract Sent, with the Show on card switch below.

Annual contract value set to show only on deals at Contract Sent or Closed Won.

With August’s stage-aware action buttons, you now shape what a partner sees and does on a deal from one screen. Segments still decide access. That is the low total cost of ownership bet applied to the pipeline. See Show a property only when it matters, Set up a shared pipeline and Pipeline rules.

Update many records at once from the portal

In a table view, partners can now tick up to 100 records: Edit sets one editable property, such as a close date, on all of them, and a custom action runs its form once per record.
A partner's shared deal pipeline with three deals ticked, and the Update deal form reading 3 deals selected, submitted once for each selected record

Three deals ticked in a partner's table view, and one update form submitted once for each of them.

Your CRM, approvals and automations still see each record on its own. An end-of-quarter clean-up in minutes is the CRM-native bet at partner speed. See Let partners update many records at once and Bulk actions in the table view.

Group portal tabs into dropdowns and add URL tabs

Add in the experience builder now opens one dialog where you pick a Tab, a Tab group or a URL. A tab group is one item in the portal navigation with a dropdown of tabs, so a Sales kit can hold battlecards and pricing without crowding the bar. Move tabs in with Move to group or by dragging, and Ungroup puts them back.
A partner portal navigation with the Sales kit group open on Battlecards and Pricing and a Help center link, next to the three kinds of navigation item: Group, Page and URL

Group related tabs under one item, and link out from the navigation.

A URL tab opens a link, such as your community or help center, and Introw checks the link before you can add it. Groups and URL tabs follow the same hide and segment rules as any tab. Reshaping the navigation yourself as the program grows is the low total cost of ownership bet. See Design the portal’s tabs and navigation.

The form’s Automation tab, rebuilt around the record it writes

A form’s Automation tab now reads top to bottom: Submission, Review, Notifications and Records written. Each record automation shows the record it writes, how it matches, the partner links, the mapped fields and the defaults. Values Introw fills itself show as locked rows, so one screen shows everything a submission creates. A Salesforce lookup such as the primary partner contact now fills from the contact the same submission created.
A form's deal automation open on the Automation tab, with Partner links above the form fields mapped to HubSpot deal properties, and the default values below them, including the rows Introw fills and locks itself.

A deal automation top to bottom: the partner it gets attached to, the fields the partner fills, and the values Introw sends itself.

The approval gate is now three choices: Manual, AI Assisted and Autonomous AI (Agentic), where the AI clears routine cases above a confidence you set and the rest go to your approvers. How much the agent decides is one visible choice, which is the AI-native bet with the human where you put them. See Connect a form to your CRM and Run a submission approval workflow.
A form's Approval gate set to Autonomous AI, with Manual, AI Assisted and Autonomous AI beside each other, the plain-language guidance Introw AI judges against, the confidence it has to clear to act, and three approval steps in order.

One question at the top decides how much of the review Introw AI owns; the guidance and the confidence bar under it are what it is held to.

Agents update deals through your own action buttons

When a partner asks the agent to change a deal, anywhere they talk to it, it now uses your custom action button, such as Move to next stage, with its guardrails and approvals, which is the AI-native bet done properly. See Partner support agent and Let partners update a deal with guardrails.
The Custom action visibility dialog: Show Edit button when Deal Stage is none of Closed Won and Closed Lost.

The rule the agent inherits: this Edit button only shows while the deal is not closed, so the agent cannot use it on a closed deal either.

The Introw bot answers in Microsoft Teams

The Introw app in Teams now holds a conversation: ask it for partners or deals, or to register a deal, in a personal chat or by mentioning it in a team. Shared channels show in the channel picker, and it is added as a custom app while the store listing is pending. Meeting your team in the chat tool it already has open is the work where you already are bet. See Connect Microsoft Teams and Configure partner notifications in Microsoft Teams.
The Link Microsoft Teams channel dialog with Run your partner program from Teams, three benefits, and the quick setup starting with Download the Introw app package.

Connect Microsoft Teams from Integrations: add the Introw app as a custom app, then connect your tenant.

Also in this release

Commissions and MDF
  • Commission reports show where each line came from, with new origin columns and filters, installment progress after the plan name, and the rate on manual and API lines. See Feed your finance stack from Introw.
  • File plans pay partner, segment and tier rates, and skipping imported rows lets you upload a corrected file. See Import commissions from a file.
  • A contact who only sees their own deals only sees their own commission lines, in the portal and in the agent’s answers. See Payouts.
  • MDF budgets count approved requests, and a fund’s page shows the requests routed to it. See Marketing development funds.
  • Give commission starts on your company currency, and clearing it pays in each partner’s own currency. See Commission lines.
  • Commission reports convert every line to one currency before they add up, with multi-currency or Introw Pay on. See Report builder.
  • Fund requests and claims can be portal sections. See Every portal section.
  • A pending MDF request shows no approved amount until it is accepted. See Proposals.
  • Partners do not see internal commission filters such as Source, Workflow and Form. See Commission lines.
Workflows and notifications
  • Update partner contact properties is a new step that can also open or revoke portal access. See Workflows.
  • A Workflows switch on a role decides who can build workflows; existing roles have it on, except CRM-only roles. See Create an internal role.
  • CRM record updated workflows ignore bookkeeping changes such as last-modified fields. See Workflows.
  • Workflow emails send even with announcement emails off, and workflow tasks are due at the end of the day in your time zone. See Workflows.
  • Trigger HubSpot workflows from partner engagement, with Introw events on the contact and company timeline. See Trigger HubSpot workflows from partner engagement.
  • A first CRM sync no longer announces old deals as new. See Notifications.
  • Notifications name the partner who acted, and CRM lookups show names instead of IDs. See Notifications.
  • Every email automation on a form sends, even when an earlier one has no recipients. See Every notification Introw sends.
  • Announcement tests go to several addresses at once, the To count shows who was actually emailed, and From shows your verified sender. See Announcements.
  • Task due dates end on their own day. Journey tasks, Assign journey, Give a task and welcome tasks are due at the end of the day in your time zone. See Build a journey from scratch.
  • A suppressed email address no longer stops the other recipients of a form email. See Troubleshoot partner email delivery.
Portal, forms and pipelines
  • Any CRM object can be a portal section, custom objects included. See Every portal section.
  • A call-to-action button can have its own color and land on a specific section. See Every portal section.
  • HubSpot custom objects get the board view, and a pipeline rule that refuses a drag tells the partner why. See Shared pipelines.
  • Partners see the form confirmation right away, and the pipeline picks up the new record without a reload. See CRM automations.
  • Form automations set the Salesforce Record Type, and stage fields offer a custom object’s own stages. See CRM automations.
  • A form’s CRM record filters apply to partners too, in the portal and over the API. See CRM automations.
  • Duplicate a form field from its handle menu, configuration included. See Form builder.
  • A form lookup can point at a record another automation on the same form creates, such as a deal pointing at its new contact. See CRM automations.
  • Multi-select questions take Select all, including on a search. See Form builder.
  • Website form embeds resize themselves, once you copy the snippet again. See Ways to submit a form.
  • Joining a segment enrols a partner in that tab’s journey. See Auto-apply a journey.
  • Portal invites take an optional first and last name. See Invite partners and their teams.
  • Accept a pending portal contact by switching on their access from the People row. See Portal access.
  • Failed logins no longer create CRM contacts, an off-portal form adds its submitter only when Auto-invite submitter is on, and refreshing a portal link keeps you signed in. See Portal access.
  • Links from your old portal land on your Introw portal. See Redirect old portal links.
  • Dark portal backgrounds read right in the builder and on the login page. See Brand the partner portal.
  • English (UK) is a portal language. See Multilingual.
  • Sharing a record no longer subscribes everyone to its updates. See Share a CRM record.
  • Quote errors name the missing HubSpot permission, a quote needs a line item to publish, and a quote form prefills the deal’s current stage again. See Quotes.
  • Form lookups can use Partner contact, and a contact on another account is never written. See CRM automations.
  • A pipeline narrowed to one stage shows as a one-column board in the portal. See Shared pipelines.
  • A partner who edits a custom-object record on a plan without custom-object collaboration sees why, and your team gets an upgrade button. See Shared pipelines.
  • Sections can be colorized, padded and moved to another tab, and text in a colored section flips light or dark by itself. See Portal experiences.
  • Button labels fall back to a readable color when your Button text color measures under 3:1 against the button, in the portal and in emails. See Brand the partner portal.
  • A quote’s buyer edits reach the end customer’s company, and saving a quote untouched no longer reverts them. See Quotes.
Partners and your team AI and MCP Courses and content Integrations
  • A note forwarded out of your CRM no longer loops back: Introw skips its own notes, and a flow that forwards notes over the API sends metadata.source as CRM. See Comments forwarded out of your CRM.
  • Crossbeam needs no partner mapping. See Crossbeam.
  • Introw says when HubSpot never granted an object. See HubSpot permissions and scopes.
  • Connecting Salesforce always asks you to sign in. See Connect Salesforce.
  • Salesforce reports fill in Days to close, stage filters are dropdowns again, and dependent picklists follow their controlling field. See Report builder.
  • Chargebee sites on the older product catalog connect. See Connect Chargebee.
  • The DKIM record name stays visible after it verifies. See Send notifications from your own domain.
  • A portal on your own domain keeps its own favicon. See Connect a custom domain.
  • Publishing an experience is fast again for large organisations, and the Intercom launcher is gone from the partner portal.
  • Partner Connect opens a fresh link from Go to portal, never an expired one. See Partner Connect.