How Rhazes decides what to do
Rhazes routes every message to the capability that fits it, sometimes to more than one, and asks when a request is ambiguous.
Updated
Routing
Before answering, Rhazes works out what you are actually asking for and sends the message to the capability that fits: a question to answer, a document to write, codes to assign, a plan to build, a presentation to make, or a task to file.
Selecting a quick action yourself is the explicit version of this. Left alone, Rhazes decides. See Quick actions.
One message, several outputs
Some capabilities can run more than once from a single message. Documents, presentations and coding are all like this, so "write me a discharge summary and a referral letter" produces both rather than making you ask twice.
Others run once per message by design. A differential, an assessment and plan, or a management question each resolve to one answer.
When it asks instead
If the request genuinely could go more than one way, Rhazes asks rather than guessing.
It knows your saved templates and PDF forms by name when it decides, so asking for something by its template name is understood rather than treated as an ambiguous fragment.
When it declines
Some requests are outside what Rhazes will do. See When Rhazes declines a request.