Filament Tel Input Laravel Package

Product Decisions This Supports

• Feature delivery for international phone capture: Adding or improving phone number fields in Filament admin panels (customer records, leads, onboarding forms) with country selection, formatting, and validation — without spending sprint capacity building a custom Alpine.js + intl-tel-input/libphonenumber integration.
• Build vs. buy for a narrow UI concern: This is a tactical "buy" (MIT, free) for a commodity form input. It should not be treated as strategic infrastructure; the decision is whether a small plugin saves enough engineering time versus a thin in-house wrapper around libphonenumber.
• Data quality roadmap: Standardizing phone numbers to E.164 at capture time improves downstream integrations — SMS/OTP providers (Twilio, Vonage), CRM sync, deduplication, and support tooling. That is a PM-visible outcome (fewer failed SMS, cleaner records), not just a UI nicety.
• Use cases that justify it: B2B SaaS with customers across multiple countries, internal sales/ops tooling, lead capture forms, and any Filament-based back office where phone numbers are a first-class field.
• Adoption risk as an explicit product decision: With ~3 stars, 0 dependents, and a single maintainer, this is a low-signal package. The PM decision is less "is this good?" and more "can we absorb the maintenance risk for a non-differentiating field?"
• Opportunity assessment: The opportunity score (~0.38) and low adoption suggest limited ecosystem momentum. Favor it only where the cost of replacement is low and the field is not on a critical path.

When to Consider This Package

Consider it when all of the following hold:

• You are building on FilamentPHP and need a phone input inside a Filament form (this package is not useful outside that context).
• Your users enter international numbers, and a country-code selector plus formatting materially improves UX or data quality.
• The field is non-critical or easily replaceable — admin-side capture, not a checkout or identity-verification flow.
• Your team is comfortable pinning the version, vendoring/forking under MIT, and owning a fallback if upstream goes stale.
• You have verified compatibility with your Filament major version, PHP version, and Laravel version, and that the repo shows recent commits, tests, and responsive issues.
• You need only input, formatting, and basic validation — not carrier lookup, number portability, or SMS verification.

Look elsewhere (or build a small internal component) when:

• The package shows no recent commits, no tests, or unanswered issues — the 3-star / 0-dependent profile is a warning sign, not a footnote.
• Phone numbers are on a revenue-critical path (signup, payments, 2FA) where a broken input blocks customers.
• You need enterprise support, SLAs, or compliance guarantees (data residency, auditability).
• You are not on Filament, or your Filament version is unsupported.
• You need features beyond input: verification, normalization pipelines, carrier intelligence. Pair a UI field with a dedicated validation library (e.g., propaganistas/laravel-phone) rather than expecting one plugin to do everything.
• A native Filament tel field plus server-side E.164 validation is sufficient for your use case — often it is.

How to Pitch It (Stakeholders)

For executives: This is a small, free, MIT-licensed UI plugin that lets us add properly formatted international phone fields to our Filament admin tools in days rather than weeks. It improves data quality at capture, which reduces failed SMS/OTP sends and cleans up customer records feeding our CRM and support stack. The trade-off is vendor risk: it is an early-stage, single-maintainer package with minimal adoption. We recommend a time-boxed pilot behind an internal wrapper component, with a documented fallback to a small in-house field if the package stalls. Cost of exit is low; the license permits forking. It is a delivery accelerator, not a platform bet.

For engineering: Treat it as a thin, replaceable adapter. Pin the version, isolate it behind our own form component, add regression tests around validation and E.164 output, and monitor upstream activity. If the package becomes unmaintained, we swap the internals without touching product code.