Dedicated phone identity and bounded voice, SMS, MMS and RCS workflows. Provider/carrier support and the PhonePatio / TelPatio product remain to establish.
Founder-requested product concept. PhonePatio is a provisional working name; TelPatio is a naming alternative. No dedicated repository, implemented phone service, live provider binding, owned domain or production deployment has been established for this product. Voice, SMS, MMS and RCS remain intended channel scope subject to provider/carrier support and qualification.
Arrow keys navigate entries. Enter selects. Alt + arrows rearranges. F fits the view; Shift + F fits the selection. + and − zoom. Shift + F10 opens actions.
Drag to pan · Ctrl/⌘ + scroll to zoom
Accessible entry list (6)
Shared foundations
Capabilities
Products & experiences
Shared foundations
Shared foundations
Shared foundations
EXPERIENCES & COVERAGE
Where this work belongs.
The note beside each product identifies the scope of this connection.
Direction to develop
Founder-requested product concept. PhonePatio is a provisional working name; TelPatio is a naming alternative. No dedicated repository, implemented phone service, live provider binding, owned domain or production deployment has been established for this product. Voice, SMS, MMS and RCS remain intended channel scope subject to provider/carrier support and qualification.
PRODUCT DIRECTIONConcept schematic
PhonePatioNumbers. Calls. Messages.
A phone channel for products, teams and agents.
↗
THE PLANNED ENTRY POINTA managed phone identity
↗CallsVoice & routing
≡MessagesSMS, MMS & future RCS
⌘EventsApplication & agent handoffs
Concept schematic · service implementation and provider setup to establish.
Infrastructure product / PatioProduct concept · phone service not established