EST. NEW YORK · COMMUNITY · STORIES

Articles on community programs, technology, and travel — gathered under one roof.

Warm sandy-brown textured background with subtle highlights and shadows, conveying an earthy, archival mood.
Home » Welcome

Welcome to Cordnewyork

Cordnewyork is the home page of CORD New York, a community organization based in New York. The site also collects short articles and updates spanning technology, lifestyle, and travel. Use the menu on the left to jump to specific sections, or scroll down for the latest posts.

Within these pages you will find notes on CORD NYC's past events, profiles of the Leadership Advisory Board, and a growing archive of newsroom-style features published under the Cordnewyork byline.


Five Things You'll Find Here

  1. WordPress-powered news and notes from the CORD NYC desk.
  2. An events archive covering community activities in and around New York.
  3. Profiles of the Leadership Advisory Board members who guide the organization.
  4. Reports on the impact of community projects, including food drives and walkathons.
  5. Reader-friendly technology and travel write-ups, refreshed on a rolling basis.

Why Siri cannot choose between multiple emails for one contact

The question of why Siri cannot use a contact's email address to send an email when the contact has multiple emails usually comes down to recipient disambiguation, the process of matching a spoken request to one stored address. It is rarely a simple refusal to send email.

On iPhone and iPad, one contact card can contain personal, work, school and shared addresses. Siri must interpret the command, locate the person and choose a valid recipient before Mail can begin a message. A failure at any of those stages can look like the same “cannot email contact” error.

How Siri parses a spoken email request

Siri's natural language processing first turns speech into an intent such as sending an email, then extracts entities including the recipient, address and subject. “Email Michael about the quote” is recognisable, but it identifies only a person unless one address can be selected confidently.

That confidence depends on labels, prior conversation and the contact record. A related example is stale listening history, where Siri uses old preferences to select a song. Voice assistants can apply familiar context confidently even when that context does not match the user's present request.

Why several contact emails cause ambiguity

A card containing michael@example.com and michael@studio.com.au gives Siri two plausible targets. This is one person with several routes, not a request to send copies to everyone. Unless you say “work”, “home” or the exact address, it may ask a clarifying question, choose the first entry or fail to populate the recipient field.

The situation is common in Australia. Sydney and Melbourne small businesses often combine Microsoft 365, Google Workspace and personal Gmail accounts, while shared family or studio mailboxes sit alongside staff addresses. Even a useful label may not indicate which inbox you mean.

“Contact me on my work email” can work when those labels survive syncing. The real trouble starts when both addresses have no label, the label is generic, or the card you see on one device differs from the one Siri reads.

How contact syncing changes the result

Apple devices can merge contacts from iCloud, Google and Exchange. Each service may contribute a separate card or a separate email field, producing duplicates such as “Michael Smith”, “Michael S.” and “Michael (work)” for the same person. Siri may resolve whichever record is currently indexed, even if a more complete card exists nearby.

Device routing adds another variable. An Australian household may use an iPhone during the day and a HomePod or iPad in the evening; a command heard by one device can be passed to another for processing. The receiving device's account, contact permissions and cached records then influence which address appears.

When connectivity matters and when it does not

A connection is required for final delivery and often needed for account lookup and contact refresh, so a dropped service can block a valid request. Train commutes in Sydney and Melbourne also pass through mobile coverage black spots, making an occasional Siri failure look like a contact problem.

However, choosing between several addresses normally fails before email transmission. If the recipient is already selected and a network error follows, Mail may show an offline or server message. Character-level parsing can also fail earlier, as percent-sign search commands demonstrates, but that is separate from an ambiguous contact.

The useful distinction is simple: a connectivity error concerns getting the request or message moving, while a disambiguation error concerns knowing which recipient you chose. Diagnosing the stage prevents unnecessary troubleshooting of the wrong system.

How Australian speech habits affect commands

Australian English speakers often rely on conversational shortcuts: “Email Sarah about the invoice” or “Send Ben the contract”. These work well with people who know the context, but a voice assistant receives the shortened command without knowing which Sarah or Ben is intended.

Accent, microphone quality and surrounding noise can worsen entity extraction, while punctuation-heavy domains challenge it further. The same sensitivity appears with song titles with symbols, where numerals and characters can be misheard or dropped. Longer explicit wording reduces reliance on inference.

Checks that isolate the cause

Start with the contact card, because it is where several plausible recipients become visible.

  • Open the intended card and check every stored email address.
  • Assign clear labels such as mobile, personal, work and shared studio.
  • Search for surname plus suburb or postcode to find duplicate cards.
  • Confirm the card is visible to the account that Siri and Mail use.

Then test the command itself without changing unrelated settings.

  • Include the full recipient address in the spoken request.
  • Say the label, such as “my personal address”, when it is distinctive.
  • Check which device handled the request if several Apple devices are nearby.
  • Open Mail manually to confirm the intended recipient before sending urgent mail.

If the exact address works but “Email Sarah” does not, the contact data or recipient-selection logic is the likely fault. If neither works, check iCloud, account access, device routing and network status.

Make the next request count

Future improvements should make Siri state the chosen address, ask for clarification when confidence is low and carry the selection into the Mail composer. Better contact ranking, clearer account boundaries and more reliable device handoff would help without pretending every contact has one permanent email.

Until those improvements arrive, direct wording remains the dependable path. Open the relevant contact now, remove duplicates, label each address accurately and make your next request with the intended address stated clearly.


Need a Hand Navigating?

If you are looking for something specific, the left-hand menu leads you to the main sections: About Us, Join Us, Past Events in New York, Impact of CORD, and the CORD NY Leadership page. The Donate page is the place to support the organization financially.


Ask a Question

Use the form below to send a note to the editorial team. We read every message.


What Readers Say

★ ★ ★ ★ ★

The events archive is the easiest way to follow what CORD NYC has been doing over the years. Clean and to the point.

— Recent visitor
★ ★ ★ ★ ☆

I appreciate having the leadership profiles alongside the community news. It keeps the people behind the work visible.

— Site reader
★ ★ ★ ★ ★

The technology and travel write-ups are a nice surprise on a community-focused site.

— Subscriber