A Gatekeeper Answers: Preserve Who You Actually Spoke With
When someone other than the intended prospect answers a cold call, record the person you actually reached, the number dialed, and what happened to any offered transfer. An answered call is not proof that you spoke with the prospect. An offered transfer is not a completed transfer, and a gatekeeper's description of someone else's availability is not that person's commitment.
The goal is a call-path record another rep can understand before the next attempt. Keep the intended contact, actual respondent, later participant, and next-action owner distinct. This guide covers that multi-person path rather than objection scripts or generic call-note formatting.
Start with the intended person and the answered number
Before recording an outcome, identify the record from which the call began and the exact number used. Preserve whether the route was a direct number, a mobile, a shared business line, or an unknown number type. Do not silently relabel a shared number as the prospect's direct line because someone answered it.
The making-calls documentation describes selecting a number from a person record or task and logging the result. The record that initiated the call supplies workflow context. It does not independently establish the identity of the person who answered.
Use record inspection to check the contact and company information available to you. Preserve uncertainty where the respondent's name or role is unknown. A role inferred from a switchboard greeting should not be recorded as a verified job title without supporting evidence.
If the number is useful as a route to the company, keep that distinction visible. Do not mark a number invalid solely because it reached a receptionist or another employee. Invalidity, shared routing, and failure to reach the intended person are different findings.
Attribute each statement to its speaker
Record what the actual respondent said, including any restriction, routing instruction, or offer to help. Distinguish direct statements from the rep's interpretation. If you summarize rather than quote, make that clear in your notes.
A respondent may describe the prospect's schedule, role, or interest. Preserve that as information supplied by the respondent, not as something the prospect personally confirmed. Do not upgrade a report of availability into a booked commitment or a report of disinterest into a detailed first-person objection from someone you never reached.
This distinction also matters when the respondent provides a name, extension, or email address. Record the source and intended use. A suggested route is not automatically permission to enroll a newly identified person in an unrelated campaign.
The account-contact research use case can support a subsequent identity check. Research should supplement the call record, not overwrite what was actually observed during the call.
Separate the stages of a transfer
A transfer can be offered, accepted, attempted, connected to another destination, and completed with an identified participant. Those stages should not collapse into a single “transferred” label.
| Stage to record | Evidence to preserve | What remains unproven |
|---|---|---|
| Transfer offered | Who offered it and the intended destination | Whether any transfer occurred |
| Transfer attempted | What the rep observed after accepting | Whether the intended person was reached |
| New destination answered | What answered and how identity was established | Whether it was the intended prospect |
| Later participant identified | The participant's confirmed identity and role, if known | Buying authority or interest beyond what was said |
| Conversation completed | Statements and commitments attributable to that participant | Any unstated agreement or future action |
If the path ends at voicemail, a queue, another gatekeeper, or a disconnected call, record that outcome. Do not report a completed prospect conversation because an intermediary initiated a transfer.
A recipient's telephone system may transfer the call. That does not prove your sales dialer supports an in-app transfer feature. The current Unify documentation on placing and logging calls should not be used to infer live transfer controls, automatic multi-party attribution, or automatic reassociation of the activity to a different person.
Choose the disposition that reflects who was reached
Unify's call disposition documentation separates attempts that did not reach the prospect, including gatekeeper outcomes, from connected outcomes that reached the prospect. Connected categories then describe how far the interaction progressed.
If the call ended with the gatekeeper, do not record a prospect conversation simply because a human answered. If the transfer did reach the prospect, use the actual final outcome and preserve the earlier path in notes. A disposition is a summary; the notes supply the detail needed to interpret it.
Workspace administrators can maintain custom dispositions within the documented controls. A custom label should have a clear definition so reps do not use the same phrase for an offered transfer and a completed conversation. Review the reporting category before introducing a new connected outcome, because categories influence analytics.
Be careful with outcomes that change eligibility. The standard Bad number disposition can mark the dialed number invalid after a call made in Unify. Do not call opts the person out of future calls. Use these actions only when the evidence supports them and the affected identity is correct. Escalate ambiguous restriction scope rather than applying a convenient but inaccurate label.
Keep the call attempt separate from the task decision
After the call, decide whether the original task was fulfilled. Logging an attempt and completing the task are different actions. The making-calls guide describes Log call, which can leave a task open, and Log and complete task. Completing a sequence task can let the enrollment advance.
Read Complete tasks before using a skip action. Skipping a sequence task can also let the enrollment advance. If the next message assumes the rep spoke with the prospect, advancing without reviewing it can carry a false premise into email.
In the Power Dialer, skipping a person in a task-based calling queue leaves their task open. That queue behavior should not be confused with skipping the task itself.
A useful next step may be to keep the attempt open, create a specifically instructed follow-up, or end inappropriate outreach. The call outcome alone does not choose among these actions. Review the recipient's actual instruction and the pending workflow before saving.
Use a blank call-path note
This template is designed for a call with more than one possible participant. It contains no invented conversation or observed outcome. Fill it from the call and keep unknown fields explicit.
| Call-path field | Entry |
|---|---|
| Original task or call activity reference | |
| Intended person and account | |
| Dialed number and known number type | |
| Actual respondent and identity evidence | |
| Respondent's stated role, or unknown | |
| Statements attributable to the respondent | |
| Transfer offered and intended destination | |
| Transfer attempted and observed result | |
| Later participant and identity evidence | |
| Statements attributable to the later participant | |
| Restrictions or contact-route instructions | |
| Disposition and task/enrollment decision | |
| Next action, owner, and agreed timing | |
| Unresolved facts requiring review |
For a longer path, add a separate participant entry instead of blending everyone into one paragraph. Preserve the sequence of events so the next rep can tell which person supplied which information.
Keep only the information needed for the follow-up and applicable business record. Avoid collecting unnecessary personal detail simply because it arose in conversation. Restrict access to any recording or sensitive note according to the team's policy.
Treat recordings and transcripts as supporting evidence
Where a permitted recording or transcript exists, it can help a reviewer check the call path. It does not automatically establish reliable speaker identity or correct association with every person involved.
Review the recording documentation and the settings applicable to the call. Do not assume every call is recorded or that a transfer creates a correctly labeled multi-party transcript. If recording was stopped or unavailable, document the evidence you actually have instead of inventing a verbatim account.
Check names, pronouns, and statements in any automated summary before using it as a next-action instruction. A summary that attributes the gatekeeper's words to the prospect can cause the next rep to open with an inaccurate claim. The responsible rep should correct the operational note while preserving the underlying activity history.
Verify the activity destination without rewriting history
If the call needs to appear in Salesforce or HubSpot, inspect call CRM sync. The destination and available fields depend on the calling provider, sync rules, mappings, and permissions. A sync success does not prove the activity identifies the person who actually spoke.
Review the record relationship and the saved notes. If association needs correction, follow the CRM's approved process and preserve the original call context. Do not create duplicate “conversations” for each participant merely to make them visible unless the data model deliberately represents one call with multiple relationships without inflating activity counts.
The completed-tasks versus prospect-touches guide helps keep these counts separate. A transferred call should not turn into several prospect conversations simply because it produced several records or tasks.
This article does not replace a connector matching test. It addresses the human evidence the record needs, whatever system stores it.
Prepare the next contact from the actual commitment
Use task creation to assign one clear action. Include the contact route, the source of the instruction, and any agreed timing. Do not leave a generic “follow up” task that forces the next owner to reconstruct the call.
Before another attempt, inspect recent activity, sequence enrollments, and applicable engagement policies. A routing suggestion should not cause concurrent calling by multiple reps or override a known restriction.
If the team needs a general follow-up system beyond the multi-person path, use the cold-call follow-up guide. For this case, the crucial question remains: what action is supported by what the actual speaker said?
Review the record before judging the account
An incomplete transfer gives information about the route, not necessarily the prospect's interest. The no-answer interpretation guide addresses that broader distinction. Avoid declaring an account unresponsive because the intended person was never reached.
Managers reviewing these records should be able to identify the intended person, actual respondent, transfer result, and next owner without asking the rep to explain from memory. If any of those is uncertain, keep it visible rather than resolving it through an optimistic disposition.
For an internal record-quality review, freeze the set of relevant call activities and the review time. Count records with all required, evidence-supported path fields as the numerator and all reviewed in-scope call activities as the denominator. Report inaccessible recordings, unknown participants, and unfinished reviews separately; an unknown fact can be accurately recorded as unknown but should not be counted as verified identity. With no reviewed calls, the measure is not applicable. This evaluates documentation quality, not prospect interest or dialer performance.
Frequently asked questions
Does a gatekeeper answer count as reaching the prospect?
No. Record the actual respondent and use the outcome that reflects whether the intended prospect was reached. A human answer alone is not evidence of a prospect conversation.
How should I record an offered transfer that did not complete?
Preserve who offered it, the intended destination, what the rep observed, and where the call ended. Keep transfer offered, attempted, and completed as distinct states.
Does Unify automatically reassociate a transferred call with the later participant?
The documentation inspected for this workflow does not establish automatic multi-person reassociation or in-app live transfer support. Preserve participant details explicitly and inspect the saved activity and CRM relationship.
Should I complete the call task after reaching a gatekeeper?
Decide from the task's purpose and the supported next action. Logging an attempt can leave the task open, while completing or skipping a sequence task can advance later outreach. Review that consequence before saving.
