Elysia Tools
Navigation
Workflow Playbook
Check email, phone, and postal code syntax with country or region context for single values and batches, while keeping format results separate from deliverability, reachability, and address existence.
Hubs
This workflow is for cleaning contact and postal fields before a form submission, CRM import, or operational handoff. Keep the raw value, the selected country or region, the validator used, and the reason attached to each result. A blank value is different from a malformed value, and an unknown country should not be silently assigned a default.
For one email or phone number, start with email-validator or phone-validator. If phone numbering depends on country context, use global-phone-validator. For postal codes, global-postal-code-validator covers supported international patterns, while us-zip-code-validator is the focused choice for US ZIP and ZIP+4 values. A regional match is not an address lookup.
Use batch-email-validator and batch-phone-validator for imported lists, preserving row numbers and failure reasons so corrections can be replayed. Recheck changed values rather than overwriting the source. If a team needs shipping or delivery context, continue to contact-shipping-validation or email-mime-delivery-workflows; use validation-format for a wider catalog of syntax checks.
Accept a field for the next formatting or import step only when its rule, geography, and reason are documented. The result must explicitly say that syntax does not establish email deliverability, phone connection, address existence, identity, or delivery success.
Workflow playbook
Validate a single email and phone value first, retaining the input, the normalized display where available, and the exact syntax or quality warning for any rejection.
Use country-aware phone validation and the matching postal rule. Select the US-specific checker only for US ZIP or ZIP+4 data; do not infer an address from a passing code.
Run imported email and phone columns through the batch tools, preserve row numbers and failure reasons, and send blanks, ambiguous countries, and borderline results to manual review.
Use the single-value validators for form entries and exceptions; use the batch email and phone validators for imported columns so row-level failures remain visible.
Use global phone and postal checks when the country varies, and use the US ZIP validator only when the field is explicitly a United States ZIP or ZIP+4 value.
Treat pass as a syntax or supported-pattern result. Route deliverability, phone reachability, address existence, and uncertain regional cases to separate verification or human review.