Phone Output Columns
Use this article if your batch processing includes Phone validation and you need to understand DQVerify phone columns. Applies to file-based batch processing only — not real-time API responses.
Dynamic phone field names
Phone output column names include the placeholder {FIELD_NAME_PHONE}. This is replaced by your actual input column name. Example: if your phone column is named mobile, then DQE_{FIELD_NAME_PHONE}_ERROR_CODE becomes DQE_mobile_ERROR_CODE.
Phone columns
| Column | Description |
|---|---|
| DQE_{FIELD_NAME_PHONE}_ERROR_CODE | Return code after Phone processing |
| DQE_{FIELD_NAME_PHONE} | Reformatted phone number returned by DQVerify |
| DQE_{FIELD_NAME_PHONE}_IS_MOBILE | Mobile detection (True/False) |
Phone error code values
| Value | Description |
|---|---|
| 0 | Invalid or non-existing phone number |
| 1 | Valid and attributed phone number |
Mobile detection values
| Value | Description |
|---|---|
| False | Number is not a mobile |
| True | Number is a mobile |
Best practices
- -Use the ERROR_CODE column to identify valid and invalid phone numbers
- -Use the reformatted phone value when business rules allow standardized values
- -Use IS_MOBILE to adapt communication channels (SMS vs. voice)
- -Keep the original input phone field to compare with DQVerify reformatted value