SMS Integration

What it does

Send stakeholder updates by text message via Twilio.

How your data reaches Specky

It doesn't — SMS is outbound only. There's nothing to ingest and no sync; it exists so Specky can deliver stakeholder updates through it.

What you'll need

Auth Token (Required) — From your Twilio Console — Account → API keys & tokens.

Account SID (Required) — Starts with AC, found on the Twilio Console dashboard.

From Number (Required) — A phone number or Messaging Service SID you own in Twilio, in E.164 format.

Setup

Go to Settings → Integrations, find SMS, and click Connect.

How to connect

Sign up at twilio.com and buy or verify a phone number capable of sending SMS

Copy your Account SID and Auth Token from the Twilio Console dashboard

In-app, connect via Settings → Integrations → SMS with the Account SID, Auth Token, and your Twilio phone number

What this is for

SMS is send-only — there's no inbound community feed the way Slack or Discord has one. It exists as a delivery channel for the Stakeholder Map's "Notify" action, for stakeholders who prefer a text over email or a chat app.

Data synced

None — this integration only sends, it never reads or ingests anything.

After connecting

SMS appears as a delivery channel wherever Specky sends stakeholder updates. It won't add anything to your product graph, because it has nothing to read.

Troubleshooting

Connected, but nothing appears. That's expected — SMS sends, it doesn't ingest.

"Upgrade to connect". Your plan caps how many integrations you can connect at once, and a few providers are Scale-only. Settings → Usage shows where you stand.

Credentials stopped working. Tokens expire and get revoked. Reconnect with a fresh one — your existing signals are kept.

See the SMS integration page for what it's for and the questions people usually ask first, or the Integrations Overview for how integrations work in general.