Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that…

The Identify field should use the built-in Number entity (which already recognises ages such as “23”) so the bot receives an integer it can branch on (≤17, 18-25, etc.). The Date and time entity returns a full date/time value; Power Virtual Agents cannot directly calculate the customer’s age from that value without calling an external flow, so the required age-group logic would fail. Therefore the proposed solution does not meet the goal.

A. Yes – Choosing Date and time would capture a birth date, not an age; PVA lacks native date-difference calculation, so conditional branches cannot directly evaluate the five age ranges.

1. Microsoft Learn

“Use built-in entities in Power Virtual Agents” – section “number” (recognises ages). https://learn.microsoft.com/power-virtual-agents/advanced-entities

2. Microsoft Learn

“Add branching logic in a topic” – shows numeric comparisons using integer variables (no date-difference function). https://learn.microsoft.com/power-virtual-agents/branching

3. Microsoft Learn

“System entities: datetime” – returns date/time value without age calculation. https://learn.microsoft.com/power-virtual-agents/advanced-entities#datetime