---
title: "Collect name, email, and phone on one step with the Contact Card"
description: "Add the Contact Card element to ask for all three contact details at once."
url: https://help.roasform.com/en/articles/56-collect-name-email-and-phone-on-one-step-with-the-contact-card
collection: "Form Builder"
updated: 2026-11-11
language: en
---

# Collect name, email, and phone on one step with the Contact Card

Add the Contact Card element to ask for all three contact details at once.

By default each question gets its own step, which is what makes ROASForm forms convert, but contact details are the one place where asking separately feels like a chore. The **Contact Card** puts name, email, and phone on a single step, as one item in your question list.

It takes a few seconds to add and you'll usually put it right before your ending.

## Add the Contact Card

1.  In the builder, click **\+ Add content**.
    
2.  Under **Contact info**, choose **Contact Card**.
    

![](https://staticfiles.gleap.io/p69cab0c4c0127a1b184858ea/wmppnT09Lt0LHlEg1kpUQGkwjisbaqARxwStw8IDUOOay237ZHivg5fnXYCIc6riVUOpGIa5MiZ.png)

**Contact Card**: name, email, and phone together on one step.

**Name**, **Email**, **Phone Number**, **Address**, **Website**: the same details as individual questions, one per step.

ROASForm creates the card with three fields:

<table data-id="c0ca20fb-d268-49d1-91ef-cceb6fa7e0ce" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p data-id="c29a00f4-28c3-44d7-b164-8456f95728fd"><strong>Field</strong></p></td><td colspan="1" rowspan="1"><p data-id="f05afccc-02e4-4fa8-8f98-0fea0005167f"><strong>Required</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p data-id="15bd75a9-e6ef-4a44-be48-b20015c360db"><strong>Name</strong></p></td><td colspan="1" rowspan="1"><p data-id="09d4b07b-b2ac-41e4-b611-27a4ced77d06">Optional</p></td></tr><tr><td colspan="1" rowspan="1"><p data-id="9d8a6dd8-1e36-471b-9cdd-333c8df49606"><strong>Email</strong></p></td><td colspan="1" rowspan="1"><p data-id="3c2e7460-6233-4350-bbeb-54a70f133ab1">Required</p></td></tr><tr><td colspan="1" rowspan="1"><p data-id="ffa1862e-2498-4115-ae86-bf62c0e4d3a9"><strong>Phone Number</strong></p></td><td colspan="1" rowspan="1"><p data-id="5d5ca573-99a7-45ff-b2fb-6707e854f64c">Optional</p></td></tr></tbody></table>

If GoHighLevel is connected on this subaccount, these three map to the contact's standard fields on their own. You don't need to set up field mapping for them.

## Good to know

**The card holds exactly those three fields.** You can't add a "business name" or "website" field inside the card. Add those as their own questions on the following step. **Website** is available in the same **Contact info** group, and **Short Text** covers the rest.

**It works on TypeSkin, Spektra Skin, and Calendar Skin with Horizontal flow.** On Chat Bot Skin, SmartSkin, and the Calendar Skin in Vertical flow you can't add it, and an existing card asks its fields one at a time. The labels in the builder are **Name**, **Email**, and **Phone Number**.

**One card per form is the normal setup.** Two Contact Cards means asking for an email twice, and the second answer is what syncs.

## Troubleshooting

**The browser offers to autofill a credit card on this step.** That's the browser, not the form. Browsers see a grouped name-and-phone block and sometimes guess it's a checkout. ROASForm never asks for payment details on a form and there's no card field to fill.

**You'd rather ask one at a time.** Use the individual **Name**, **Email**, and **Phone Number** elements instead. Each one becomes its own step, which usually means a higher completion rate on cold traffic and a slower form for people who are already sold.

**Email is rejected as invalid.** The Email field checks the format. If Email verification is on, it also refuses addresses that can't receive mail, and addresses on your Blocked List are refused too. If a real address is still refused, send us the exact address you typed.

## Related articles

-   [Question Types Overview](https://help.roasform.com/en/articles/30-question-types-overview.md)
    
-   [Mapping Form Answers to GoHighLevel Custom Fields](https://help.roasform.com/en/articles/22-mapping-form-answers-to-gohighlevel-custom-fields.md)
    
-   [Choosing a Form Skin](https://help.roasform.com/en/articles/41-choosing-a-form-skin.md)
