Lead capture & contacts

A contact database that can prove what it claims

Anyone can store a checkbox. When a complaint arrives four years later, what matters is the wording you showed, the page it was on, and when the person actually clicked. All three are recorded here, and none of them can be edited afterwards.

Request access Why it matters

Three ways in, one record

However a lead arrives, it lands in the same place

Deduplicated on a case-folded email and an E.164 phone number, per organization — so the same person filling in two forms is one contact, not two.

Hosted lead forms

A public page at your own link, or embedded in the site you already have. Separate email and SMS consent checkboxes, never pre-ticked, with the required disclosures checked before you can publish it.

Honeypot · rate limited · field allowlisted

CSV import

Map your columns, preview exactly what will land, then import. You declare where the list came from and attest to it before a single row is written — and the summary tells you what was refused.

RFC 4180 · batched · resumable

Meta lead ads

Leads from Facebook and Instagram lead ads flow in as they are submitted, matched to the Page you connected. Nothing is dropped even if retrieval is delayed.

Signature-verified webhook

The consent model

Four states per channel, not a checkbox

“Never asked” and “told me no” are different facts with different rules. Flattening them into one boolean is how agencies end up texting someone who opted out last year.

Consent states and who can set them
State	What it means	Who can move a contact here	May we send?
Unknown	Never asked. The contact exists, but nobody has sought permission.	Default for an imported or manually added record	NO
Pending	Asked, not yet confirmed. Waiting on a double opt-in reply.	Set when a confirmation is sent	NO
Granted	Permission given, with the exact wording and timestamp on file.	A lead form, a double opt-in, the API, or a declared import	YES
Revoked	They said no. Nearly terminal — and deliberately hard to undo.	Only the contact themselves can lift it	NO

Segments

Saved questions, not frozen lists

A segment stores the filter, never a snapshot of who matched it. Membership is recalculated every time you use it, so somebody who opts out today drops off every segment today — rather than lingering in an export from March until somebody remembers to refresh it.

Filter by contact type, tag, source, consent state per channel, or when they were added. Live counts show how many are actually reachable on email and on SMS, which are usually two different numbers.

Saved segments

Caregiver applicants — Mesa412email288sms
Families, enquired last 90 days1,204email331sms
Referral partners86email71sms
Newsletter subscribers3,961email0sms

Start with a form that holds up

Hosted lead forms ship with compliant default wording, so the first lead you capture is already evidenced properly.

Request access See how campaigns use it

Questions first? contact@swift-pivot.com

State

What it means

Who can move a contact here

May we send?

Unknown

Never asked. The contact exists, but nobody has sought permission.

Default for an imported or manually added record

Pending

Asked, not yet confirmed. Waiting on a double opt-in reply.

Set when a confirmation is sent

Granted

Permission given, with the exact wording and timestamp on file.

A lead form, a double opt-in, the API, or a declared import

YES

Revoked

They said no. Nearly terminal — and deliberately hard to undo.

Only the contact themselves can lift it

Saved questions, not frozen lists

Filter by contact type, tag, source, consent state per channel, or when they were added. Live counts show how many are actually reachable on email and on SMS, which are usually two different numbers.