All guides

Outreach

Strip emojis from B2B prospect names

Compare the display and cleaned values. Accents, apostrophes, and meaningful hyphens should survive.

Start with a small representative sample

A recruiter exports public professional names that have rocket icons, flags, and decorative characters next to otherwise valid Unicode names.

Choose a source page you are authorized to use. Make a named list for the job so you can compare new rows with earlier entries from the same source. Include a typical row, a row with a missing or ambiguous value, and a row with formatting that tends to break the next step. A sample can be just a few rows as long as it gives you a way to verify the process before using a whole campaign.

Test a decorative emoji between words as well as one prefixed to the name. A gap can matter when adjacent pieces should remain separate tokens.

Check the source before export

Keep an approved and a review-only group while you work. Personalization fields are easiest to audit when you can see the original source beside the value that will appear in a draft. One changed value can affect the greeting, a conditional branch, or a reference to an employer. Review those lines before campaign scheduling. When the source field is unclear, keep the row for research and use the sending tool’s neutral fallback only when the contact is otherwise appropriate.

A name field made only of symbols should become a blank review case. Flag emojis may consist of multiple Unicode code points.

Write down the number of source records you expect to review. If only part of a source table renders at once, make sure your count describes the portion you actually captured. The evidence can be simple: a distinct first row, a last visible row, and a field you can find again later. On a repeated run, these reference points help explain the difference between a bad mapping and a changed source page.

Work through an example

The table shows what a useful before-and-after check looks like for Full Name. Use it as a model for your own field map. Inspect the visible input first. Look at the output in its intended form, then consider what an operator would do if the source value turned out to be unavailable or different. When the field has more than one legitimate interpretation, include a second example with a different expected result.

FieldVisible exampleExpected result
Full Name🚀 Zoë D’Angelo ✨Zoë D’Angelo

Compare the display and cleaned values. Accents, apostrophes, and meaningful hyphens should survive.

Check both the displayed display-name input and the derived first and last values. Entries with no actual letters need a manual decision before personalization.

Compare ‘Marie 🚀 Claire’ with ‘Marie🚀Claire’. The former has clear separation even after cleanup. The latter may require a human decision about spacing. Use the source display to resolve it rather than inventing an extra name token.

Review the cases that can slip through

Deleting all characters outside ASCII can corrupt names and make a friendly greeting look careless.

An emoji-cleaning test should include a flag, a skin-tone modifier, and a family emoji as well as a single rocket. Add one accented name and one non-Latin name. An import rule that only looks right for the most common English examples can still damage a significant share of a cross-border list.

Check the sample after filtering and editing. Search should return both the ordinary case you expect and the exception you selected deliberately. If the exception is hard to find, add a review note or place it in a separate list. Keep an original source reference where it is useful. The goal of this pass is a repeatable decision about those few ambiguous rows before the selection takes on a life of its own.

Prepare the destination

In the Workbench, choose the outreach preset and review the derived fields alongside the original values. A clean name and a company label sit in separate columns so they can have different handling. A standard export can still support manual mapping where you want to keep a wider set of source columns. Retain the original spelling before correcting a display error and check for punctuation that affects how the final message reads. Preview the exact destination variables before sharing the batch.

Export with UTF-8 and review imported names in the destination preview before storing or using them in a greeting.

Label the first output a trial and record the list name, selection, target format, and the field that determines whether the row can be used. Compare at least one expected blank and an ordinary populated row after export. Keep test changes easy to roll back. For larger jobs, measure the number of rows that need manual handling so you know where the remaining review will take time.

Validate what the recipient will use

Test with a fictional or approved contact. Review the fully rendered greeting and company reference instead of relying only on the preview table. The person approving the final outreach needs to know which values were actually visible and which were derived heuristically. A formatted name or syntactically valid address gives no assurance about permission, freshness, or the appropriateness of sending. Apply the destination’s relevant suppression list before any approved outreach.

Look for invisible formatting or records stored in a different character encoding while reviewing exports. A name rendered correctly in one app can be imported incorrectly by another.

Sample the exported last and first names in the exact browser or CRM that will use them. Emoji components, zero-width formatting, accented characters, and apostrophes have different meanings. A policy that treats them all as decoration can alter a name even when the row looks clean at first glance.

Review one result where the converted value looked straightforward and one where your team had to choose between plausible interpretations. Give the recipient the updated row count and a practical next action. If review exposed a source inconsistency, note the observable issue and include enough context for the recipient to reproduce it. Close the loop by storing or removing the trial material according to how long your team needs it.

Record the minimum needed for a repeat run

Save a simple checklist with your source path, list name, review filter, format, and destination fields. Keep the choices about Full Name near the top so the next operator can pick a meaningful test row. A useful recurring process records the fields that affected the outcome and the points where someone needed judgment. It can be rerun when the source layout changes without forcing every old decision into a script.

LeadSheet Clean keeps captured rows and derived values in the browser. Start with Standard Clean CSV or copy TSV when you need a quick review sample. Lifetime Pro adds unlimited export rows, specialized presets, PDF briefs, and multi-list ZIPs. Select the path that produces the format and selection required for your handoff, and verify the license or Free allowance before repeating a large export.