Solution skill
PhantomBuster placeholders are case-sensitive - #firstName# works, #firstName goes out as literal text
Complete solution
PhantomBuster placeholders are case-sensitive - #firstName# works, #firstName goes out as literal text. PhantomBuster message personalization failing silently? Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
PhantomBuster message personalization failing silently?
Fix
PhantomBuster message personalization failing silently? Expected: you can confirm this matches your situation.
When to use
- You are dealing with this situation.
- The symptom matches: PhantomBuster placeholders are case-sensitive - #firstName# works, #firstName goes out as literal text.
When NOT to use
- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported per the linked source. Source: https://support.phantombuster.com/hc/en-us/articles/24248994798482-How-to-Use-Advanced-Settings-for-Phantoms-and-Workflo.
Variant phrasings
PhantomBuster placeholders are case-sensitive - #firstName# works, #firstName goes out as literal text
Why it happens
PhantomBuster support (answered on their LinkedIn Search Export page): message placeholder tags are case-sensitive. Putting #firstName (missing the trailing #) in a message sends the literal text to the recipient - the correct placeholder is #firstName#. Always verify capital and small letters: #firstname# will not substitute either. The pattern is hash, camelCase name, hash: #firstName#, #lastName#, #companyName#.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Source
https://support.phantombuster.com/hc/en-us/articles/24248994798482-How-to-Use-Advanced-Settings-for-Phantoms-and-Workflows
Evidence
Source: PhantomBuster support (answered on their LinkedIn Search Export page): message placeholder tags are case-sensitive. Putting #firstName (missing the trailing #) in a message sends the literal text to the recipient - the correct placeholder is #firstName#. Always verify capital and small letters: #firstname# will not substitute either. The pattern is hash, camelCase name, hash: #firstName#, #lastName#, #companyName#.
Verified resolution: PhantomBuster message personalization failing silently? The placeholder tags are case-sensitive and need both hashes: #firstName# works, #firstName (no trailing hash) goes out as literal text to the recipient. Same for wrong casing - #firstname# will not substitute. If your outreach messages arrive with raw placeholder text, check the exact casing and the trailing hash before blaming the Phantom.
Source URL: https://support.phantombuster.com/hc/en-us/articles/24248994798482-How-to-Use-Advanced-Settings-for-Phantoms-and-Workflows
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_RUZ6FkfZccnr76sXp_4CTA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">PhantomBuster placeholders are case-sensitive - #firstName# works, #firstName goes out as literal text <span>— Vectle</span></a>