If an AI built your venue list, check the email addresses before you send anything. Ours invented 13 out of 15.

On the morning of April 15, 2026, we fired 15 outreach emails for a small private dinner in the Portland–Vancouver metro. Thirteen of them hard-bounced. Every bounce carried the same timestamp: 9:27 a.m. Pacific.

The venues were not the problem. Most of those restaurants were real, open, and perfectly reachable. The addresses were the problem. Our own sourcing step had generated them — plausible-looking, correctly formatted, attached to domains that did not exist.

This is the post about the day we broke our own search. We are publishing it because the same failure is sitting inside a lot of venue lists right now, and the checks that catch it take about ninety seconds per venue.

The brief

A planner in the Portland–Vancouver metro needed a private dinner for 13 guests on Wednesday, April 29, 2026. Budget: $2,000 all-in. The request came in 14 days before the date.

The math that actually matters:

• $153.85 per guest, all in
• On a 3-hour dinner window (our assumption — the brief did not state one): $666 per hour, or $51 per guest per hour

That is workable in Portland for a private room with a menu-driven bill and no separate room fee. It is not workable against a food-and-beverage minimum. So the list skewed toward upscale restaurants with a private table or a small back room — the format where the whole budget goes into the meal.

9:27 a.m.: thirteen bounces, one minute

Fifteen emails went out. Thirteen came back as hard bounces — domain not found, or address invalid — all stamped within the same minute. That is an 87% failure rate on first contact, against a 25% threshold that is supposed to trigger an emergency re-source.

Hard bounces that fast are diagnostic. A real mailbox that is full, restricted, or retired usually takes longer and returns a different reason. A domain that has never existed fails instantly, because there is no mail server to ask.

Here is what the fabrications actually looked like, because the pattern is the useful part:

• Real venue, invented domain. The most common case, and the most dangerous. One address used a French-sounding variant of a real Portland restaurant’s name that the restaurant has never used. Another dropped the city suffix that the real domain actually carries. Both looked completely ordinary.
• Right name, wrong city. A seafood restaurant we listed as a Vancouver, Washington waterfront option is real — on the Oregon coast, roughly two hours from the dinner.
• Right name, wrong coast. We listed a culinary education center as a Portland cooking-class venue. It is real. It is at the New York Botanical Garden, in the Bronx, about 2,900 miles away.
• Venues that do not exist at all. Three of the fifteen — a Pearl District Spanish wine bar, a farm-to-table bistro on Division, and a waterfront steakhouse — have no counterpart in Portland under those names. They were assembled out of what a Portland restaurant sounds like.
• Real venue, closed. One had shut months earlier.
• Real venue, wrong size. One private room we flagged as a fit for 13 guests maxes out at four.

The tell we missed: one of the invented domains had a doubled letter in the middle of the venue’s own name. A typo inside a hallucination. Nobody caught it, because nobody was reading the addresses — they were reading the venue names, and the venue names looked great.

That is the whole trap. Fabricated contact data does not look wrong. It looks like contact data.

9:58 a.m.: the canary batch

The fix started by isolating the variable. We hand-copied three addresses off the venues’ own websites and sent the same brief to those three. Zero bounces. Fast bounces fire in two to three minutes, and nothing came back.

Then the replies started:

• 10:15 a.m. — Le Pigeon: no availability for a group that size on April 29, and no private event space. A clean, honest no, 17 minutes after send.
• 10:20 a.m. — Canard: “We need to discuss this with our chef and management team, and we will get back to you tomorrow afternoon.” A real answer in 22 minutes.
• Andina replied as well, with the date unavailable and a question about flexibility.

Three real addresses, three real answers, inside an hour. The Portland restaurant scene was responsive the entire time. We had just spent the morning emailing places that were not there. That tracks with what we see at scale: when venues do reply, about 7 in 10 replies land within a day.

2:45 p.m.: the rebuild

By mid-afternoon we had re-sourced the city from scratch under a stricter standard. Sixteen venues, all confirmed as real operating businesses against their own websites and map listings. Twelve had an email copied from a specific source URL and passed an MX check before anything was sent. Four had no published email at all and were routed to phone or web form — its own common problem, and one we have measured across 897 venues.

Eight names from the original list did not survive. The rejection reasons, verbatim from the record: closed in January. Maximum four guests. Does not exist in Portland. Cannot verify. Only exists in New York. Name and contact unverified.

The replacement list was better in every way that matters. It was also four hours too late.

4:25 p.m.: the part we do not get to explain away

Earlier that day, before any of this surfaced, the planner had received a confirmation email telling her how many venues we had contacted. That number was true as a count of emails sent. It was false as a count of venues reached. We told a customer we had done something we had substantially not done.

At 4:25 p.m. she cancelled. The message was seven words: “Please cancel my request for April 29.”

No reason given. We do not actually know whether the bounces cost us that booking — she may have booked direct, or the dinner may have moved, or a mass-email approach may simply have been the wrong shape for a 13-person dinner two weeks out. We are not going to claim a tidy cause. What we know is that we gave her a number that was not operationally true, and seven hours later the search was over.

