Derek runs global operations, with a background spanning CPaaS, VCaaS, telecommunications, APIs, and messaging. He is the operator behind the white-glove carrier approvals and the delivery infrastructure customers depend on.
What Derek works on
Derek runs the part of RCS that businesses find hardest to do alone: getting a brand verified and approved by carriers and by Google, and keeping messages landing once it has been. A2P messaging is not a single integration but a standing relationship with four US networks, each with its own registration requirements, filtering behaviour, and escalation path. He has worked that ground across CPaaS, VCaaS, APIs, and messaging, which is why SimplyRCS handles approvals for customers rather than handing them a checklist and wishing them luck.
Carrier approvals, handled for you
Brand registration, use-case declaration, and sender verification are done by the operations team on behalf of the customer. This is the step that most often stalls an RCS launch for weeks when a business attempts it unassisted, usually on a detail no one told them mattered.
RCS agent verification with Google
A verified agent is what puts a brand name, logo, and check mark in the thread. Getting there means satisfying Google on brand ownership and on how the agent will actually be used, then keeping the declaration true as the programme grows.
Deliverability across all three US national networks
Connectivity to AT&T, Verizon, and T-Mobile only helps if traffic is shaped to what each network expects. Watching delivery behaviour per carrier, and reacting when filtering changes, is continuous operational work rather than a launch task.
Coverage that does not sleep
The team behind Signalmash works across several countries specifically so network operations and support are staffed around the clock. Messaging failures do not wait for business hours in Oregon.
Areas of expertise
What Derek can speak to first-hand:
- Carrier approvals and verification
- A2P message deliverability
- CPaaS operations
Education: DeVry University
How we publish
SimplyRCS content is written and reviewed in-house by the people who run carrier approvals, deliverability and support. Collective pages carry the SimplyRCS byline; a personal name appears only on work that person did. See our editorial standards.
Related reading
- How to get RCS verified
- 10DLC, toll-free, and short codes explained
- Trust, verified senders, and consent