What problem does it solve?
This Skill helps you design and sanity-check phone-call products without assuming the app itself can control carrier-level routing. It is useful when you need to understand what is possible across carrier forwarding, CPaaS numbers, caller ID, and mobile OS constraints.
Core Features & Use Cases
- Carrier and routing analysis: Distinguishes SIM-level, forwarded, ported, and CPaaS-controlled numbers so you can choose the right call flow.
- Platform constraint checking: Clarifies what iOS and Android can and cannot do for caller ID, blocking, and native call handling.
- Product architecture guidance: Helps plan spam screening, voicemail replacement, AI receptionist flows, and shield-number setups with realistic tradeoffs.
- Use Case: A team building an AI answering service can use this Skill to decide whether to rely on conditional call forwarding, port a number to a provider, or use a secondary eSIM for faster launch.
Quick Start
Ask for a telephony architecture recommendation for your call product, including carrier routing limits, iOS and Android constraints, the main blocker, a ship-fast option, and a long-term option.