October 2026 Summaries

Sent has launched an official Claude connector that enables authorized users to manage messaging through their Sent accounts, including sending and tracking SMS, WhatsApp, and RCS messages, accessing templates and contacts, checking compliance and sender-profile readiness, looking up phone numbers, viewing analytics, and reviewing account status. The connector provides 25 tools for Claude connections, while direct MCP clients such as Claude Code and Cursor can access a fuller 27-tool set, with all actions routed through Sent’s public API. Its channel-routing system can automatically choose among WhatsApp, SMS, and RCS based on factors such as deliverability, coverage, and cost, while reporting the final channel used. Built-in safeguards enforce opt-outs, registration, and consent requirements, restrict access to authorized organizations and sender profiles, and require confirmation before billed number lookups. Claude’s consumer-facing connections have additional limits, including one recipient per send, utility and authentication templates only, default organization-wide quotas of 10 sends per minute and 100 per day, and no sender-profile creation or deletion, while bulk campaigns and marketing templates must be handled through Sent’s Dashboard or API.

Sent’s Zapier integration enables users to connect SMS, WhatsApp, and RCS messaging with CRM, calendar, database, and other business tools without hosting webhooks or maintaining custom integration code. Sent can function as a Zap action for sending messages, as an instant trigger for inbound messages or delivery events, and through search or lookup steps for finding contacts, messages, activity, and account details. Common workflows include texting new leads, sending appointment reminders, recording replies in CRM systems, confirming task completion after delivery, posting inbound messages to Slack, logging them to spreadsheets, or creating support tickets based on keywords. Sent actions are also available to MCP-compatible AI agents and TypeScript services through Zapier, with Zapier managing authentication and permission scopes so API keys are not exposed. Users must still meet messaging compliance requirements, filter event triggers carefully because they fire for every status change, ensure they use the latest Sent Zapier app version, and monitor Zapier task limits as message volume increases.