Smartsheet vs Zapier

Smartsheet investors sue over undisclosed acquisition offer

Rosen Law Firm has filed a securities fraud class action lawsuit against Smartsheet Inc. on behalf of investors who sold shares between June 2024 and September 2024. The suit alleges that Smartsheet failed to disclose an unsolicited acquisition offer from a consortium of investors, while the company was repurchasing its own stock at lower prices. The action seeks to recover damages for investors who sold shares during this period. The deadline for lead plaintiff applications is October 5, 2026.

• Rosen Law Firm filed a securities fraud class action against Smartsheet Inc.
• The class period is June 1, 2024 to September 23, 2024.
• Smartsheet received an unsolicited takeover offer at $56.25 per share on January 24, 2024.

Smartsheet Appoints Takeshi Osawa as President & General Manager of Japan Amid Accelerating Customer Demand and AI Adoption

Smartsheet appoints Takeshi Osawa as President & General Manager of Japan, and names new leaders across APAC and Japan as demand surges in technology, manufacturing and professional services.

Zapier Automates Marketing Funnels with ChatGPT Work

Zapier's enterprise marketing team uses ChatGPT Work to automate funnel QA/QC, campaign asset creation, and reporting. The system performs quality assurance on thousands of leads monthly, surfaces recurring pipeline issues via an executive dashboard, and generates campaign assets quickly, allowing the team to focus on creative and strategic work. Zapier reports the automation yields seven-figure pipeline impact handed off to sales each month. The team plans to move toward always-on automation loops and a shared contextual “brain” integrating meetings, call recordings, and market insights.

• Zapier's enterprise marketing team uses ChatGPT Work to build automated funnel optimization systems.
• The system performs automatic QA/QC on thousands of leads every month.
• Zapier quantified the project's impact as seven figures in pipeline delivered to sales monthly.

Update Claude Code for Claude 5 Models

This newsletter explains how to adapt Claude Code workflows for Anthropic’s new 5-series models (Sonnet, Opus, Fable). The author highlights that the Claude team removed roughly 80% of the Claude Code system prompt for Opus 5 and found the model performed better, and recommends starting from Claude Code’s safe mode to identify obsolete customizations. The post links to an /update-to-cc-5 skill that automates the three recommended transformations, and lists related AI industry updates (Google Gemini leadership changes, Meta and Nvidia model releases, feature updates across tools, and recent fundraising). It also calls out several tooling updates (Zapier SDK, Wispr Flow, Superblocks, Arcads, Helena) and notes Sapiom’s $35M raise.

• Anthropic’s Claude Code team deleted ~80% of the Claude Code system prompt for Opus 5 and observed improved performance.
• Claude Code provides a safe mode to baseline behavior and compare outputs with customizations.
• The author published a downloadable skill that runs /update-to-cc-5 to automate recommended changes for Claude 5 compatibility.

Twilio to remove conference_participant on Aug 1, 2026

Twilio will remove the conference_participant field from Voice Insights Call Summary on August 1, 2026. The field will remain in responses but its attributes will uniformly return null (HTTP 200 unchanged) across both the REST API and Event Streams. Twilio points customers to the separate Conference Insights APIs (conference- and participant-keyed resources) as the replacement, meaning migrations require capturing or mapping ConferenceSid/ParticipantSid and reshaping call-centric storage to conference-centric storage. Because the change preserves response shape and status codes, analytics and pipeline consumers that relied on conference_participant may silently see conference metrics decay to zero rather than generate errors.

• Twilio will remove the conference_participant field from Voice Insights Call Summary on August 1, 2026, affecting both the REST API and Event Streams.
• After removal the field remains present in responses but conference_participant.attributes will return null for all calls while responses continue to be HTTP 200.
• Twilio's recommended replacement is the separate Conference Insights APIs, which are keyed by ConferenceSid and ParticipantSid (conference-centric addressing).