How to Import Viber Number Check Results into a CRM: TXT, Excel, and Field Mapping

AppShai’s current Viber-to-CRM workflow is a clear TXT upload → task processing → Excel export → CRM import sequence, not a zero-configuration API. With field mapping and history controls, a file workflow can be repeatable and gives the team a valuable validation point before CRM records change.

This guide follows a business confirming Viber channel status for existing customers. Button names vary by CRM, but the data-design principles remain the same.

Choose the Viber result the CRM actually needs

Viber task	Current supported fields	CRM question
Registration Check	Phone number and registration status	Does the customer have a supported Viber registration signal?
Activity Check	Phone number, active days, mid, and offline time	Does an existing service workflow require time-related fields?
Age and Gender Check	Phone, skin tone, gender, nickname, active days, mid, offline time, people in picture, picture type, age, and picture	A defined workflow with necessity and sensitive-data review

If the CRM needs channel status only, Registration Check is enough. More columns add matching, permission, and retention cost; they do not automatically create sales value.

Step 1: export the permitted source list

Select CRM records with traceable provenance, a current business purpose, and no opt-out. A working spreadsheet may contain internal customer ID, original number, country, source, and permission, but all of those values should not enter the upload.

Add a normalized-phone column. Use source-country information to add the international code, remove spaces, brackets, and hyphens, and flag records with unknown country or impossible length. Do not guess country from number length.

Step 2: create phone-only TXT

Copy valid normalized numbers into plain text, one per line, deduplicate, and save UTF-8. AppShai accepts TXT only; Excel and CSV cannot be uploaded directly. Names, customer IDs, provenance, emails, and notes stay out of TXT.

+447911123456
4915123456789
84901234567

Keep the internal-ID mapping in the working spreadsheet. It is the bridge that safely reconnects Excel results to CRM records.

Step 3: run the matching AppShai task

Open the AppShai Viber Number Checker and select Registration, Activity, or Age and Gender according to the target fields. Use a small sample for the first run to confirm parsing, country codes, and column alignment before scaling.

Record task name, creation time, operator, input-file version, and business purpose. These values explain where a later CRM field came from.

Step 4: validate the exported Excel

Preserve an untouched export, then create a working copy. Compare valid input and output rows, duplicates, exceptions, missing values, and number joins. Format phone columns as text to prevent scientific notation, truncation, or lost plus signs.

Interpret fields by task. Registration is not marketing consent. Offline time is not real-time presence. Gender, age, skin tone, and image fields may be missing and are not identity verification.

Step 5: design CRM field mapping

Avoid placing every result in one vague Viber-status field. Use traceable fields:

• viber_check_service: selected service;
• viber_registration_status: registration result;
• viber_active_days, viber_offline_time, and viber_mid: activity tasks only;
• viber_checked_at: check date;
• viber_result_version: export or task identifier;
• viber_result_note: exceptions and missing-value explanation.

Permission, provenance, and opt-out remain original CRM fields and are never replaced by a check result.

Step 6: simulate before production import

Match on internal customer ID when possible. If phone number is the only key, apply exactly the same normalization on both sides. Import first into a test environment or copied data view and count successful matches, unmatched rows, one-to-many conflicts, and fields scheduled to change.

After review, update production records and retain an import batch ID. Do not clear an existing CRM value merely because an Excel cell is blank unless an approved business rule requires it.

A compact field-mapping example

Excel column	CRM target	Rule
Phone number	phone_normalized	Match only; do not overwrite the source value
Registration status	viber_registration_status	Write the current result
Active days	viber_active_days	Activity task only
Offline time	viber_offline_time	Store with the check date
Task date	viber_checked_at	Required for every import

Rollback and history

Before production import, export the affected CRM records as a backup and preserve the batch ID plus changed-field list. If something fails, restore fields from that batch instead of replacing the whole database. For repeated checks, use a history table so one customer can have several dated observations.

Do not recheck on an arbitrary calendar. Create another task only when the business relationship remains valid, an old result no longer supports a current decision, and the user has not opted out.

Pre-launch checklist

• Provenance, permission, and current purpose are confirmed.
• The upload is genuine UTF-8 TXT with one number per line.
• Excel or CSV has not been uploaded directly.
• Service and CRM fields align.
• The original Excel export is read-only.
• Match rate, conflicts, and blanks passed a simulated import.
• Check date, task version, and batch ID are stored.
• A rollback export exists.

With these controls, Viber results become explainable CRM data rather than a collection of new labels with no audit trail.