CRM Vendors Keep Outsourcing the Part of Sales Tech Nobody Wants to Own: the Carrier Relationship

Tells.co opened a developer integration hub this week aimed at a recurring problem for CRM and SaaS product teams: customers keep asking to text from inside the product, and the API call to send that first message is the easy part.

What happened: the hub, live at tells.co/developers, documents how CRM and vertical SaaS teams add SMS, MMS, RCS Business Messaging with automatic SMS fallback, AI SMS and voice agents, branded call announcements, and number intelligence through a single OAuth2 REST surface, with webhooks covering carrier acceptance, delivery, inbound replies, and opt-outs. Tells.co also published an evaluation page comparing itself to Twilio on access model, documentation, and registration ownership, citing each vendor’s own published material. Access is provisioned per account, with the endpoint reference, SDKs, and a sandbox environment handed over during onboarding. “Product teams do not want to become a telecom operation,” said David Schlaegel, co-founder of Tells.co. “They want one integration and someone else holding the carrier side.”

Why it matters: the part of texting-in-product that actually breaks roadmaps is not the API call, it is what comes after it, sender registration under the A2P 10DLC framework, consent and opt-out record keeping, and delivery event reconciliation with a carrier relationship no engineering team planned to own. Tells.co’s team prepares, submits, and tracks those registrations directly, which is the actual product here: not messaging capability, but the removal of a compliance queue from a CRM vendor’s backlog.

The original insight: this is the same build-versus-buy calculus now playing out across sales tech’s data layer, where vendors increasingly expose a governed connection point rather than make every downstream team rebuild the same plumbing, the same logic behind sales intelligence vendors opening direct data access for developers instead of gating it behind a dashboard. For a RevOps leader weighing build versus buy on texting, the real criteria are not features, they are who owns the carrier registration queue when it breaks.

Source: Tells.co