Audrey · Entity Submission — Twilio 1-800

AUDREY · BUSINESS IDENTITY · 12 MAY 2026

First audrey-prefixed dev report. Incubating in devreports.dare.co.uk per project_audrey_devreports_lifecycle.md until volume or ownership change warrants a move to devreports.audreyinc.com.

TL;DR

• Twilio toll-free verification for an audrey 1-800 number returned null during the KYC step. Cause: audrey’s Brooklyn-address entity exists in NY Department of State records but hasn’t propagated to commercial-aggregator databases (LexisNexis Risk Solutions, D&B, Experian Business) that Twilio’s vetting flow queries.
• The fix is a 4-layer identity stack: state DOS filing (exists) → IRS EIN (assumed exists) → D&B D-U-N-S Number (missing — this is the unlock) → LexisNexis/downstream (auto-propagates from D&B over ~2-4 months).
• D-U-N-S submission is free via the patient 30-day path on dnb.com; expedited paid path (~$200, 5 business days) only worth it for a deadline.
• One calendar entry to set: 90 days post-D-U-N-S → pull LexisNexis Consumer Disclosure report to verify clean propagation. Single check, future-proofs years of KYC friction.

What happened

audrey requested a toll-free 1-800 number through Twilio. Twilio’s toll-free verification flow runs a KYC check on the business — querying commercial-database aggregators (LexisNexis Risk Solutions and similar) to confirm the entity exists, is in good standing, and matches the submitted address. The check returned null on audrey, because:

• audrey IS a registered NY entity, at a Brooklyn address.
• That address (and the entity itself) doesn’t appear in commercial-aggregator databases because no D-U-N-S Number has been issued. D-U-N-S is the most common upstream feeder into LexisNexis-class databases; without it, NY DOS filings can take years to propagate, especially for small entities at unusual addresses.

Result: Twilio’s verification system has nothing to match against, so it returns null even though the entity is completely legitimate.

Root cause

The 4-layer business identity stack (top = authoritative, bottom = where KYC vendors look):

The Twilio null isn’t a problem with audrey’s legitimacy — it’s a coverage gap in the commercial-aggregator layer that the D-U-N-S submission directly fixes.

Action plan

1. Confirm Layer 1 — NY DOS canonical entity record

Action: lookup at https://apps.dos.ny.gov/publicInquiry/. Search by entity name (AUDREY DESIGN, then variations: AUDREY DESIGN INC, AUDREY INC, AUDREY DESIGN LLC).

Capture: - Exact registered entity name (D&B is case-sensitive) - DOS ID - Registered agent name + address - Principal address (the Brooklyn one) - Formation date - Filing status

Save into project_audrey_business_identity.md once located.

2. Confirm Layer 2 — IRS EIN

Action: locate the EIN from audrey’s formation paperwork or tax filings. If lost: IRS Form SS-4 can be re-requested via https://www.irs.gov/businesses/employer-id-numbers.

Capture: - EIN - Date issued - Federal tax classification

3. Submit Layer 3 — D&B D-U-N-S (the unblocking step)

Action: https://www.dnb.com/duns-number/get-a-duns.html → choose the free path (D&B buries it under upsell prompts; it’s labelled along the lines of “Standard / 30-day”). Avoid paid expedite unless there’s a deadline.

Submission requires: - Exact NY DOS entity name (from step 1) - Brooklyn registered address - EIN (from step 2) - Brief business description - NAICS code: 315990 (Apparel Accessories & Other Apparel Manufacturing) or 448190 (Other Clothing Stores) — pick whichever matches actual operations - Owner contact + estimated annual revenue (broad-band OK; no precise disclosure required)

Decline the upsells. D&B will pitch Credibility Builder, monitoring, trade-references, paid scoring products. None are necessary. The D-U-N-S Number itself is the deliverable.

Timeline: 30 business days from submission to issuance, free path. 5 business days if paid.

4. Wait + verify Layer 4 — LexisNexis & downstream

Action: ~90 days after D-U-N-S issues, pull audrey’s record via the LexisNexis Consumer Disclosure portal: https://consumer.risk.lexisnexis.com. (Labelled “consumer” but business records are accessible too.)

Verify: - Entity name matches NY DOS exactly - Address matches DOS exactly - D-U-N-S Number recorded - Status: Active

If anything is wrong or missing: dispute via the same portal. The dispute path is the only “submission” surface LexisNexis exposes — and it only works once they already have you in the database.

5. Re-attempt Twilio 1-800 verification

Once the LexisNexis Consumer Disclosure pull (step 4) shows audrey present and accurate, retry the Twilio toll-free verification. The null should resolve to a positive match.

Why this matters beyond Twilio

The D-U-N-S + LexisNexis path doesn’t just unblock Twilio — it unblocks essentially every B2B/fintech/wholesale KYC touchpoint audrey will encounter:

One free 30-day form solves all of them simultaneously. The upfront work pays back across the next several years.

Open items for audrey

• [ ] Locate the canonical NY DOS entity name + ID
• [ ] Locate audrey’s EIN
• [ ] Decide on NAICS code (315990 vs 448190 — pick one based on actual operational mix)
• [ ] Submit D-U-N-S free request
• [ ] Calendar entry: pull LexisNexis Consumer Disclosure report ~90 days after D-U-N-S issues
• [ ] Re-attempt Twilio toll-free verification after layer 4 is clean

Portability — applies to dogwood + clients

This is exactly the same stack any portfolio property will need. Dogwood operates in NYC/CT/Hamptons and will eventually hit the same KYC walls (wholesale dog-supply buyers, insurance providers, premium banking). Future dare client work will encounter it at the formation stage. The runbook in project_audrey_business_identity.md generalises; per-entity status memories (project_dogwood_business_identity.md, etc.) instantiate it.

Linked memories

• project_audrey_business_identity.md — new today — the canonical reference + runbook
• project_audreyinc_beta_foundation.md — the technical-infrastructure layer this sits underneath
• feedback_just_in_time_permission_grants.md — applies: decline D&B’s paid upsells unless a specific workflow demands them
• project_audrey_devreports_lifecycle.md — this report is the first instance of the lifecycle pattern (audrey-prefixed, incubating in dare’s catalog)