CRM Email and Phone Normalization Example
See a mixed-case email and formatted phone transformed into separate, stable matching fields without changing source values.
CRM Email and Phone Normalization Example
Real fields and representative values
| Source field | Operation | Target field | Example result |
|---|---|---|---|
| Domain from email | Email Domain | northstarlabs.example | |
| Phone | Digits only | Normalized Phone | 15550162201 |
Scenario
The specific job behind this example
A client CRM needs consistent email-domain and phone matching while retaining the original values exactly as entered.
Input
What the work started with
- Email: [email protected].
- Phone: +1 (555) 016-2201.
- Blank Email Domain and Normalized Phone target fields.
Output
What the completed workspace contains
- Email Domain: northstarlabs.example.
- Normalized Phone: 15550162201.
- Original Email and Phone remain unchanged.
The result is complete only after these checks.
A generated field, copied record, or finished diagram is not automatically correct. These checks define the minimum acceptance boundary for this example.
Validation checklist
- Repeating the transform produces the same output.
- Missing input does not erase an existing normalized value.
- No new contact record is created.
Reproduce the result
Normalize Contact Details Workflow Template
Inspect the starter structure, known limitations, product source, and setup steps before adapting this completed example to your own project.
More examples from this Kition surface
Ready when you are.
Kition is a desktop AI workspace for connected documents, structured tables, editable designs, whiteboards, visual workflows, and reviewable AI agents.