Overview
Capture Customer Info is one of the Web Flow templates within the Customer Profile category.
This Web Flow template has pre-configured components to collect the customer’s information. It can be used to build an application just as it is or it can be further tailored for a customized experience from Activity Builder.
Collect One Time Payment Web Flow template components
This Web Flow contains two Web Pages with the following components:
Contact Info Capture Form
- Label controls that tell users which information goes in the text inputs.
- Text inputs according to the following type of personal information:
- First Name
- Last Name
- Email Address
- Phone Number
- A Container that contains a Continue Button
- A Button that allows the user to continue.
Once users complete their information and clicks on the Continue button, the "Contact Info Captured" event is triggered .
Contact and Address Capture Form
- Label controls that tell users which information goes in the text inputs.
- Text inputs according to the following type of personal information:
- First Name
- Last Name
- Email Address
- Mobile Number
- Address
- City
- State
- Zip
- A Label control displaying an error message if the email given is invalid.
- A Label control displaying an error message if the phone number given is invalid.
- A Container that allows to visualize a Continue Button only after all the information is written
- A Button that allows the user to continue.
Once users complete their information and clicks on the Continue button, the "Contact Info Captured" event is triggered.
Inputs
The Capture Customer Info Web Page includes the following inputs that create only text type variable:
Contact Info Capture Form
Text
- first_name
- last_name
Phone
- phone
Contact and Address Capture Form
Text
- first_name
- last_name
- address
- city
- state
- zip
Phone
- phone
Events
Contact Info Captured
- Event Variables:
-
- firstName
- lastName
- phone
- address
- city
- state
- zip
This event is created as a web flow event and, in Journey Builder, an action or a node can be added to it to continue the application’s path.
Use Cases
Collect Customer information processed by a platform of your choice through a Journey.