DO ONE THING WELL
CRM Prefill: Plan the Right Data
Listen to this guide
English narration. Duration shown in the player.
Read the narration transcript
Prefill means placing approved existing information into a form before the respondent starts. A volunteer renewal, for example, could begin with a name and email already entered. The respondent can review that information instead of typing every answer again.
First confirm that your connector and form workflow support the intended kind of prefill. A working CRM connection or a record lookup does not, by itself, provide a secure respondent-facing form. This lesson explains the decisions needed before that workflow is used.
Decide how the workflow will identify the record and confirm that the respondent is allowed to view it. Do not rely on a person's name alone. Define what happens when no record is found or several records could match.
Create a small allowance of fields for the form. Names and approved contact details may be appropriate for a renewal. Private notes, internal ratings, and unrelated CRM information do not belong there. Check that each visible value has a clear purpose.
Use the approved access mechanism for your implementation. CRM credentials must remain on the server. Avoid putting sensitive information directly into a link. Where a secure link is supported, confirm its expiry and access rules, and understand what happens if someone forwards it.
Decide which values the respondent may edit and which should remain fixed. Explain what will be saved when the form is submitted. Consider stale information and empty fields. Prefilled values still need appropriate review and validation.
Loading information into a form does not automatically update the CRM. Write-back needs its own approved mapping and record action. In a test environment, review the displayed values, submit a deliberate change, and verify the correct destination record when write-back is supported.
Your next step is to list who may open the form, which fields may appear, and what should happen after submission. Confirm those requirements against the capabilities available in your account. Use the written guide as your prefill planning checklist.
Watch the narrated slides
Music: A Kind Of Hope by Scott Buckley, licensed under CC BY 4.0. Edited for length, fades and background level.
Understand what prefill does, which fields to expose, and how to separate loading data from writing it back.
Reduce repeat typing
Prefill means placing approved existing information into a form before the respondent starts. A volunteer renewal, for example, could begin with a name and email already entered. The respondent can review that information instead of typing every answer again.
- Identify the correct person
- Load only approved fields
- Let the respondent review the values
Confirm the actual capability
First confirm that your connector and form workflow support the intended kind of prefill. A working CRM connection or a record lookup does not, by itself, provide a secure respondent-facing form. This lesson explains the decisions needed before that workflow is used.
- Check the selected connector
- Check the form delivery method
- Use only an available, verified workflow
Identify the intended record
Decide how the workflow will identify the record and confirm that the respondent is allowed to view it. Do not rely on a person's name alone. Define what happens when no record is found or several records could match.
- Use an approved identifier
- Confirm who may view the record
- Handle a missing or ambiguous match
Choose a small field allowance
Create a small allowance of fields for the form. Names and approved contact details may be appropriate for a renewal. Private notes, internal ratings, and unrelated CRM information do not belong there. Check that each visible value has a clear purpose.
- Include: first name and last name
- Include: approved contact details
- Exclude: private notes and internal ratings
Keep access controlled
Use the approved access mechanism for your implementation. CRM credentials must remain on the server. Avoid putting sensitive information directly into a link. Where a secure link is supported, confirm its expiry and access rules, and understand what happens if someone forwards it.
- Keep CRM credentials on the server
- Avoid sensitive data in the URL
- Apply expiry or access checks as required
Decide what the respondent can change
Decide which values the respondent may edit and which should remain fixed. Explain what will be saved when the form is submitted. Consider stale information and empty fields. Prefilled values still need appropriate review and validation.
- Separate editable and fixed fields
- Explain what will be saved
- Check stale and empty values
Treat write-back as another action
Loading information into a form does not automatically update the CRM. Write-back needs its own approved mapping and record action. In a test environment, review the displayed values, submit a deliberate change, and verify the correct destination record when write-back is supported.
- Define a separate mapping
- Choose the write action
- Verify the destination after testing
Your next step
Your next step is to list who may open the form, which fields may appear, and what should happen after submission. Confirm those requirements against the capabilities available in your account. Use the written guide as your prefill planning checklist.
- Who may open the form?
- Which fields may appear?
- What happens after submission?
Examples illustrate decisions and do not report a completed CRM transaction.