One Buyer Joined the Sales Call From Two Devices: Merge Attendance and Transcript Identity

When a prospect joined meeting from two devices, do not count two attendees. Create a buyer-level record only after you can show that both instances belong to the same person, then retain the original instances underneath it.

This protects booked-call reporting from a basic mistake: a device event is not a buyer. It also keeps sales notes honest when one person speaks from a laptop, reads chat on a phone, or reconnects during the call.

Does a prospect joined meeting from two devices count as one buyer?

Yes, after identity verification. A signed-in platform identifier, a calendar invite tied to the buyer, or an explicit confirmation during the call can support that decision. A similar display name, a company domain, or a time overlap can flag a review, but should not settle it alone.

Google Meet exposes a participant's first join and last leave times, plus one identity form: signed-in, anonymous, or phone. Its signed-in form includes a unique user ID, while anonymous and phone entries expose display information instead. Use that distinction when you decide how much confidence the platform record can carry. Google Meet participant reference

• Verified merge: a stable platform identity or direct confirmation connects both instances to the same buyer record.
• Review needed: the evidence is plausible but does not uniquely identify the person.
• Keep separate: the records conflict, or neither record identifies the buyer well enough.

What should the participant-identity merge record contain?

Make one merge record for the buyer, not a replacement participant row. Store the raw identifiers, the evidence, the reviewer, and the final count. That gives a sales manager a way to recheck a booked call without guessing why two device instances became one person.

The table is a working record, not a claim that every field comes from every meeting platform. Capture the fields your platform provides, then record the human verification separately.

How should attendance be merged without inflating attendance?

Keep each device's join and leave events as raw evidence. At the buyer level, record one attended status after the merge. Do not add two device durations together when they overlap, because that creates more attendance time than the person could have been present.

Google Meet models participant sessions separately. It states that a new unique session ID is assigned whenever a user joins, including when the same user rejoins from the same device. That is why session count belongs in the audit trail, not in the buyer count. Google Meet participant-session reference

For a simple buyer-level duration, take the union of verified attendance intervals. If the laptop runs from 10:00 to 10:30 and the phone runs from 10:20 to 10:25, the buyer attended for the 10:00 to 10:30 window, not 35 minutes. Record that calculation method beside the merge record.

• Keep raw intervals by participant instance.
• Merge only intervals tied to the verified buyer.
• Use the combined interval coverage for buyer attendance.
• Keep the device-session count separate from the buyer count.

How should transcript and chat evidence be assigned?

Assign an item to the participant instance that produced it before you make a buyer-level rollup. This prevents a transcript line or chat message from becoming proof of identity when it only proves that one unlabeled instance was active.

Google Meet describes a transcript entry as one user's speech during a transcript session, and its entry includes a participant reference plus start and end times. Keep that entry ID and participant reference in the merge record. Google Meet transcript-entry reference

At buyer level, present the verified person's transcript and chat items together, with the source instance still available. If the platform cannot tie chat to a participant, label the item as meeting evidence rather than buyer-owned evidence.

What should stop an automatic merge?

Stop when the evidence could fit more than one person. Two anonymous entries with the same first name, an attendee who shares a company with the buyer, or a device that arrives only during a screen share all need a human check before they change buyer reporting.

Also separate identity from transcription. Google Meet treats a transcript as metadata for a conference transcription session, and it can have its own start and end time. A transcript's existence does not verify who attended or spoke. Google Meet transcript reference

Route an unresolved case to the meeting owner with the raw participant records, the calendar invite, and the reason the link remains uncertain. Until that review finishes, report the known buyer count and the unresolved instances separately.

How does this change booked-call reporting?

Count the meeting once for the verified buyer who attended. Keep the device instances as evidence, but do not let them raise the attendee count, buyer count, or booked-call total. This is especially important when you reconcile a meeting attendee identity mismatch or an unexpected attendee.

Use the same record when notes conflict with a transcript. The transcript-and-notes reconciliation workflow starts from the evidence rather than a salesperson's memory. For broader reporting, keep the final buyer-level status consistent with your LinkedIn outreach attribution model.