What changed, permanently

The incident produced a written verification standard the same week. It is now a hard rule, not a preference:

1. Every contact email needs a source URL. Not a pattern, not a guess — a specific page on the venue’s own site where that address is published. If we cannot point at the page, the address does not get used.
2. Every address gets an MX check before send. A domain with no mail server is caught in milliseconds, for free, before anyone’s morning is wasted.
3. Never trust a generated address pattern. A guessed format is the single most reliable way to manufacture a bounce. Even when the pattern is right, the kind of mailbox you land on changes your odds enormously.
4. Confirm the venue exists, is open, and fits. Real business, current status, and a room that actually holds the headcount. Three of our fifteen failed the first test and one failed the third.
5. Send a small canary batch first. Three verified addresses, then wait three minutes. It costs nothing and it catches a broken list before it reaches scale.
6. A bounce rate above 25% stops the wave. It is a data failure, not a demand failure, and sending more of the same list makes it worse.

The slower version of the same failure

While verifying the listing links for this post, we found one of our own Portland pages pointing at Doug Fir Lounge — a genuinely beloved room that has been closed since 2023, mid-relocation, with reopening targeted for later this year. Our page still presented it as bookable, with a capacity and an average price. We pulled it from this post rather than link it.

Nobody fabricated that listing. It was accurate when it was written and the world moved. But to a planner clicking through, a stale listing and an invented one fail identically: both send a real email about a room you cannot have. Verification is not a step you pass once. It has a shelf life.

Portland options that are live right now

Every venue below is on VenueKonnex, and we re-checked each page and each venue’s current operating status while writing this. Average prices are what our listing data shows across past events — they are not a quote for your date, and a 13-top on a Wednesday will price very differently from a Saturday reception.

• Portland City Grill — 30th floor of the Bancorp Tower, private and semi-private dining rooms, up to 200 guests across 3,000 sq ft. Our page shows a $3,000 average — 150% of this planner’s entire budget — but that average is weighted by buyouts and large receptions, and a menu-driven 13-person private room is a different conversation. Closest match to what the brief needed.
• Pittock Mansion — historic home in the West Hills. $2,050 average, almost exactly this budget.
• Lan Su Chinese Garden — walled Ming-style garden in Old Town. $1,150 average, about 58% of budget, leaving room for catering.
• Oregon Historical Society — downtown on the Park Blocks. $850 average, the most headroom of the group.
• McMenamins White Eagle Saloon — North Portland saloon and hotel, up to 150 guests, $20 average per head. Verified operating with a live show calendar.
• Aladdin Theater — Southeast Portland, up to 500 guests, $35 average per head. Also verified against a current calendar.

How to check a list you did not build

If someone hands you a venue list — an assistant, a tool, an intern, us — four checks, under two minutes each: find the email on the venue’s own site rather than in the list; search the venue name plus the city and see whether it comes back in the right place at all; check map listings for a closure flag or an events calendar that stopped eighteen months ago; and read the capacity for your format, since seated dinner is not standing reception and a private room number is not the venue number.

FAQ

How much does a private dinner for 13 cost in Portland?
This brief worked at $2,000 all-in, or about $154 per guest — roughly $51 per guest per hour on a 3-hour window. At that level you are looking at a private room or reserved table inside a restaurant, with the budget going to food and beverage rather than a room rental. Dedicated event spaces in Portland run from about $850 to $3,000 for the space alone.

Why do so many venue outreach emails bounce?
Three reasons, in order of frequency: the address was guessed rather than found, the published address is a bare role alias that is unmonitored or restricted, or the venue publishes no email at all. The first is entirely preventable, and it is the one that caused this.

Can AI be trusted to build a venue list?
For discovery, yes — generating candidate venue names for a city and format is genuinely useful. For contact data, not without verification. A language model will produce a confident, well-formatted email address for a venue that does not exist, and there is no way to tell from looking at it. Verify against the source page every time.

What is an MX check and why does it matter?
It asks whether a domain has a mail server at all. It is instant and free, and it catches the entire class of failure described in this post before you send anything. If a domain has no mail server, no address at that domain can receive mail.

How far in advance should I book a private dinner?
Two weeks is tight but workable for a group of 13, because small private dining is the most flexible inventory in any city. In this case the venues that were reached responded in under half an hour. The delay was never the venues.

Where this leaves us

We lost a booking, published the reason, and rewrote the rules. Source URL, MX check, real-business confirmation, canary batch, hard stop at 25% — that standard now runs on every search we do. For the wider picture on what event space costs and how booking works, start with our 2026 event venue booking and cost guide.

Planning something in Portland or anywhere else? Tell us the date, the headcount, and the number, and we will do the verifying. Send us your brief — there is no charge to planners.

Run a venue? The single highest-return thing you can do is publish a real, monitored email address on your own website, and keep your listing current. Claim your venue listing so the details planners see are the ones you control.