Where's the reasoning behind the direction?

The roadmap explains the themes and why we've chosen them.

The Txtra Roadmap Board

September 6, 2026

The whole picture at a glance. Shipped is concrete, it's already live in the product. Building now and Next are directions, not a named feature list, on purpose: we'll tell you where we're headed without publishing a build order a competitor can race us to. For the dated record of what's shipped, see the release notes; for the reasoning behind the direction, the roadmap.

Shipped

BroadcastOne-to-many sending with per-recipient quiet hours

Two-way inboxReplies in a real inbox, with tagging

P2P conversationsHuman-in-the-loop peer sending

SequencesAutomated multi-step drip flows

AutoresponderKeyword-triggered replies and opt-in

Scheduled sends & AutopilotQueue sends ahead; return-file sends on a tap

Voter file & audienceImport, match, and manage the list

Smart import & matchingExcel + CSV, column mapping, voter-file append

GrowForms, keywords, and QR list-building

SegmentsSlice the list by attribute

List hygiene & scrubLitigator/landline scrub, in-house at import

TemplatesReusable, on-brand messages

ReportsReal outcomes, not vanity clicks

Link & click trackingAuto-shortening with per-recipient clicks

Conversion & fundraising outcomesGift webhook ties dollars to sends

Compliance layerConsent, STOP/HELP, quiet hours, audit trail

One-tap 10DLC registrationBrand + campaign filing, filed by Txtra

Verified RCSBranded, verified sending with SMS fallback

AI, the magenta sparkleDrafting, suggested replies, always labeled

Command dashboardLive program metrics at a glance

Teams, roles & 2FASeats, scoped access, secure sign-in

Building now

Sharper, always-labeled AIMore drafting help, same transparency

Richer RCS cardsRich cards as a first-class composer control

Deeper integrationsCleaner fit with fundraising and CRM tools

Wider verified RCSFollowing carrier and device support

More automation depthDeeper sequencing and behavior triggers

Down-ballot election coverageReaching below Congress

Building now

Making compliance more invisibleLess for you to remember, more the platform handles

Sharper, always-labeled AIMore help, same transparency

Deeper team controlsTighter scoping for staff and volunteers

Richer messaging as RCS spreadsFollowing carrier and device support

Deeper integrationsCleaner fit with the tools you already use

Stronger outcome analyticsSends tied more directly to results

Down-ballot election coverageReaching below Congress

Cards move left as they ship. Shipped is exact; the right two columns are the direction, the specifics stay internal until they land, and then they get a dated release note.

What's not on the board, and won't be

Anything that buys speed by cutting a compliance corner. No feature to text unconsented numbers, no way to dodge opt-outs, no AI that sends in your name without you. Those aren't stalled cards, they're deliberately off the board.

Frequently asked questions

Why are the "Building now" and "Next" cards vague?

On purpose. Shipped features are already public in the product, so we name them. Upcoming work is described as a direction rather than a named feature, so customers see where we're headed without a competitor getting our exact build order.

How do I know when something ships?

It moves to the Shipped column and gets a dated release note. The board is the picture at a glance; the release notes are the record.