Meetings and the Contact Record
What the conversation leaves behind on the person.
What It Is
When a meeting has a contact attached and you have the contact update setting switched on, processing writes three things onto that person's record.
A note, carrying the factual summary of the meeting, dated and marked as coming from the meeting. It sits in their history alongside everything else.
A sharper profile — what the conversation revealed about the problems they have, what they want, what is driving them, and what they are worried about. Each one recorded with the words it was drawn from.
Specific details, where Zyntro picked something up with enough confidence to be worth recording: a job title, a timezone, what kind of organisation they are.
None of this appears on the meeting's screen. It is on the contact.
Why It Matters
Because this is the part that accumulates. A single meeting's summary is convenient. Thirty meetings' worth of accumulated profile is a different thing entirely — a contact record that knows what this person cares about, built from conversations rather than from somebody remembering to type it in.
And nobody maintains it. The reason CRM data decays is that keeping it current is work that never feels urgent. This is the same work, done as a side effect of having the conversation.
Because the rest of Zyntro reads it. The profile is not a filing cabinet. It is what shapes how Zyntro writes to that person, what it decides to say next, and when. A contact whose pain points came out of a real conversation gets better-aimed communication than one built from a form.
Because it closes the loop with the brief. The brief before a meeting is assembled from what Zyntro knows; the meeting then improves what it knows; the next brief is better. After a few conversations the brief stops being a summary of a form and starts being a summary of a relationship.
How It Works
It needs a contact on the meeting
No contact, nothing to write to. A meeting with only typed-in attendees, or only colleagues, produces its results on the meeting screen and in your debrief and goes no further.
This is the practical reason to attach the contact rather than typing a name: it is what connects the conversation to the person.
The note
A note is added to the contact's history carrying the factual summary, prefixed so you can see where it came from and when. It is attributed to the meeting's organiser rather than to the system, so their history reads as a record of who spoke to them.
The same summary is not added twice. If a meeting is processed again, the note is not duplicated.
The profile
Pain points, desires, motivations and fears are recorded as a profile entry against the contact, each item carrying a short label, a fuller description, the evidence from the conversation, and a strength of high, medium or low.
New findings are merged with what was already there rather than replacing it. An item already on the profile is not added again, and anything new is appended. So a contact's profile grows across conversations instead of being overwritten by the most recent one — which is what makes a long relationship's record worth more than a new one's.
The entry records that it came from a meeting, so you can tell conversation-derived material from anything entered by hand.
The inferred details
Zyntro also picks up specific facts and can write them onto the contact: their title, their timezone, tags, the role they play. Where the contact belongs to an organisation in your CRM, it can do the same at that level — the organisation's name, type, location and tags.
Only confident inferences are applied. Something mentioned in passing, or ambiguous, is left alone rather than written onto the record as fact. This is deliberately conservative: a wrong job title that arrived automatically is worse than a missing one, because nobody thinks to doubt it.
Every contact on the meeting
If several contacts were in the meeting, all of them get this treatment. A three-way call with two of your contacts updates both records.
Examples
A discovery call with a new prospect
Their record gains a note summarising the call, a profile carrying the three problems they described with the quotes behind them, and possibly their job title if they said it. Before the call their record held a form submission; after it, it holds a picture of them.
The fourth call with an existing client
The new material is merged into what is already there. Concerns they have raised before are not duplicated; anything new is added. Their profile is now built from four conversations.
They mention they have moved to a new role
If they said it clearly, the title on their record is updated. If it was ambiguous — a passing reference to a change — it is left alone, and you would find it in the transcript rather than on the record.
An internal team meeting
No contacts involved, so nothing is written to any record. The meeting still has its full intelligence and you still get your debrief.
You typed the attendee's name in rather than attaching their contact
The meeting is processed normally but nothing reaches a contact record, because Zyntro has no contact to write to. Attaching contacts rather than typing names is what makes the difference.
Important: None of this happens unless the contact update setting is on. It is off by default, at Settings → Sales Settings → Meeting Settings as Update the contact record from what was said. A workspace that has never visited that screen is producing meeting intelligence and writing nothing to its CRM.
Tip: Check the evidence before acting on a profile item. Each pain point and desire carries the words from the conversation it was drawn from. If something on a contact's profile looks wrong or surprising, the evidence tells you whether it is a misreading or something you simply did not notice at the time.
