Useful CRM fields. Less manual sorting.

For a company, that might be an adoption concern mentioned in a conversation. For a person, it might be a stated contact preference. Keep the question specific enough that a teammate can judge whether the proposed answer is supported.

Start in CRM → Fields with a saved custom field, then open AI suggestions. Choose the instructions, permitted sources and time window. Text and long-text fields work for concise explanations. Select and multi-select fields work when your team needs one of the options already defined for that field.

The record type matters. A company-level field should describe the company; a person-level field should describe that person. A detail about one deal should not quietly become a general fact about the whole business. Clear instructions and a small reviewed sample help you catch that mismatch before applying values.

Ask an answerable question

Prefer “What concern did this company state?” to an instruction that asks the model to infer everything about the account.

Choose the right shape

Use an explanation when context matters and an allowed category when consistent grouping is the goal.

Test different records

Include records with useful context, little context and an existing value so you can inspect the different outcomes.

It defines the question, chooses the permitted CRM and meeting sources, and selects a few companies. Spacebrain shows the cost quote before the sample runs through Orbit. Saving the field configuration alone does not run the sample or change the CRM.

For each result, compare the current value, suggested value and source excerpt. One company might have a clear concern about migrating its records. Another might have too little evidence. Leave unsupported results unapplied; a missing answer is not a reason to clear an existing field.

Values entered by people or other tools receive protection. Replacing an existing value requires explicit overwrite review, and a changed record can require a fresh sample. Where private context is involved, review the visibility choice before publishing a derived value into a shared CRM field. These controls make the proposed change inspectable at the point of use.

Run a small sample

Up to ten records lets you assess the instruction and quoted usage before expanding your use.

Keep the approved result

Apply selected suggestions after checking the evidence. The result is a value on the native CRM record.

Refresh deliberately

Optional refresh uses a selected scope and daily credit cap. It creates new suggestions; applying them remains a separate review.