Changelog

Usage Analytics, New Guides & Blog Launch

Track your real message spend in the dashboard, explore rewritten guides, and check out 20+ new blog posts on pinnacle.sh/blog.

What’s new?

Live usage analytics

The analytics dashboard now shows your real-time messaging volume and spend.

• RCS, SMS, and MMS usage charts with a default 30-day window
• Combined credit balance showing purchased and subscription credits side-by-side
• Improved validation feedback when creating test agents — errors now tell you exactly which fields need attention

Updated documentation

• Sending messages — expanded with coverage on broadcasting to audiences, typing indicators, and message reactions
• Receiving messages — expanded with a step-by-step webhook setup walkthrough and structured event-type reference
• Test agents — updated to reflect that test agents support the full RCS feature set (rich cards, carousels, buttons, media), limited only to your whitelisted numbers
• Ruby quickstarts — updated to use the SDK’s process() method for webhook verification and idiomatic snake_case, now on SDK v2.0.15

Better RCS error messages

When whitelisting testers, you’ll now get clear error messages if the carrier requires your agent to be launched first — instead of a generic rejection.

Blog launch

We published 20+ posts on pinnacle.sh/blog covering everything from getting started to platform deep-dives:

• RCS Test Agents: Send Your First Rich Message in Under Two Minutes
• RCS Fallback: Automatic SMS/MMS Delivery for Every Recipient
• Bulk Messaging: Send to Thousands of Contacts at Once
• Validate Before You Send: Message Validation for SMS, MMS, and RCS
• Pinnacle vs. Twilio | vs. Attentive | vs. AWS

Bulk Webhook Management

Webhook management just got simpler — attach and detach webhooks to multiple senders in a single API call.

What’s new?

Bulk webhook attach/detach

• Attach webhooks to multiple senders at once via POST /webhooks/attach — pass an array of phone numbers and/or RCS agent IDs
• Detach webhooks from multiple senders via POST /webhooks/detach — remove webhook routing in bulk
• Simplified senders field replaces the previous per-number configuration
• Detach now works regardless of webhook status

No more looping through numbers one at a time — configure all your webhook routing in a single request.

View API reference →

Simplified RCS Campaigns

RCS campaign submissions just got easier — we’ve streamlined the required fields so you can get approved faster with less friction.

What’s new?

Simplified RCS campaign submissions

We’ve removed deprecated and redundant fields from the RCS campaign schema. Submitting a campaign now requires fewer fields while still meeting carrier compliance requirements.

• Removed legacy profile fields that are no longer needed
• Added cta_media for attaching compliance media (e.g., opt-in screenshots)
• Added opt_in_method to clearly describe how users consent to receive messages
• Updated use_case_description for clearer campaign intent

These changes reduce the back-and-forth during carrier review and help you get your RCS agents approved faster. See our RCS campaign compliance guide for details.

Conversations, Reactions & More

New conversation threading, message reactions, validation endpoints, URL shortening, and an expanded MCP server.

What’s new?

Conversations API

Messages between a sender and recipient are now grouped into conversation threads — the backbone of inbox-style experiences.

• List conversations filtered by brand, campaign, sender, or receiver
• Get a conversation by ID or phone number pair
• List messages within a conversation with pagination
• Update conversation notes for internal tracking

View API reference →

Message reactions

React to messages with emoji using POST /messages/react. Messages support multiple reactions.

Message validation

Validate SMS, MMS, and RCS messages before sending — check segment count, encoding, unsupported files, and estimated cost without consuming credits.

• POST /messages/validate/sms | POST /messages/validate/mms | POST /messages/validate/rcs

URL shortener

Create tracked short links (pncl.to) with click analytics, configurable expiration, and updatable destinations.

• POST /tools/url | GET /tools/url/{linkId}

MCP Server — 89 tools

The Pinnacle MCP server now exposes 89 tools (up from 71 at launch), covering conversations, webhooks, test agents, and more.

Feedback, Support & SOC 2

New in-app feedback tools and SOC 2 compliance infrastructure to keep your data secure and your voice heard.

What’s new?

Feedback & support

A new feedback button is now available directly in the dashboard — ask questions about our docs, submit feature requests, report bugs, or reach out to support without leaving your workflow. Help documentation is also accessible from the dashboard header.

SOC 2 compliance

We’ve implemented automated audit log exports and database backup infrastructure to meet SOC 2 requirements. Your messaging data is backed by enterprise-grade security and compliance controls.

RCS Test Agents & Carrier Status

Go from zero to your first RCS message in under 2 minutes — no campaign approval required. Create a test agent, whitelist your number, and start sending rich messages right away.

What’s new?

RCS test agent management API

Every Pro account gets up to 5 test agents to experiment with RCS before going through the full campaign approval process. With the new test agent API, you can:

• Create a test agent via POST /rcs/test/agents — set up branding, contact info, and colors in a single call
• Whitelist your number via POST /rcs/test/agents/{agentId}/whitelist — register your device to receive test messages
• Send your first RCS message — once whitelisted, you can immediately send rich messages with cards, buttons, and media through your test agent

You can also update agents and check whitelist status programmatically, making it easy to integrate into your development workflow.

RCS carrier launch status

You can now see the launch status of your RCS agents across each carrier directly in the dashboard and API. Each agent shows per-carrier status — NOT_LAUNCHED, PENDING, or LAUNCHED — so you know exactly where your agent stands before going live.

Inbox Embed

The embedded components library now includes an Inbox, allowing you to add a full-featured messaging inbox directly into your website.

What’s new?

Inbox embed

Give your users a complete RCS and SMS messaging experience — conversations, message history, rich media, and real-time updates — all in a single iframe.

• Token-based authentication with scoped permissions
• Filter conversations by brand, sender, or simply show everything for a team
• Customizable colors with primaryColor
• Real-time message and conversation updates

Send RCS Message updates

Send RCS Message embed has been updated to use the new v2 token-based flow — message configuration is now securely encoded in the signed token on your backend.

MCP Server

Introducing the Pinnacle MCP Server — connect AI assistants like Claude, Cursor, and Windsurf directly to the Pinnacle API using the Model Context Protocol.

What’s new?

MCP Server with 71 tools

Send SMS, MMS, and RCS messages, manage contacts, audiences, brands, and campaigns, purchase phone numbers, configure webhooks, and more — all through natural language in your AI client. No code required.

• Remote: Connect instantly at https://mcp.pinnacle.sh/mcp with your existing API key
• Local: Run via npx @pinnacle-rcs/mcp for development and testing
• npm: Available as @pinnacle-rcs/mcp

Supported clients: Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible AI tool.

Get started →

RCS Fallback Messages

Never lose a message again — RCS messages now automatically fall back to SMS or MMS when a recipient’s device doesn’t support RCS.

What’s new?

RCS fallback messages

Include a fallback object in your RCS send request with a from phone number and text or mediaUrls. If RCS delivery fails, the message is resent as SMS or MMS automatically.

• SMS fallback when only text is provided (≤3072 characters)
• MMS fallback when mediaUrls are included or text exceeds 3072 characters
• Original RCS message status updates to FALLBACK_SENT
• Webhook delivers fallbackMessage details so you can track both legs

Learn more →

Send RCS Message Embed

Say hello to embedded components! This is the beginning of our embedded components library, starting with our send rcs demo, which allows you to add a component like this: where you can demo RCS to your customers.

What’s new?

Embedded UI components

Instead of building RCS demos yourself from scratch, you can drag, drop, and customize ours in one simple iframe with your company’s product’s information and brnading. Want to check out what the component looks like? Try it out!