Your account holds a pool of sending lines. The first time you reach a voter, they get pinned to one of them. Every message to that person after that goes out from the same line, the whole cycle. They see one number, one thread, one campaign.
A voter gets a text from you in September. Another in October, from a different number. A third in November, from a third. To them, that's not a campaign. That's three strangers, and the third one gets a stop.
The first text pins the voter to a line in your pool. The pin lives on their record, not in a setting someone forgets.
September, October, November, the same ten digits every time. A steady number over weeks reads as someone they know.
A voter who texts back reaches the number that texted them, not a stranger’s line. The thread stays intact, both directions.
A text in September, another in October from a different number, a third in November from a third. To the voter that’s three strangers, and the third one gets a stop. Same number ends that.
Carriers hunt the pattern where one message ducks the filters across a wall of numbers. That pattern has a name, and it’s the loophole shops’ whole playbook. One line, many messages, a real thread reads clean, and clean is the floor you sell.
Two-way texting only works when the voter’s reply reaches the campaign that texted them. The pin is what keeps the conversation one conversation.
Verified sender is the name on top. The pinned line is the consistent number underneath it. Together, one voter, one number, one name, every time.
Everyone else calls this sticky sender. Say that once, to the buyer who’s heard the term, right before you tell them yours does more than stick. Then call it what it is. The voter gets the same number every time, and the name already told them so. One honest note. The pin lives on the contact in the live version, mapped voter to line, read on every send. In this build the assignment shows on the record and holds across sends. Wiring it to the real number pool and the reply router is the live step, and it drops cleanly onto the account and number model already in place.
Left or right, Txtra is the sender your carriers trust and your lawyers approve.
The first text pins a voter to one line in your pool, and every message after goes out from it, the whole cycle. One number in their phone, one thread, and replies that reach the campaign that texted them.
That's the term the rest of the market uses. Ours pins per voter on the record, keeps the reply thread intact both directions, and runs underneath Verified sender, so the voter sees one name and one number every time.
Yes. The pin lives on the contact record and every send reads it. In this build the assignment shows on the record and holds across sends. Live, it wires to the real number pool and the reply router.