Surveys

How Lead360 helps

Lead360 Surveys collects structured feedback across multiple questions or steps and stores the result for review and follow-up. Teams can design a focused experience, reduce response bias, and connect answers to the correct contact or business process.

When to use this area

Use Surveys for feedback, qualification, assessment, or research that needs more context than a short form.

Before you begin

• Define how each answer will be used.
• Remove unnecessary or leading questions.
• Map identity, consent, scoring, branching, and follow-up requirements.

Design slides and questions

1. State the audience and purpose, then arrange related questions in a logical slide order with an understandable progress flow.
2. Choose the correct response type: text, textarea, dropdown, checkbox, number, date, Multiple Choice, rating, or Yes or No.
3. Set options, required or hidden state, labels, help text, and contact or custom-field mapping only where the answer should update that record.

Configure behavior

1. Use query-string prefills only for approved values and avoid exposing sensitive data in URLs.
2. Keep mobile slides short, make consent clear, and set the visual style for readable contrast and controls.
3. Enter the full post-submit redirect. A Funnel step can use that survey redirect as its next destination.

Install and verify

1. Share the direct link or approved embed code.
2. Run a controlled desktop and mobile submission and verify validation, branch or slide progression, saved responses, contact mapping, completion state, redirect, and authorized reporting.

Use Ask360 here

Ask360 can explain the survey builder and prepare one reviewed create or update when supported. It waits for Accept and never infers a respondent answer, sends follow-up, exposes responses, or claims the survey works before a controlled submission.

Confirm the result

A completed Surveys workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Test every branch, required field, progress state, and completion path.
• Review stored answers and any calculated result.
• Confirm notifications and automations do not reveal sensitive responses to unauthorized users.

Troubleshooting

Respondents cannot complete a branch

Check conditional rules, required hidden questions, option values, and navigation after editing the survey.

Results look inconsistent

Compare question versions, scoring rules, incomplete responses, filters, and duplicate submissions.