Article content
In briefShow moreShow lessHubSpot described segmentation, sales documents, ticket assignment and workflow actions.
- HubSpot described segmentation, sales documents, ticket assignment and workflow actions.
- Power Platform previewed Copilot chat inside model-driven apps.
- Salesforce Spring ’26 brought new field features into its monthly release.
- Automation should be tested against representative exceptions before production.
The customer process gains more connection points
HubSpot’s 19 February industry summary described early February changes for several customer teams. Marketing included a private beta TikTok Ads integration and more precise segmentation. Sales gained multi-brand support in sales documents and visibility into scheduled sequence sends. Service teams gained explanations for ticket assignment. Status varied, so the collection cannot be described as generally available.
The roundup also described a private beta workflow action that added line items to deals. This is concrete automation between a product library and the sales process. Before adoption, organizations should test currency, price book, duplicates and discontinued products. An assignment explanation should be compared with the actual queue rule; generated text supports troubleshooting but does not become the authoritative routing rule.
Copilot enters the business application
Microsoft’s 17 February Power Platform update made Microsoft 365 Copilot chat available in model-driven Power Apps as public preview. An administrator configured the capability and a maker enabled it per app. This may give sellers and service staff context close to the record they use. A preview should remain limited to selected roles, defined data types and tasks that support human review.
Tests need to distinguish reading, proposing and writing data. Log the grounding material, approver and overwritten fields. Measure completion time, corrections and rejected suggestions. If chat merely moves search work without improving quality or throughput, that is useful evidence before licensing and support expand.
Test the field release across the work order
Salesforce said the broad Spring ’26 rollout would start on 23 February. Field capabilities included voice-to-form, mapping, data capture, work order views and scheduling, with different availability statuses in the release notes. A field manager needs to verify status in the organization and test offline use, location data, required fields and synchronization before adding features to standard procedures.
Use one work order from customer request through appointment, visit, documentation and billing input. Record where marketing or sales data affects priority, how customer service receives updates and which automated steps can be stopped. February’s changes create more system handovers. Management receives value only when owners can explain data, decision rule, exceptions and recovery at every transition.
Include licensing, configuration and training cost in the same evaluation. A faster handover is not a benefit when more cases reopen or field records need later correction.
Sources
HubSpot Community, “The February 2026 Industry Edit: Essential HubSpot Updates,” 19 February 2026
Microsoft Power Platform Blog, “What’s new in Power Platform: February 2026 feature update,” 17 February 2026
Salesforce, “Spring ’26 Release: 10 Tools to Help Build an Agentic Enterprise,” 9 January 2026
Salesforce Help, “Salesforce Spring ’26 Release Notes,” February 2026
Join the discussion
How do you check that a customer journey gives recipients relevant follow-up? Share a practical example in the discussion.









