← Help Center
Surveys & discoveryGUIDE

Branding, and answers that update your records

How the response page looks, and how an answer can correct a contact record.

The response page carries your letterhead

A questionnaire either inherits your workspace letterhead, carries its own, or shows a bare page — set it per questionnaire. Branding is resolved when the page loads rather than frozen when the questionnaire was created, so updating your logo in Settings → Workspace updates every questionnaire already sitting in somebody's inbox. (Documents work the opposite way on purpose: a signed contract has to keep the branding it was signed under.)

Long questionnaires stay navigable

Turn on the pinned header and the letterhead, title and progress bar stay at the top as the respondent scrolls, so they can always see how much is left. It is off by default, because on a five-question survey it is just clutter.

Answers save as they go

Anyone on a per-person link can close the page and come back to it. Their answers are saved as they type, the page tells them so, and the same link picks up where they stopped — including after a reminder. This is what makes a long discovery questionnaire realistic to send to a busy executive.

Writing answers back to the CRM

A survey is one of the few moments a customer volunteers correct information about themselves. Any question can be pointed at a contact or company field — including your custom fields — so the answer updates the record instead of sitting only in a response. This is off until you turn it on, per questionnaire.

Trust follows the link

  • A per-person link names exactly one contact, and the respondent is that person. They are allowed to correct a value that is already wrong.
  • The public link is the same questionnaire in anybody's hands. By default it fills blanks and stops there — it will not overwrite something you already know.

Nothing changes silently

Every write-back is recorded as an activity on the record's timeline naming the old value and the new one. That is what makes a bad answer visible, and reversible by hand.

Still need a hand?
Check system status, report a bug, or message the team.