Flow Copilot
Copilot can now tell a sales leader why the forecast moved, and the first answers are landing
Beta 1.3 reached all 16 beta accounts Thursday morning. By the end of the day, Meridian’s revenue operations lead had used it to rebuild a forecast bridge he used to make by hand.
At 9:15 a.m. Thursday, Sofia Alvarez’s team switched on “Why did my forecast change?” for every account in the Flow Copilot beta. Ask Copilot why the commit number moved since last week and it now answers with the deals that moved, the amount each one added or removed, and a link back to the CRM record behind every line.
It was the most-requested capability in last month’s beta feedback, and it arrived fast enough that the first real use came the same afternoon. On a 2 p.m. check-in with Elena Rossi, Elliot Shaw, VP Revenue Operations at Meridian Payments, asked Copilot to explain a $410,000 drop in his team’s Q4 commit. The answer named three deals pushed to January and one that had been split into two smaller opportunities.
Shaw had his answer before the call ended. He said he usually spends Monday mornings rebuilding that bridge in a spreadsheet before his forecast call.
That’s my Monday morning. I build that bridge by hand every week, and it just did it with the links.
Usage was already climbing before the release. Beta accounts asked Copilot 1,412 questions in the four days through Thursday, more than in any full week since the beta opened in August (see Chart of the Day). Sofia’s team will watch whether forecast-change questions become a weekly habit or a one-time novelty; the next read on that comes after Monday’s forecast calls.
What’s next: 1.3 stays limited to the 16 beta accounts through October. General availability depends on two things Grace Kim has set as gates: citation accuracy above 98% on the evaluation set, and admin controls for which pipeline fields Copilot can see.
Sources: Release copilot-beta-1.3Gong call · Meridian check-inSlack #product-launches