Siri, their and there in a shortcut name

In Sydney, a commuter on a crowded train might say, “Hey Siri, archive their receipts,” expecting a shortcut to file documents. In a quiet flat, “their” can sound exactly like “there”, so Siri may receive different text from the one intended.

How Siri handles a command that contains a homophone like “their” and “there” in a shortcut name depends on where recognition ends and interpretation begins. Speech-to-text creates a transcript; language models infer intent; Siri then looks for a matching shortcut title.

Any weak link can break the chain. A microphone may miss a consonant, a congested mobile network may delay processing, and a nearby HomePod or paired iPhone may capture different audio. The shortcut can also fail after recognition if it needs missing input.

None of this proves that Siri ignores grammar. It shows why identical sounds do not guarantee identical results. Clear naming, deliberate user habits and better confidence handling can make the difference.

Why the words become ambiguous

Australian English does not remove the collision: “their” and “there” are near-homophones in most accents, including Sydney and Melbourne speech. Context helps—“archive their receipts” wants a possessive, while “put it there” asks for a location—but the waveform may be the same.

A shortcut name adds another complication. If one title is “Archive Their Receipts”, a transcript of “archive there receipts” may not match it exactly. Siri may select another title, ask for clarification, or treat the request as ordinary dictation rather than a named automation.

From spoken words to a launched shortcut

The likely sequence is wake-word detection, transcription, intent analysis, title matching, shortcut launch and parameter handling. Failure can occur at any stage, and the visible symptom may be identical: “Siri didn’t find that shortcut.”

That message should not be confused with the empty-string shortcut failure, where the spoken wording may be right but an action receives no usable value. Homophone confusion happens earlier, in the words used to identify the shortcut.

Some versions of Shortcuts also expose alternate phrases or aliases. These can help when a title is awkward, but an alias that differs only by a homophone may simply create another candidate. Testing on each device used is safer than assuming one alias will behave consistently.

Devices and networks change the outcome

Hardware changes the input. An iPhone held near a noisy Melbourne laneway café, an Apple Watch on a wrist, a HomePod across a room and a Mac beside a Canberra desk all present different microphones, wake settings and acoustic conditions.

Processing may also be divided between the device and Apple’s network. A drop from Telstra or Optus service inside a Sydney station can leave a wake phrase heard but the request unfinished, while a home broadband connection usually behaves differently. On non-Apple systems, an XFCE panel alternative dock can organise a useful Linux workspace, but it does not add access to private iOS Shortcuts actions.

Australian speech and everyday habits

Communication habits matter as much as accents. Australians often shorten requests—“run that one” rather than the complete title—and rely on context established by a previous question. That works well in conversation, but a shortcut catalogue has no way to infer an unstated destination with certainty.

Deictic words such as “there” are common in spoken instructions, while possessives such as “their” carry different meaning. Siri’s language model can use surrounding words to favour one interpretation, yet the selected shortcut name remains a hard target. Silence, slang and fast speech further reduce useful context.

A practical checklist for dependable shortcuts

A dependable shortcut should sound distinctive before it needs debugging. These changes reduce collisions and make failures easier to diagnose:

• Rename the shortcut with a concrete verb and a distinctive noun phrase.
• Avoid titles whose useful version depends on “their” or “there”.
• Speak the full title after the wake phrase, with a short pause.
• Test every alias on each iPhone, iPad, Mac and HomePod used.
• Validate required variables before the automation performs a destructive action.

Keep a harmless test action, such as reading a note or adding a draft, rather than testing with deleted files. Record the spoken wording, displayed transcript and outcome after each run; repeated failures then reveal whether the problem is acoustic, linguistic or operational.

Where Siri can become more reliable

Better user understanding would let Siri weight several signals together: the transcript, recent dialogue, the installed shortcut catalogue and the confidence attached to individual words. A clearer prompt such as “Did you mean Archive Their Receipts?” would be more useful than silently opening the wrong automation.

Future systems could also learn a household’s preferred phrasing, preserve useful context between devices and offer an offline fallback. They should distinguish an uncertain title match from an empty input, explain the problem briefly and avoid retrying an action that may already have run.

Run a controlled shortcut test

Run one controlled comparison before trusting the shortcut. Use a harmless action, capture the transcript and timing in a reproduction note, and repeat it in a quiet room, on a busy street and over mobile data. Include one run with every required variable supplied.

Aspect	Typical failure	More resilient behaviour
Recognition	“their” transcribed as “there”	Retain alternate transcripts and confidence
Matching	Wrong or no shortcut selected	Offer a close title or request clarification
Parameters	Required input is empty	Identify the missing value before acting
Device continuity	Another device captures the request	Pass the command to the intended device

Interpret the results separately. A wrong transcript points towards acoustics or language recognition; a correct transcript with the wrong shortcut points towards title matching; and a correct launch with no result points towards variables or the action itself. This separation prevents unnecessary redesign.

Create the harmless test shortcut today, run the same wording in your Australian home, café and commute, then keep the version that stays reliable across Wi-Fi, 5G and every device you use.