An agent action that lists available appointment slots keeps surfacing openings at hospitals across the whole region instead of the owner's home clinic, confusing pet owners who only want their local branch. Which configuration change most directly fixes this?
Select an answer to reveal the explanation.
Short Explanation
If the search itself hands back every clinic in the region, no amount of polite summarising fixes that at the end. Filter the well before you draw from it, don't ask the model to pretend half the bucket isn't there.
Full Explanation
The action's data source is returning too broad a record set, so the correct fix operates at that layer: a filter on the action restricts which Appointment records are eligible to be returned in the first place, based on the owner's home clinic. This is deterministic and guarantees the model never even sees out-of-scope options to summarise. Telling the model via instruction to mention only local results is unreliable because the underlying data still contains region-wide rows, and a model asked to selectively ignore visible data will do so inconsistently, especially as conversations get longer. Rewriting the classification description addresses which topic gets selected for a given utterance, not what data an already-selected action returns, so it does not touch this problem at all. Moving the action to a Sales agent conflates agent type with data scoping; agent type governs role and available standard capabilities, not per-action record filtering, and it would not make regional results become local. The broader principle: whenever an action is returning more than it should, look first at whether its data source can be filtered before reaching for instruction-level workarounds.