Question 1

What is Pinnacle?

Accepted Answer

Pinnacle is the messaging API for developers. One API lets you send and receive RCS, iMessage, MMS, and SMS — with automated compliance, a unified dashboard, SDKs in Python, TypeScript, and Ruby, and an MCP server so your AI agents can message users directly.

Question 2

What messaging channels does Pinnacle support?

Accepted Answer

Pinnacle supports RCS (rich interactive messages on Android and iPhone), iMessage (native rich messaging to Apple devices), MMS (pictures and media over cellular), and SMS (plain text everywhere). You can pick the channel per message, or let Pinnacle pick the best-available channel with automatic fallback.

Question 3

How do I get started?

Accepted Answer

Sign up at app.pinnacle.sh, install the SDK for your language (Python, TypeScript, or Ruby), grab an API key from the dashboard, and send your first message. You can test immediately in our sandbox without waiting for production approval.

Question 4

What is RCS?

Accepted Answer

RCS (Rich Communication Services) is the next generation of SMS messaging. It enables businesses to send rich, interactive messages with features like high-resolution images, carousels, quick replies, and read receipts directly through the default messaging app on Android and iOS devices.

Question 5

What's the difference between RCS and SMS?

Accepted Answer

RCS offers enhanced features over traditional SMS including high-resolution images and videos, interactive buttons and carousels, read receipts and typing indicators, and branded sender information. SMS is limited to 160 characters of plain text, while RCS supports rich media and interactive elements.

Question 6

What's the difference between RCS and iMessage?

Accepted Answer

Both are rich messaging standards, but they reach different users. iMessage is Apple's proprietary protocol, available only to Apple devices. RCS is an open standard supported on Android and iPhone. Pinnacle lets you target either or both from a single API.

Question 7

What happens if a user can't receive RCS or iMessage?

Accepted Answer

Pinnacle automatically falls back down the chain: RCS → iMessage → MMS → SMS. Before sending, we look up the recipient's capabilities so each message ships on the richest channel their device supports.

Question 8

How do I get iMessage?

Accepted Answer

iMessage is onboarded per-account at Pinnacle. Send a note to founders@pinnacle.sh with your sending number and use case, and we'll get you enrolled. Once enabled, iMessage rides on the same send_mms endpoint — no separate integration.

Question 9

How long does it take to go live?

Accepted Answer

Under a minute to your first sandbox message. To live carrier-registered traffic: 10DLC (SMS/MMS) in 1–2 days, toll-free SMS/MMS in 1–2 days, RCS in 1–2 weeks. Pinnacle automates the compliance paperwork — brand vetting, campaign registration, RBM submission — so you don't wait in a queue you can't see.

Question 10

Do I need to handle compliance myself?

Accepted Answer

No. Pinnacle handles 10DLC brand and campaign vetting for SMS and MMS, toll-free verification, RCS agent registration and RBM approval, and iMessage account onboarding. You fill out a short form once, we take it from there.

Question 11

Can I test before going live?

Accepted Answer

Yes. Pinnacle gives you a sandbox you can message against immediately — no carrier approvals needed. The sandbox covers every protocol: real RCS rich cards to whitelisted test numbers, iMessage/MMS/SMS rendering, and full webhook surface for inbound messages and delivery events.

Question 12

Which countries does Pinnacle support?

Accepted Answer

SMS, MMS, and RCS ship today on every US carrier (AT&T, T-Mobile, Verizon, and every major MVNO). iMessage is global by nature but onboarded per-account. International SMS/MMS coverage and additional country support is on the near-term roadmap.

Question 13

What is 10DLC and do I need it?

Accepted Answer

10DLC (10-Digit Long Code) is the framework US carriers require for any business sending SMS or MMS from a standard 10-digit number. It involves Brand registration (who you are) and Campaign registration (what you're sending). Pinnacle handles both as part of onboarding.

Question 14

What are the message size limits and segmentation rules?

Accepted Answer

SMS supports GSM-7 encoding (160 characters per segment) or UTF-16 encoding (70 characters per segment). MMS has a 4.5 MB maximum per message and supports up to 10 files. RCS Text uses UTF-8 encoding with 160 byte segments. RCS Media supports up to 100 MB per message.

Question 15

Do you offer API documentation?

Accepted Answer

Yes. Full API reference at docs.pinnacle.sh, with worked examples for sending SMS, MMS, RCS, and iMessage in Python, TypeScript, and Ruby. Every endpoint has a copy-paste request body, response schema, error codes, and a live Try-it console.

Question 16

What SDKs are available?

Accepted Answer

We ship and maintain official SDKs for Python, TypeScript (Node), and Ruby. Each SDK is generated from the same OpenAPI spec, so feature parity is guaranteed. If you're on another language, the REST API is documented end-to-end.

Question 17

Do you have an MCP server?

Accepted Answer

Yes. Pinnacle ships a Model Context Protocol server that lets AI agents (Claude, Cursor, Codex, and anything else that speaks MCP) send messages, check deliverability, and read conversations directly through tool calls.

Question 18

How do I receive inbound messages and delivery events?

Accepted Answer

Pinnacle pushes every inbound message, delivery receipt, read receipt, and button tap to webhooks you configure in the dashboard. Webhooks are signed, retried with exponential backoff, and mirrored to dashboard logs.

Question 19

What analytics and logging do you provide?

Accepted Answer

Every message is logged with its full payload, channel, delivery status, timestamps, and user interactions. The dashboard includes built-in analytics for send volume, delivery rate, cost, and engagement broken down by channel.

Question 20

Can I send bulk messages or campaigns?

Accepted Answer

Yes. Pinnacle supports bulk sends via a single API call with per-recipient personalization, throttling controls, and scheduled delivery. Campaigns are visible in the dashboard with real-time progress and per-recipient delivery status.

Question 21

How does pricing work?

Accepted Answer

Pinnacle pricing is transparent and published at pinnacle.sh/plans. You pay a flat monthly base plus per-message fees that match carrier pass-through pricing for each channel. No sales calls, no custom quotes, no hidden carrier fees.

Question 22

Is my data secure?

Accepted Answer

Pinnacle encrypts data in transit (TLS 1.2+) and at rest, stores only what's needed to deliver and audit messages, and issues scoped API keys per environment. See our trust center at trust.pinnacle.sh for the full security posture.

Question 23

Is Pinnacle SOC 2 compliant?

Accepted Answer

Pinnacle's SOC 2 Type II audit is in progress and expected to complete soon. If SOC 2 is a hard requirement, get in touch — we can share current controls, audit status, and timeline.

Question 24

Can I talk to someone before I sign up?

Accepted Answer

Yes. The sandbox is free and the docs are public, but if you want to talk through a use case, custom volume, or an enterprise agreement, reach out at pinnacle.sh/contact. We usually respond same day.

Frequently Asked Questions