Twilio setup FAQ for InsertLead — auth tokens, webhooks, A2P

Where do I find my Account SID and Auth Token?

Log in to console.twilio.com. The Account SID and Auth Token are displayed at the top of the home dashboard.

• Account SID starts with AC followed by a long hex string. Safe to share; it identifies your account but doesn't grant access on its own.
• Auth Token is the secret. Treat it like a password. Never post it publicly. We store it Fernet-encrypted in our database.

In InsertLead Settings, paste both into the Twilio configuration form. We never log them; they're decrypted only at request time when we make a Twilio API call on your behalf.

Which webhook URLs do I configure?

After saving your Twilio credentials in InsertLead Settings, we display the exact webhook URLs to copy. They look like:

• Inbound SMS: https://insertlead.com/webhooks/twilio/sms
• Status Callback: same URL (we route both through one endpoint)
• Inbound Voice (optional): https://insertlead.com/webhooks/twilio/voice

In your Twilio Console, navigate to Phone Numbers → Manage → Active Numbers, click your sending number, and paste the URLs into the Messaging webhook fields. Set HTTP method to POST. Save. That's it.

Do I need A2P 10DLC registration?

Yes, for any commercial SMS to US recipients from a US local number. Carriers (T-Mobile, AT&T, Verizon) block unregistered traffic by default with the message "30007 carrier filter."

Registration is filed inside Twilio Console under Messaging → Regulatory Compliance → A2P 10DLC. Costs ~$71 upfront, ~$10/month maintenance. Full A2P cost breakdown. If you'd rather we file it for you, Full Setup onboarding covers it.

Can I use an existing Twilio account?

Yes. InsertLead's webhook configuration is per-phone-number, so it doesn't affect any other apps using different numbers in the same Twilio account.

We recommend using a dedicated phone number for InsertLead-driven outreach. Why: the carrier reputation score is tracked per-number, so mixing your wholesaling traffic with (say) a notification system or a personal SMS app would dilute the reputation signal. Buy a fresh number, register it under your existing A2P Campaign, and use it only for InsertLead.

Common setup problems

"Twilio webhook returns 400 Bad Request"

Most common cause: the webhook URL has a trailing slash that shouldn't be there, or you pasted an http:// instead of https://. Both URLs above must be exactly as shown.

"My first send returns 'Error 21610'"

Twilio code 21610 means "you're sending to a number on Twilio's STOP list." Twilio auto-handles STOP keywords platform-wide, so a recipient who once texted STOP to ANY Twilio sender is on the list. Use a different test number for your smoke send.

"30007 spam filter on every message"

This is the most common A2P 10DLC issue. It means either: (a) your A2P Campaign isn't approved yet (check Twilio Console), or (b) your Campaign is approved but the carriers are scoring your sample messages as spam-like. Re-submit Campaign registration with cleaner sample messages. DNC + STOP defenses page has more on this.

"My number isn't appearing in InsertLead's dropdown"

After buying a number in Twilio Console, you have to add it to your InsertLead Settings as the "sending phone number." We don't auto-discover Twilio numbers (intentional — you might have multiple numbers for different uses).