← All experiences
PhonePatio

A phone number with a clear purpose.

Bring calls and carrier messages into the right workflow. PhonePatio is a proposed service for dedicated numbers, application access and accountable routing.

The Patio atlas

Inside PhonePatio.

Choose a topic or browse every data resource, capability and integration. Open an item to see what connects to it.

40items

Explore by topic

PhonePatio

Browse all items 40

1–18 of 40 items
Page 1 of 3

The catalog distinguishes upstream building blocks from proposed Patio connections. These are not live account bindings.

Inspect item

The workflow lab

See the records change.

Choose an incoming case and a recipient permission. Inspect the field mapping, the records kept and the exact handoff.

Fictional sample data

PhonePatio / Workflow

Decide whether a reminder may be sent

Normalize an authenticated reply, apply consent and local quiet hours, then expose a content-free operating result.

Recipient permissionOperating result in InfraPatio
Current resultOne recipient, one eligible reminder
1local records2source relationships
PhonePatio. Consent active, daytime. One recipient, one eligible reminder. Selected projection available. 4 Fields received.
01

Source records

What arrived, with its context

Authenticated inbound event
provider.sms-event
messageRef
provider:sm-81
signatureVerified
true
fromRef
contact:17
All fields & provenance5
body
OK
receivedAt
2026-10-28T10:15:00+01:00

A supplied host verifies the provider signature before accepting this event.

Reminder preference
communication.delivery-policy
purpose
appointment_reminders
consent
active_before_event
timeZone
Europe/Paris
All fields & provenance5
quietHours
21:00–08:00
recipientRef
contact:17

Consent, purpose and timing are independent eligibility checks.

02

Mapping & decisions

What changes, what stays separate

01Mapped
authenticated.bodyOK
consent.signalnone
Mapping rule

Recognized STOP becomes a consent signal; the message body is not copied into it.

02Mapped
local time + timeZone10:15 Europe/Paris
timing.eligibletrue
Mapping rule

Evaluate the chosen recipient’s quiet-hours window.

03Mapped
consent + timing + purposeappointment_reminders
intent.eligibilityeligible
Mapping rule

All required checks must pass before dispatch can be authorized.

One recipient, one eligible reminder
Why this decision?

The sample is eligible for a separately authorized send. Eligibility is not provider acceptance or delivery.

Operational evidence excludes the message
Why this decision?

InfraPatio can receive the channel and eligibility result through the selected projection, without the phone number or body.

03

Resulting records

What this product keeps

Reminder intent
communication.sms-intent
eligibility
eligible
intentRef
sms:reminder-18
recipientRef
contact:17
All fields & provenance6
consentScope
appointment_reminders
contentRevision
draft:v3
providerSend
false

This is eligibility evidence for a sample intent, not a sent SMS.

Typed handoff

PhonePatioInfraPatio

communication.eligibility-event.v1
Selected projection available
Fields received
intentAlias
reminder-18
channel
sms
result
eligible
occurredAt
2026-10-28T09:15:00Z
Remain outside this handoff
phoneNumbermessageBodyrecipientIdentity

Only these selected fields cross into the receiving product.

Sample grantdemo-grant:phonepatio:infrapatio:communication.eligibility-event.v1
Inspect the rules and source foundations4

One recipient and appointment-reminder purpose; no provider call is made.

ContractSpec supplies the cited building blocks. This end-to-end recipe is a proposed Patio composition; its fixture decisions do not run those services.

A local simulation. No account is connected and no message, publication or deployment is sent.