Prepare a lead list a person can stand behind
Published by Labbie AI ยท Reviewed . First-party editorial guidance based on implemented interfaces and the limitations stated below.
Decide who belongs on the list
Start with the reason each person expects contact. A recent enquiry, an event registration or a request for a callback can have different purposes and contact preferences. Keep a record of the source and permission available to your team. An exported phone column is not permission to call. Exclude people who asked you to stop, and ask an appropriate adviser when the purpose or legal basis is uncertain. This is an operational preparation checklist, not legal advice or a claim that importing a file makes a campaign compliant.
Make the spreadsheet reviewable
Use a working copy of the original export so you can trace corrections. Keep one intended contact per row and consistent column labels. Identify which column contains the telephone number, then inspect whether spreadsheet software has dropped a leading zero or changed a value to scientific notation. Labbie's supported import kinds include CSV, TSV and Excel workbooks, but support for a format is not proof that every ambiguous row can be repaired. Exporting a Google Sheet as a supported file is different from connecting a live Google Sheets integration.
Treat phone formatting as a check, not identity proof
Malaysian phone-number handling normalizes recognizable input and holds uncertain values for operator review. Keep the source value until corrections are confirmed. Do not guess a missing digit, assign a country code merely from a person's name, or treat a successfully formatted number as proof of ownership. Review shared business lines, old enquiries and multiple numbers for the same contact carefully. A number may be syntactically plausible and still belong to someone else. Resolve uncertainty with the source owner before including the row in an approved calling exercise.
Choose the business context
Prepare the facts the agent is allowed to discuss alongside the list. A campaign selects one primary offer; several projects in a library do not mean the campaign can safely combine all of them. For a property enquiry, confirm the project and the approved price explanation with the responsible person. Remove stale promotions and separate lists when the intended offer differs. Keep a human callback owner available for questions the approved information cannot answer. Never fill gaps with assumptions about a customer's budget, eligibility or willingness to buy.
Review duplicates and contact preferences
A duplicate can represent a repeated export, a shared line or two different people. Decide the matching rule with your team before removing rows, and preserve an audit note for uncertain cases. Apply stop requests consistently across the systems your team uses. The retry refusal for a do-not-call lead is a product control, not a substitute for an up-to-date suppression process. Agree who can correct a record, who checks the imported list and when a refreshed export should replace an older working copy.
Finish with a release checklist
Check the imported row count against the intended source, review held numbers, confirm the selected offer, choose allowed days and hours, and name the person who will review outcomes. Live calling release remains owner-gated, so complete account and route availability confirmation before any real outreach. A simulation can reveal script problems but cannot establish lead-list permission or telephone connectivity. Begin only with an explicitly approved scope, then examine available outcomes and transcripts before deciding on further activity.