The card you collect without holding
A deposit confirms a booking. A card on file makes the next invoice one click instead of a phone call. But the moment a form asks for card details, you're standing inside a compliance question most small teams would rather not own.
The new Credit Card element sidesteps that entirely. Card entry runs through Stripe on your own connected account, so the platform never touches the number — only an opaque reference and the brand and last four ever come back. Set it to save a card on file, or to take a deposit for a set amount. The form does the asking; Stripe does the holding; your books stay clean.
The "when are you free" no form usually asks
The other gap is timing. A service request tells you what someone wants, then leaves the scheduling to a round of phone tag.
The new Schedule element lets the visitor answer the question up front: tap "as soon as possible," or pick the days and the windows — morning, afternoon, evening — that work for them, with room for a note. It arrives on the submission as plain availability you can book against, so the first call is "here's a time," not "when are you around?"
Two elements, one pattern
Both drop onto a form the same way every other element does — drag, configure, publish — and both render on your own site and on a customer's domain through the SDK. No new tool to learn, no separate page to send people to. The card and the calendar live inside the form they already started.
A booking that holds a deposit. An intake that already knows when to call. The work that used to happen after the form now happens inside it.
See the form builder → · Try Business Dash →
Related: how a form can book the meeting itself.