Can one tag carry more than one action?
Not in the way people expect. Writing several action records does not give the user a choice, because no platform presents a menu: it picks one. Several outcomes from a single tap are achieved behind the tag, on a page or in an automation, rather than on it.
Why stacking records does not work
A tag holding a URL, a phone number and an email address does not offer three options. The platform walks the records, acts on the first it recognises, and ignores the rest.
Which one it picks depends on the platform and on the order you happened to write them in. The result is a tag that appears to offer choice and delivers whichever outcome the system chose, differently on different phones.
This is the single most common misunderstanding about writing tags, and it survives because the records are all genuinely there when you read the tag back.
The landing page pattern
Put a URL on the tag and the choices on the page it opens.
A page with three large buttons, call, email, directions, gives the user a real choice, works identically on every phone, and can be changed at any time without touching a single tag. It also lets you add a fourth option later.
The cost is a network connection. Where coverage is uncertain, this is a genuine problem and the honest answer is that no arrangement gives you both offline operation and multiple choices.
The automation pattern
For personal use, the tag triggers a routine and the routine does several things.
One tap turning on a light, setting a mode and starting a timer is a single action from the tag's point of view. The multiplicity lives in the automation, where it can be edited from an armchair rather than by rewriting the tag.
This is why a personal tag should hold as little as possible: an identifier the automation recognises, and nothing else.
Making one tag behave differently
The same tag can produce different outcomes if the decision is made at the server.
Time of day, how many times it has been tapped, or which page the visitor came from can all change what the link returns. The tag never changes and its behaviour does.
What cannot be done is having the tag itself decide. A tag is memory, not logic: it hands over the same bytes every time, to everyone, and every clever behaviour lives somewhere else.
Frequently asked questions
Will the phone ask me which record to use?
No. Neither platform presents a menu of records, so extra action records are not options, they are candidates the system did not choose.
So why write more than one record at all?
As a fallback, where a second record covers the case of the first being ignored on some platform. That is a different purpose from offering a choice.
Can a tag do something different on a second tap?
Not by itself. Some chips include a counter that increments on read, and using it requires software that reads the counter and decides, which means the logic is again not on the tag.
Is there any way to get two actions offline?
Not from one tap. Two separate tags in two places is the workable offline answer, with each holding one thing and the placement making the choice.