The lists we went out to, as opposed to the leads that came in. Drop a day's CSVs here — the filename says which state and which day, so ar0831-ready.csv and ar0831-ready-2.csv both file themselves under Arkansas on the 31st. Every number is matched against the CRM on the phone number, so a file can be judged on the sales it produced rather than on how many rows it had.

Upload a file of filings and it is mailed. Before anything goes to PostGrid the file is scrubbed: any business whose name has reached the website (a lead at any stage, or a tracked click), any business already mailed from an earlier file, repeats within the file, and rows without a usable address are taken out. Everything left is sent as a letter straight away.

Notify your team by email when a lead hits a trigger. These go to internal recipients — not to the lead.

Every product needs at least one live gateway. Weights are relative shares inside a product — 70 and 30 split traffic 70/30, and so do 7 and 3. Set a weight to 0 or flip a gateway off to pull it out of rotation without losing the link.

{}

const cfg = await fetch('/api/merchants/config').then(r => r.json());
const p = cfg.products[serviceType];        // 'standard' | 'extended'

// One random draw, one winner — the ranges already encode the weights.
const r = Math.random() * p.total_weight;
const gateway = p.gateways.find(g => r >= g.range_start && r < g.range_end) || p.gateways[0];

window.location = gateway.url;              // gateway.merchant tells you who took it

Every succeeded Stripe charge in the range against every CRM lead in a sales stage (Paid, Pending Info, Need Info, Completed, Refunded, Reversal, Error), dated the same way the Dashboard dates a sale. Anything that exists on one side and not the other is listed below. Nothing here changes a stage — the only write is Link, which records the Stripe id on the lead.

Create and remove CRM logins, and choose which of them need an emailed code to sign in. Only administrators can see this tab.

A role is a set of permissions. Every protected route checks them on each request, so what you switch off here is refused by the server — not just hidden in the interface.

Every change to a lead, its notes and its documents — who made it, when, and what moved. Entries are append-only: nothing in the CRM edits or removes them, and deleting a lead leaves its history behind. Automated postbacks are recorded too; use People only to see just what staff did.