Check the customer's actual need

Read the conversation before contacting the lead. Separate a buying enquiry from a support problem, and check which product, quantity, or service was discussed. Missing information is a reason to ask a focused question, not to assume purchase intent.

Keep your process consistent

Use the lead status controls available in your workspace to distinguish open enquiries from completed follow-ups. Check repeated submissions before contacting the same person several times. Store only the notes your team needs and avoid unnecessary sensitive information.

If a test lead is missing

Check the package entitlement, widget lead settings, and whether the visitor completed the form. A conversation alone does not necessarily create a lead. Include the approximate test time and widget reference when contacting support, with contact details redacted where possible.

A note on availability

Dashboard labels may currently be in German. Available controls and modules depend on your package and release. If a control described here is missing, check your workspace or contact support.