Email & SMS

Ballot Signal + Hustle

Via webhook Webhook Nonpartisan API key

What is Hustle?

Conversation-first peer-to-peer texting, where a warm consented contact converts far better than a cold one.

It sits in the Email & SMS category of a campaign stack. The channels that live or die on a defensible consent record.

Who uses it

Nonpartisan. Used across both parties and by nonpartisan organizations.

How the Ballot Signal + Hustle integration works

Supporter records reach Hustle as a list import or via the universal webhook. SMS-consented records only, with consent columns carried through.

What syncs

  • Contacts
  • Groups

Field mapping

The supporter record is the same shape everywhere. What changes is where each field lands. The full record is documented on what you get.

Supporter record field mapping
Supporter record Messaging object Notes
firstName, lastName Subscriber / profile Left empty rather than guessed when resolution is not confident.
email Subscriber / profile — primary identifier Primary match key. Lowercased before hashing.
phone Subscriber / profile — phone field Included only when SMS-specific consent is present.
addressLine1, city, state, zip Subscriber / profile — address fields Third dedupe fallback.
consentTimestamp Custom fields or merge fields ISO 8601, UTC.
consentVersion Custom fields or merge fields The language in force at the moment of consent.
consentSource Custom fields or merge fields The exact page URL where consent was captured.
consentCategories Custom fields or merge fields Normalized from your consent platform.
intentSignals Tags, lists or segments Donate-page, volunteer-page, issue-page and any you define.
utmSource, utmMedium, utmCampaign, referrer Custom fields or merge fields or source fields Carried verbatim.
dedupeKey Match key Lowercased email hash. Match order: dedupeKey, then phone, then name + address.

How to set it up

  1. 1

    Confirm SMS-specific consent on the capture page.

  2. 2

    Export SMS-consented supporters as CSV with consent columns.

  3. 3

    Import into the Hustle group your agents will work.

  4. 4

    Retain the consent export.

  5. 5

    Brief agents that these are inbound-consented supporters, not a cold list.

Why it matters

Conversation-first peer-to-peer texting, where a warm consented contact converts far better than a cold one.

Ballot Signal + Hustle: questions

Is the Hustle integration available today?

Via webhook. Not a native connector. This works today through our signed universal webhook, and someone on your side (or your consultant) wires up the endpoint. Full supporter record, full consent record, no UI.

What authentication does the Hustle integration use?

API key. Credentials are stored encrypted and are never rendered back into the interface after entry.

Will this create duplicate records in Hustle?

No, assuming you leave deduplication on. We match on the lowercased-email hash first, then phone, then name plus address. On a match we update rather than create, and only the fields you have marked overwritable.

Does the consent record travel into Hustle?

Yes. Consent timestamp, consent version, consent source URL and granted categories are included in every push, by default, and there is no configuration that strips them. That is the point of the product.

Does connecting Hustle make a phone number legal to text?

No. Nothing does. We capture and preserve the consent evidence in the form platforms and carriers expect, so the consent you actually collected is provable. If you did not collect express written consent to send automated texts, we will not manufacture one. Read the TCPA page first.

See what your own website already knows.

Book a 20-minute walkthrough. We will look at your site's current consent posture first — that part is useful whether or not you buy anything.