Data management

Your customer data, handled with intent.

What we hold, how identity is verified with SSN and date of birth, and how accounts get in — by direct upload or automated SFTP, your choice — then reconciled back to your partner every day.

The customer record

What sits behind every call.

A compact, purpose-built record. Some fields come straight from your source; others we derive; one is sensitive and treated accordingly.

Account / Loan IDThe unique key that ties every call, outcome, and report back to one customer.Core
Name & phoneWho to call and how to reach them — the minimum needed to place a call.Core
Address → time zoneWe derive the state and IANA time zone from the address so every call lands in the right window.Derived
BalancesLoan amount, total balance, payoff, and arrears — read live to the customer once verified.Core
SSN + Date of birthHeld only to confirm identity mid-call. Never read back to the customer.Sensitive
Processing & contact windowWhen the account becomes callable and its follow-up cadence — managed automatically.Derived
Identity verification

SSN + date of birth — confirmed, not exposed.

Sensitive actions only happen after the caller proves who they are. Here's how that check runs mid-conversation.

Asked on the call

Before any sensitive action, the agent asks the customer for their date of birth and SSN — spoken naturally, in conversation.

Matched, never exposed

The values are combined and checked against the record on file as a simple match / no-match. The agent never reads the SSN back, and nothing sensitive is surfaced in the transcript.

Verified or failed

On a match, the agent proceeds with actions like taking a payment. On a mismatch it follows your failure path — re-try, escalate to a human, or end the call.

Data ingestion

Two ways in. Same destination.

You're not locked into one pipe. Upload a file by hand or wire up automated SFTP — the system handles both and converges them into one clean queue.

Automated SFTP

Best for — Ongoing, high-volume, partner-integrated feeds that should run continuously and untouched.

  • Your partner drops a dated file into a secure SFTP folder.
  • The system pulls on a schedule — several times a day.
  • Each new-accounts file is parsed straight into accounts.
  • Runs hands-off, with no human in the loop.

Either way, every record is normalized, enriched with its time zone, de-duplicated against existing accounts, and queued identically. The dialer doesn't care how the data arrived.

Closed loop

Reconciled back to your partner, every day.

Ingestion isn't one-way. The system delivers same-day, fully reconciled files so your partner's books always match what actually happened on the phones.

↓ INGEST

New accounts in

Each day's drop of fresh accounts to call — turned into queued accounts automatically.

WelcomeCalls_YYYYMMDD.csv
↑ DELIVER

Call data out

Every outbound attempt and its outcome, delivered back same-day.

CallData_YYYYMMDD.csv
↑ DELIVER

Inbound data out

Every inbound call received that day and how it was handled.

InboundCallData_YYYYMMDD.csv
↑ DELIVER

Manual data out

Accounts your team marked as contacted by hand, reconciled into the same feed.

ManualCallData_YYYYMMDD.csv

Isolated & access-controlled

Your customer data lives in its own database, reachable only by the system and your authorized operators.

Audited & separable

Manual changes leave a paper trail, and test calls are flagged so they never mix with real customer data.

Ready when you are

Plug in your data. We'll do the calling.

Pick a package and we'll wire your source — upload or SFTP — into the queue in weeks, not months.

View packages See the funnel