Some products and features are in the process of being renamed. Generative playbook and flow features are also being migrated to a single consolidated console. See the details.
The following sample dialogs demonstrate common scenarios handled by this
prebuilt component. The sample dialogs demonstrate behavior when the component is
called via telephony, which triggers the Default Welcome Intent and the first
agent response at the start of the conversation.
Full date of birth
End-user provides complete date of birth in one turn; agent successfully accepts it.
User input
Agent response
Please provide your date of birth. Please say your birth month, followed by your birth day, and then your birth year.
September 9th 1995
Okay, your birthdate is September 9, 1995. Is that correct?
yes
Great, I've collected your birthdate.
Partial date of birth
End-user provides date of birth by saying month first followed by date and year;
agent successfully accepts it.
User input
Agent response
Please provide your date of birth. Please say your birth month, followed by your birth day, and then your birth year.
March
What day were you born on?
12
What year were you born in?
1999
Okay, your birthdate is March 12, 1999. Is that correct?
yes
Great, I've collected your birthdate.
Future date validation
This scenario assumes the current date is March 22, 2023. End-user provides a
future date of birth; agent validates it and re-prompts end-user to provide the
correct date of birth.
User input
Agent response
Please provide your date of birth. Please say your birth month, followed by your birth day, and then your birth year.
September 9th 2023
What year were you born in?
2023
Okay, your birthdate is September 9, 2023. Is that correct?
yes
Sorry, you have provided a future date. Let's start again. Which month were you born in?
March
What day were you born on?
12
What year were you born in?
1999
Okay, your birthdate is March 12, 1999. Is that correct?
yes
Great, I've collected your birthdate.
Invalid date
End-user provides an invalid date of birth such as February 30th 1999 or April
31st 1999; agent validates it and re-prompts end-user to provide the correct
date of birth.
User input
Agent response
Please provide your date of birth. Please say your birth month, followed by your birth day, and then your birth year.
February 30th 1999
Okay, your birthdate is February 30, 1999. Is that correct?
yes
The date you have provided is invalid. Let's start again. Which month were you born in?
March
What day were you born on?
12
What year were you born in?
1999
Okay, your birthdate is March 12,1999. Is that correct?
yes
Great, I've collected your birthdate.
Unrecognized input
Component exits the flow after the end-user provides unrecognized input three times.
User input
Agent response
Please provide your date of birth. Please say your birth month, followed by your birth day, and then your birth year.
It's fine
Sorry, I didn't get that. Can you please say or enter your date of birth again?
nice
Sorry I did not get your date of birth. Let's start with month. Please say which month were you born in?
good
Sorry, I didn't get that. Can you please say or enter the month number again?
nice
Hmm, I still wasn't able to get that. Please make sure you're saying the month. If I am having trouble hearing you, you can also use the keypad to enter the month number.
nice
Sorry, I'm having difficulty understanding your response.
Date of birth validation
This prebuilt component uses the IS_DATE
and IS_FUTURE_DATE system functions to
check whether a collected date is valid and in the past. In addition:
Inputs such as "this month", "next month" or "last month" are converted into the appropriate months. For example, if the end-user is interacting with the agent in March, then "this month", "next month" and "last month" are converted into "March", "April" and "February" respectively.
Validates that the year should be four digits. If the year input contains only two digits, the component converts it into a four-digit year. For example, "98" is converted to "1998".
Input such as "this Thursday", "last Thursday", and "next Thursday" are captured as the appropriate month and day and the agent prompts to provide the year. For example, if end-user is interacting with the agent on March 22, 2023, which is a Wednesday, then "this Thursday", "last Thursday", and "next Thursday" are converted into "March 23", "March 16", and "March 30" respectively.
Naming conventions
This prebuilt component uses the following naming conventions:
Output parameters are session parameters that will remain active after exiting
the component. These parameters contain important information collected by the
component. This prebuilt component provides values for the following output
parameters:
Parameter Name
Description
Output Format
dob_collection_dob
This parameter returns an object containing date of birth elements: day, month and year
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis prebuilt component is designed to collect and validate a user's date of birth, including the month, day, and year.\u003c/p\u003e\n"],["\u003cp\u003eThe component can handle complete or partial date inputs, as well as future or invalid dates, by re-prompting the user for correct information.\u003c/p\u003e\n"],["\u003cp\u003eIt utilizes system functions \u003ccode\u003eIS_DATE\u003c/code\u003e and \u003ccode\u003eIS_FUTURE_DATE\u003c/code\u003e to ensure date validity and checks that the date is in the past.\u003c/p\u003e\n"],["\u003cp\u003eThe prebuilt component is limited in that it does not offer ID verification to verify the user's date of birth, and uses specific naming conventions for flows, intents, parameters and entity types.\u003c/p\u003e\n"],["\u003cp\u003eThe component provides a \u003ccode\u003edob_collection_dob\u003c/code\u003e output parameter containing an object with the collected day, month, and year, and also offers repeat, waiting room, and playback functionalities.\u003c/p\u003e\n"]]],[],null,["# Date of birth collection prebuilt component\n\nThis\n[prebuilt component](/dialogflow/cx/docs/concept/prebuilt-component)\ncaptures and validates a date of birth by collecting month, date, and year.\n\nLimitations\n-----------\n\nIn addition to the\n[common prebuilt component limitations](/dialogflow/cx/docs/concept/prebuilt-component#limits),\nthis prebuilt component has the following limitations:\n\n- This component does not support verification of end-user's date of birth via ID verification.\n\nRecommended agent settings\n--------------------------\n\n[Enable DTMF](/dialogflow/cx/docs/concept/parameter#dtmf) to allow users to input numeric values using the telephone keypad.\n\nAdditional functionalities\n--------------------------\n\nThe following additional functionalities are provided by this prebuilt component:\n\n- [Repeat](/dialogflow/cx/docs/concept/prebuilt-component#repeat-functionality)\n- [Waiting room](/dialogflow/cx/docs/concept/prebuilt-component#waiting-room-functionality)\n- [Playback](/dialogflow/cx/docs/concept/prebuilt-component#playback-functionality)\n\nSample dialogs\n--------------\n\nThe following sample dialogs demonstrate common scenarios handled by this\nprebuilt component. The sample dialogs demonstrate behavior when the component is\ncalled via telephony, which triggers the Default Welcome Intent and the first\nagent response at the start of the conversation.\n\n### Full date of birth\n\nEnd-user provides complete date of birth in one turn; agent successfully accepts it.\n\n### Partial date of birth\n\nEnd-user provides date of birth by saying month first followed by date and year;\nagent successfully accepts it.\n\n### Future date validation\n\nThis scenario assumes the current date is March 22, 2023. End-user provides a\nfuture date of birth; agent validates it and re-prompts end-user to provide the\ncorrect date of birth.\n\n### Invalid date\n\nEnd-user provides an invalid date of birth such as February 30th 1999 or April\n31st 1999; agent validates it and re-prompts end-user to provide the correct\ndate of birth.\n\n### Unrecognized input\n\nComponent exits the flow after the end-user provides unrecognized input three times.\n\nDate of birth validation\n------------------------\n\nThis prebuilt component uses the [IS_DATE](/dialogflow/cx/docs/reference/system-functions#func-isdate)\nand [IS_FUTURE_DATE](/dialogflow/cx/docs/reference/system-functions#func-isfuturedate) system functions to\ncheck whether a collected date is valid and in the past. In addition:\n\n- Inputs such as \"this month\", \"next month\" or \"last month\" are converted into the appropriate months. For example, if the end-user is interacting with the agent in March, then \"this month\", \"next month\" and \"last month\" are converted into \"March\", \"April\" and \"February\" respectively.\n- Validates that the year should be four digits. If the year input contains only two digits, the component converts it into a four-digit year. For example, \"98\" is converted to \"1998\".\n- Input such as \"this Thursday\", \"last Thursday\", and \"next Thursday\" are captured as the appropriate month and day and the agent prompts to provide the year. For example, if end-user is interacting with the agent on March 22, 2023, which is a Wednesday, then \"this Thursday\", \"last Thursday\", and \"next Thursday\" are converted into \"March 23\", \"March 16\", and \"March 30\" respectively.\n\nNaming conventions\n------------------\n\nThis prebuilt component uses the following naming conventions:\n\nOutput parameters\n-----------------\n\nOutput parameters are session parameters that will remain active after exiting\nthe component. These parameters contain important information collected by the\ncomponent. This prebuilt component provides values for the following output\nparameters:\n\nBasic setup\n-----------\n\nTo set up this prebuilt component:\n\n1. [Import the prebuilt component](/dialogflow/cx/docs/concept/prebuilt-component#import).\n\n### Complete\n\nYour agent and should now be set up and ready to test."]]