A proposed channel product for dedicated numbers, inbound and outbound voice, SMS, MMS and RCS. PhonePatio and TelPatio remain alternative names for this one telephony scope; carrier support and service implementation are to establish.
PhonePatio / TelPatio. Two name sets for the telephony scope. Email remains MailPatio’s focus; this concept covers numbers, voice and phone messaging.
A WAY INTO THE PRODUCT
A phone channel alongside email.
A proposed phone boundary for voice calls, SMS, MMS and RCS, with scoped routing, consent and delivery evidence.
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.
01
Numbers, calls & SMS
Choose the workflow that needs a phone identity, then define its routing and allowed actions.
THE PRODUCT WORKFLOW
Planned product scope.
These are the requested capabilities of a product direction. Implementation and provider bindings remain to establish.
Dedicated workflow phone numbers
Proposed
Planned scope · implementation to establish.
Inbound and outbound calls
Proposed
Planned scope · implementation to establish.
SMS conversations and delivery events
Proposed
Planned scope · implementation to establish.
Routing, context and application permissions
Proposed
Planned scope · implementation to establish.
MMS and RCS where qualified providers support them
Proposed
Planned scope · implementation to establish.
LSSM ACCOUNT / ACROSS PATIO
Your account. Your context in PhonePatio / TelPatio.
Patio’s infrastructure and data holding includes focused brands with a shared account direction. Choose the personal or work context that belongs in this experience.
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 (12)
Shared foundations
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Products & experiences
Shared foundations
Shared foundations
Shared foundations
HOW IT CONNECTS
Its own purpose. Useful neighbours.
This entry has a distinct purpose within the ecosystem. Its related products and capabilities offer other ways to approach the work.
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.
This is an owner-requested product concept with a scope diagram. It is not an inspected application interface or a live service.
CONNECTED WAYS IN
Explore the connections around PhonePatio.
Find the relevant group, follow a capability, or compare another experience for the same role.
Composes contracts, intelligence, infrastructure and data. Runs and operates the environments that bring them into use.
RUNTIME & OPERATIONS
Target ecosystem architecture. ContractSpec specializes into domain and platform contracts. The foundation roles come together through LSSM OS; each technical relationship carries its own evidence.
Patio: the specialized infrastructure and data holding within LSSM, with focused product brands. Implementation and availability are recorded per service.Inspect the scope ↗ · Explore the products ↗