Jeremy leads business development, bringing years of telecom industry experience to helping businesses find the right path into RCS, from first conversation to first verified send.
What Jeremy works on
Jeremy handles the stretch between a business becoming curious about RCS and that business sending its first verified message. Most of that conversation is not a sales pitch; it is scoping. Which channel the use case actually needs, whether 10DLC, toll-free, or a short code is the right registration path, what consent the programme already has, and what the fallback to SMS has to cover. Years inside telecom usually make that call clear inside one conversation, including when the honest answer is not yet.
Scoping before selling
The first question is what the messaging programme is meant to achieve, not which plan to buy. Some businesses should start on SMS and add RCS once their volume and consent base justify it, and saying so early costs less than an abandoned launch later.
The free sender ID test
Rather than describe branded messaging, the team sets up a verified test sender so a prospect can see their own brand name and logo arrive on a real handset. It turns an abstract capability into something a stakeholder can hold.
Choosing the registration path
10DLC, toll-free, and short code differ in cost, throughput, approval time, and what carriers will tolerate. Picking the wrong one is expensive to undo, so the choice is made deliberately at the start with the operations team.
Handing off cleanly
A signed customer moves to onboarding, carrier approval, and a named support contact rather than a ticket queue. Jeremy stays attached through the first verified send, which is the point at which the programme is genuinely working.
Areas of expertise
What Jeremy can speak to first-hand, and reviews before we publish:
- Business messaging adoption
- Telecom business development
What Jeremy reviews
SimplyRCS content is written and reviewed in-house by the same people who run carrier approvals, deliverability, and support, because most of what we publish is operational knowledge rather than research. Jeremy is the reviewer for how businesses actually adopt the channel. Pages that are maintained collectively are published under SimplyRCS rather than a personal byline, and a personal name appears only on work that person actually did. Our editorial standards set out how topics are chosen, how statistics are sourced and labelled, and how corrections are handled.