Phone number input
International phone entry, parsing, country selection, E.164 storage, extension and formatted display.
Shared componentFuture Spec 16 →Current-state summary
Phone number input appears across the current product but is not yet governed as one fully documented reusable component. Phone fields exist in Client, Application and Workspace forms, but there is no documented country selector, parsing rule, extension field, E.164 storage or consent relationship.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Canonical interaction | Default country from Workspace or address context but let the user change it. Parse and validate using international numbering metadata; store E.164 when valid. Keep extension separate, format for display by locale and never infer SMS capability or consent from presence of a number. | Required reusable contract |
| Data contract | Store raw input, parsed E.164 number, country calling code, national number, optional extension, label/type, verification state and independent channel-consent records. | Required shared storage and API behavior |
| Accessibility | Use tel input mode, text labels for country codes, keyboard-operable country search and errors that explain format without erasing input. | Required before component is approved for reuse |
| Reuse inventory | Client contacts, Teammates, Designer and Provider profiles, Applications, Workspace Profile, Twilio calling and SMS, delivery contacts | Known current and future consumers |
| Current inconsistencies | Numbers may currently be stored as unstructured text. Country context and extensions are not consistently captured. Consent, type and verification are not linked to the field. | Observed or identified correction work |
User journeys
Current flows
Use Phone number input
- Render from the shared component registry
- Load canonical value and configuration
- Accept keyboard, pointer or assistive-technology input
- Validate and normalize
- Persist canonical value with provenance
- Render the same meaning in profiles, grids, filters, exports and integrations
State model
Current and expected states
Value can be entered or selected with a visible label.
Must provide a visible focus indicator without layout shift.
Must distinguish unavailable input from view-only canonical value.
Requirement is communicated in label, schema and validation—not colour alone.
Inline message explains the problem and preserves the user’s input where safe.
Async work prevents duplicate commands and remains announced.
Null, empty string, zero and empty collection retain distinct meanings.
Product rules
Non-negotiable boundaries
- Build once and reuse the same component, schema and formatter in every Workspace experience.
- Display formatting is separate from canonical storage.
- Every value has a stable field key, type, validation, privacy classification and version.
- Client validation improves usability; server validation remains authoritative.
- Equivalent values render consistently in forms, grids, profiles, filters, exports, notifications and documents.
- Default country from Workspace or address context but let the user change it.
- Parse and validate using international numbering metadata; store E.164 when valid.
- Keep extension separate, format for display by locale and never infer SMS capability or consent from presence of a number.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- Numbers may currently be stored as unstructured text.
- Country context and extensions are not consistently captured.
- Consent, type and verification are not linked to the field.
Future alignment
Required evolution
- 01Promote this pattern into the approved component library.
- 02Replace local copies incrementally and retain migration adapters only where required.
- 03Add automated interaction, validation, accessibility and serialization tests.
- 04Track reuse across: Client contacts, Teammates, Designer and Provider profiles, Applications, Workspace Profile, Twilio calling and SMS, delivery contacts.
Current baseline
Acceptance record
- The component has one public API and canonical data contract.
- All required states are documented and tested.
- Formatting and validation are consistent across every consumer.
- Keyboard and screen-reader testing passes.
- Existing inconsistent copies have an owner and migration plan.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented