
A prospect record built for calling needs 12 fields: who the person is, how to reach them, why to call now, what happened last time and what happens next. Everything else is optional, and most of it is never read.
The test for any field is simple. Does it change what the rep does in the ten seconds before the dial or the ten seconds after the hang-up? If not, it does not belong on the first screen.
Most CRM templates are designed by the person who builds reports. The record ends up with 60 properties, half of them empty, and the phone number is three scrolls down.
A caller uses the record differently. Before the call, it answers "why this person, why now, what do I say first". After the call, it captures the outcome so the next attempt is smarter than this one.
Between the two, it feeds the machine: which list the contact lands in, when they are called again, and who owns the follow-up.
Make a field mandatory only when the call cannot happen, or cannot be followed up, without it.
Mandatory at creation: number, number status, role, company segment, owner. If one is missing, the contact should not enter a call list.
Mandatory after each call: last outcome, attempts, next step. These should be one click or automatic. If logging takes longer than the call, reps stop logging.
Filled when it exists: trigger, best slot, conversation note, language. Valuable, but forcing a value produces junk like "n/a" and "see notes".
In our experience, every mandatory free-text field ends up filled with a single character by the end of the quarter. Use short picklists for anything you want to filter on.
Some properties look serious and never change a conversation.
Keep them in the CRM if reporting needs them. Move them off the calling view.
The opposite problem is more expensive. Reps only use about 20% of the signals already in their CRM, mostly because those signals are buried in properties no one opens. A trigger that is not on the first screen does not exist.
Each field should drive a decision without a human in the middle.
If a field does not feed one of these rules, ask again why it is there.
One note for European teams: a record is personal data. Keep what the call needs, record where the number came from, and honour opt-outs fast. Your DPO or legal counsel should confirm the details for your case.
In Sonik, the record is what the rep sees in the seconds before a pickup, so it is built around the same three questions: reach, relevance, memory.

The contact view puts account intelligence, the person's experiences and the signals that qualify the contact on one screen, next to the call button. The rep does not open five tabs to find the trigger.
After the call, the outcome and the AI summary go back to HubSpot or Salesforce, and the next step becomes a callback in the dialer. 50% of Sonik's own pipeline comes from signals that were already in the CRM. The record is where they become visible.
A good prospect record is short, and every field earns its place by changing the call or the follow-up. This week, open the record of the last contact you called and count the fields you actually read before dialing. Put those first. Hide the rest from the calling view.