Book a demo
Menu

Glossary

Write plan

A write plan is the preview of a pending CRM write, listing every create and update, field by field, against a match key before a person authorizes it.

It shows you the full effect of a write before your CRM changes. Tools that use one make it the review step of CRM write-back.

What does a write plan show you?

  • Operations: create contact, link an existing company, fill blank company fields, update contact fields, capture a note, record event attendance.
  • Values: each field’s current CRM value next to the value to send. For contacts and companies, FieldXM fills blank fields only.
  • The match: the match key that matched the record, such as email.
  • What stays out: anything blocked, with the reason, such as a missing CRM field.

Why does it matter to your CRM admin?

Your CRM belongs to the team that runs it, often RevOps, and that team pays for a bad write. A write plan gives them each change and the match behind it to inspect at write time. Then a person makes the call in a named commit.

How does FieldXM write to your CRM?

Each lead your reps capture goes to HubSpot or Salesforce with the conversation attached. Your declared match keys decide create or update, so FieldXM updates a contact you already have in place, and FieldXM leaves every filled field on your contacts and companies as it found it.

Meetings your reps book at the booth go straight into your CRM, tied to the show. When FieldXM reads from your CRM, it changes nothing. Changes you ask of Ask FieldXM run under your team’s approval gate: ask first, draft for approval, or act and tell you. See what FieldXM writes to your CRM.

Related terms

  • CRM write-backCRM write-back is the outbound half of a CRM integration, the step where a connected tool creates or updates CRM records such as contacts, companies, notes, and event attendance.
  • Named commitA named commit is an approval step some CRM write-back tools use, where an identified person authorizes a previewed delivery so each change traces to a decision.
  • Match keysMatch keys are the fields an integration compares to decide whether an incoming record already exists in the CRM, such as email for contacts and domain for companies, and so whether a write creates or updates.
  • Approval gateAn approval gate is a rule in FieldXM that sets how much autonomy an action that changes records gets, from always ask first to act autonomously; the team chooses the level, and FieldXM logs it.

See it in FieldXM

  • Your CRMConnect HubSpot or Salesforce, and FieldXM puts each lead on the right record with its qualification answers, notes, and enrichment, in your own fields.

Browse