Why do phone numbers look broken?
Excel writes a long number as 9.05332E+11 and the digits vanish. Format the phone column as Metin in the source file, save .xlsx, upload again.
The panel reads a number exactly as the file hands it over, and most damage starts in the file. Excel turns a 12-digit phone typed as a number into scientific notation. For .xlsx the panel rebuilds those digits from the raw cell; for .csv it cannot, because the digits went missing on save. The Geçersiz counter on the summary step tells you how many rows were dropped.
Before you start
- The source file, openable in Excel. This repair happens in the file, not in the panel.
- The phone column formatted as Metin, with 8 to 15 digits in every number.
- A .xlsx save where possible. Scientific notation written into a CSV never comes back.
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Find the damaged numbers in the preview table
Open Veri İçe Aktar from the Listeler tab of Veri Yönetimi and upload the file. Read the phone column in the preview table of step 1. Dosya.
Format that column as Metin in the source file
Select the phone column in Excel and set its format to Metin. Write each number as 905xxxxxxxxx and save the file as .xlsx.
Watch the Geçersiz count fall on the summary step
Press Değiştir, pick the new file and move to step 3. Özet. The amber scientific-notation note should disappear, and Geçersiz should land where you expect.
Result checkIf it did not work
Check these
- An amber note about scientific notation on a CSV means the digits are already lost. Go back to the original Excel file rather than editing the CSV.
- Once the import finishes, the summary step lists sample rejected numbers. Use the CSV indir link to download gecersiz-numaralar.csv.
- Adding a single record can return Geçersiz telefon numarası. Write the number with its country code; the example format on screen is 905xxxxxxxxx.
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 29 August 2026.
