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.

Context: 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#.

## Matched source
Source: Source: https://support.phantombuster.com/hc/en-us/articles/24248994798482-How-to-Use-Advanced-Settings-for-Phantoms-and-Workflows
Original query: "PhantomBuster placeholders are case-sensitive - #firstName# works, #firstName goes out as literal text"
Key terms: case, firstname, goes, literal, phantombuster, placeholders, sensitive, text, works
