Skip to content

Forms and chatbox

How to prepare a lead form with fewer fields and clearer follow-up

A form should capture an inquiry and guide it to the right next step, not collect every possible detail. Unnecessary fields make completion harder.

Maptinger · Content updated:

Choose fields needed for a first response

A starting point for a demo request: name, a reply address and “What task would you like to make easier?” Avoid requiring company size, budget or phone at the first step unless the answer is needed to handle the inquiry. Adapt this synthetic field outline to your response process. Do not request identity or bank details; use visible labels, clear errors and a natural mobile keyboard order.

Connect submissions to durable records

When a person submits a second form, preserve their identity and submission history rather than creating duplicates. A demo request and a quote request may be different inquiries from the same person. One identity does not mean discarding those separate requests.

Keep inquiries and permission decisions distinct

A submission provides context for answering an inquiry; it is not automatic permission for every campaign. Workflows tied to submissions require explicit activation. Keep acknowledgements, marketing audience membership and human review as separate decisions.

Common mistakes

  • Treating every submission as marketing permission
  • Creating a new person for each list

How to approach this in Maptinger

Choose the fields needed for your inquiry in Forms and inspect the mobile preview. Check publishing and embedding permissions, then review how a sample submission reaches its record. A form does not activate WhatsApp or a marketing workflow.

The user WhatsApp channel is disabled; forms or chatbox do not unlock it. Publishing and connection permissions are separate.

Related topics

How to prepare a lead form with fewer fields and clearer follow-up — Maptinger