Ask a question in a broadcast and the answer writes onto every contact who replies. Free text captures verbatim. A constrained question captures a choice. Point it at a field you have, or name one inline and it mints on send.
A campaign asks a question by text and gets back two thousand replies nobody has time to read. The answer was data, and it died as a conversation.
A composer tool points the send at a field. The composer then states what it captures into, the field name, the options or free text, and whether the field is new.
A required target makes no new column. A named target that doesn’t exist yet mints one on send. Either way the answer lands on the record, not in a pile of replies someone has to sort.
Ask two thousand, six hundred answer. The blank count is a re-ask segment on its own. The question builds its own follow-up.
Free text on a record is a note. A captured answer is a field, and a field is something a segment can read. That’s the difference between a conversation and a database.
Name, phone, email, consent, stage, party, address, city, state, ZIP, district, risk. The required spine never renames or deletes, so a segment built on District means the same thing on every account. Custom fields sit beside them, defined once by an Owner.
Ask which issue matters most and each option becomes an audience. The schools answer gets the schools message. Nobody exports anything.
Keyword, pledge page, QR, and now capture. A send that asks is a send that learns, and the field it fills carries its provenance, the question, the send, the date.
Capture writes into the field registry today, and the field, the options, and the blank count are real in this build against seeded contacts. Live, the reply router reads the inbound message against the target field, mints a named field that doesn’t exist yet, and files the answer with the send that asked it.
Left or right, Txtra is the sender your carriers trust and your lawyers approve.
A composer tool that marks a message as a question and points it at a field. Free text captures verbatim, a constrained question captures a choice, and the answer writes onto the contact record instead of dying in a reply pile.
Yes. Name a field inline and it mints on send. Point at one of the thirteen locked required fields and no new column appears. Either way the field carries its provenance, the question, the send, and the date.
The blank count is a re-ask segment on its own. Ask two thousand, six hundred answer, and the fourteen hundred blanks become the next send. The question builds its own follow-up.