The scope of appointment must be obtained before the call — no later than the moment the appointment is set, and in every practical case the evening before Friday's 10 a.m. slot, not during or after it. The binding rule comes from CMS's 2008 Medicare Marketing Guidelines-as-regulation (42 CFR §422.2264 and §423.2264 for Part D) and its standing clarification: for a telephonic personal marketing appointment, the SOA is collected no later than 48 hours before the scheduled encounter, and the plan must document it. A same-day or tie-break appointment needs the SOA at the point of scheduling.

The one exception that matters most in the field: a beneficiary-initiated inbound call that becomes an unscheduled sales discussion. In that case the SOA is captured before any plan-specific marketing begins, on a recorded line, and the 48-hour clock never starts.

Everything else — including Friday at 10 a.m. booked on a Thursday by an outbound agent — falls under the 48-hour rule, and an agent who "collects it on the call" has already violated the timeline.

What CMS Actually Requires When an Agent Sets a Telephonic Appointment

CMS treats the Scope of Appointment as a consumer-protection document, not a formality. The governing text is in the Medicare Marketing Guidelines, incorporated by reference into the Part C and Part D regulations, and it makes a clean distinction between telephonic and in-person appointments. For a telephonic personal marketing appointment, the SOA must be obtained no later than 48 hours before the scheduled appointment. For an in-person appointment, the same 48-hour rule applies to the scheduled time, but the document may be captured at the start of the meeting when the appointment was set within 48 hours at the consumer's request.

The practical consequence for the Friday 10 a.m. scenario is arithmetic. If the appointment is set at any point before Wednesday 10 a.m., the SOA must be in place by Wednesday 10 a.m. If it is set later than that, the SOA must be captured at the moment the appointment is made, with the date and time of capture logged. The 48-hour figure is not a suggestion; it is what CMS enforcement and plan-level audits look for first.

The SOA must be specific, too. It names the plan types the consumer agrees to discuss — Medicare Advantage, Medicare Advantage with prescription drug coverage, stand-alone Part D, and, where relevant, supplemental products. A signature (wet, electronic, or recorded verbal attestation under plan policy) and a date are required. A blank "any plan" authorization fails the specificity test, and CMS has said so in sub-regulatory guidance that plans fold into their agent training.

One detail agents routinely miss: the SOA covers the products, not the companies. The document authorizes a conversation about plan types. The agent still needs a separate, compliant basis for the specific plan discussion, and the SOA does not waive the consumer's right to end the call at any point. That distinction shows up in plan audit findings more often than agents expect.

The 48-Hour Clock for a Friday 10 a.m. Call, Worked Through

Start with the deadline, not the call. Friday at 10 a.m. minus 48 hours lands on Wednesday at 10 a.m. That is the outside wall for capturing the SOA if the appointment was set earlier in the week. An agent who books the appointment Monday and takes the SOA Thursday at 9 a.m. has a 25-hour gap and a compliance problem.

Run the scenarios against that wall:

When appointment is set SOA deadline What the agent must do
Monday 2 p.m. Wednesday 10 a.m. Capture SOA within 44 hours; log timestamp
Tuesday 4 p.m. Wednesday 10 a.m. Capture SOA within 18 hours
Wednesday 9 a.m. Wednesday 10 a.m. Capture SOA immediately after booking
Wednesday 3 p.m. At the point of scheduling SOA same conversation; no 48-hour window exists
Thursday 11 a.m. At the point of scheduling SOA same conversation, appointment stays Friday 10 a.m.

The table is the part most agents get wrong in practice. They assume the 48 hours runs from when they first talked to the consumer rather than from the scheduled encounter. It runs from the scheduled encounter. A Thursday booking for Friday 10 a.m. cannot satisfy a 48-hour buffer, which is exactly why CMS built the "at the point of scheduling" fallback into the same paragraph.

For agency principals, the operational rule is simple. Build the booking screen so that a Thursday booking cannot be confirmed without a completed SOA capture in the same session. If the CRM allows the appointment to be saved without the document, the compliance failure is a software configuration problem, not an agent discipline problem.

When the 48-Hour Rule Doesn't Apply: The Beneficiary-Initiated Inbound Exception

The exception agents most often cite incorrectly is the inbound-call carve-out. When a beneficiary calls the plan or an agent directly and the call turns into a sales discussion, no advance SOA is required, because there was no scheduled appointment. CMS instead requires that the SOA be obtained before any plan-specific marketing begins, on a recorded line, and that the recording be retained under the plan's recordkeeping policy.

The distinction hinges on who initiated the contact and whether a marketing appointment was scheduled in advance. A consumer who calls a call center after seeing a television ad is beneficiary-initiated. A consumer who returns a voicemail from an agent who called first is not, even if the consumer placed the callback. That caller-ID technicality gets tested in audit, and agents who rely on "they called me back" as an exception have lost the argument.

There is a second, narrower exception worth naming. If a consumer is already in a sales appointment that was scheduled for a specific product type and, during the conversation, asks about a different product type, the agent may not simply pivot. The agent needs a fresh SOA for the new product type, captured in that same call. The appointment's original scope does not travel to on-the-spot requests.

Plans differ on whether a recorded verbal SOA satisfies their internal policy or whether a signed document or e-signature is preferred. Agents should confirm the specific plan's requirement before their first appointment of the week rather than assume the recording will clear audit. The regulation sets the floor; plans can raise it.

Documenting the SOA so Thursday's Booking Survives a Friday Audit

The documentation is where the case is won or lost. CMS auditors look for the SOA date, the agent's identity, the plan types authorized, the consumer's signature or verbal attestation, and a timestamp that proves capture preceded the appointment. A document that exists but cannot be tied to a date and time fails the same way a missing document does.

Every SOA record needs:

1: The date and time the SOA was captured, not the date the appointment was made. 2: The consumer's name, the plan types discussed, and the signature or recorded attestation. 3: The agent's national producer number and a record of the appointment scheduling timestamp. 4: The recording or e-signature trail, retained per the plan's retention schedule. 5: A note on which exception, if any, applies — inbound beneficiary, at-point-of-scheduling, or the 48-hour rule itself.

Store the "why" record alongside the "what." A plan auditor reading a Thursday-at-3-p.m. SOA attached to a Friday-10-a.m. appointment needs to see that the appointment was set that same Thursday afternoon, not three days earlier. Without the scheduling timestamp, the SOA date alone makes the file look noncompliant even when it isn't.

The failure case that trips up most agencies is a consumer who reschedules. The original SOA captures the product type, not the appointment slot. If Friday 10 a.m. moves to the following Tuesday, the SOA stays valid for those products, but the agent should re-confirm the SOA is still on file and unexpired. Plans vary on how long an SOA stays valid; confirm the specific carrier's rule because the regulation does not fix a federal expiration window.

Why the Appointment Type Changes the Timing — Telephonic Versus In-Person

The telephonic SOA timeline differs from in-person because CMS reasoned that the consumer cannot sign a document in the room at the start of a phone call the way they can in a kitchen. That reasoning drove the 48-hour requirement for telephonic appointments, and it is the reason the same-day in-person fallback does not extend to phone calls.

For in-person appointments, CMS allows the SOA to be captured at the start of the meeting if the appointment was set within 48 hours at the consumer's request. For telephonic appointments, that fallback is not available on the same terms. If the Thursday booking is for a phone call at Friday 10 a.m., the SOA must still be captured at the point of scheduling — not at the start of the call. Agents who treat the phone call like an in-person visit and "take the SOA at the top of the hour" are outside the safe harbor.

This is one of the areas where the applicable regulations (42 CFR §422.2264 and §423.2264) and the sub-regulatory marketing guidelines interact. The regulations set the framework; the guidelines explain the 48-hour mechanics. When a plan's agent handbook and the guidelines conflict, the plan's more restrictive rule usually controls the audit, but the regulatory floor is the one a complaint investigation will measure against.

The Exception Agents Claim That Doesn't Exist, and What to Say Instead

"Verbal permission on the call is good enough" is the single most common wrong belief, and it surfaces in real audit findings. A consumer who says "sure, talk to me about Advantage plans" at 9:55 a.m. Friday does not satisfy the SOA requirement for a Friday 10 a.m. appointment that was scheduled on Tuesday. The SOA needs to be documented before the call, not extracted from it.

The compliant version of that consumer is different. If the appointment was set on Thursday afternoon at the consumer's request, the SOA is captured at the point of scheduling, with the timestamp proving it. If the consumer called inbound and the call became a sales discussion, the SOA is captured on the recorded line before any plan-specific pitch. Both are exceptions. Neither is "verbally at the top of the scheduled call."

There is one genuine edge case where the timeline is arguable: the appointment was set by a third party, such as a caregiver or a spouse, for a consumer who wasn't on the original call. In that case, the SOA must be captured in the first conversation directly with the consumer, ideally at the point of appointment confirmation, and no later than 48 hours before the scheduled time if the appointment is more than 48 hours out. If the caregiver booked Thursday for Friday 10 a.m., the direct conversation with the consumer must happen before any marketing content is discussed.

When in doubt, the conservative rule wins. Capture the SOA at the point of scheduling if the appointment is inside 48 hours. Capture it at least 48 hours before a scheduled appointment if you can. Document both. A regulator reading two timestamps that satisfy both the letter and the spirit of the rule has no case to make.

A Worked Scheduling Checklist for Friday at 10 a.m.

Monday, set the appointment. Agent confirms the consumer's plan-type interest, opens the SOA workflow, captures the signature or recorded attestation, timestamps the record, and logs the appointment. Compliance checks: SOA captured Monday, appointment Friday at 10 a.m., gap is 4 days and falls comfortably inside the 48-hour rule.

Wednesday, confirm the appointment. Agent reviews the file, confirms the SOA remains on record, and notes any product-type additions the consumer requested. If the consumer adds a product type, the agent captures a new SOA. If not, the original document stands.

Thursday, if the appointment is moved. If the appointment is moved to a different time on Friday, the SOA stays valid because the product type and the appointment nature didn't change. If the appointment is moved to next week, the SOA stays valid but the agent re-confirms with the plan because carrier expiration rules differ.

Friday at 9:45 a.m., pre-call check. Agent verifies the SOA on file, verifies the appointment record shows the scheduling date and time, verifies the recording is running on a consent-monitored line, and places the call at the scheduled time. No marketing content before the SOA is referenced and the consumer is reminded the conversation is limited to the authorized product types.

Handling a failure: if the agent discovers at the pre-call check that the SOA is missing or the timestamp doesn't line up, cancel and reschedule. A missed appointment is a marketing inconvenience. A completed appointment without a valid SOA is a reportable compliance event, and the plan's agent-oversight team will treat it as one.

How Plan and Jurisdiction Differences Change the SOA Workflow

Plans implement the federal rule with their own overlays, and the differences matter on a Friday 10 a.m. booking. Some carriers accept a recorded verbal SOA. Others require an e-signature with a timestamp. A smaller number require both, plus a confirmation call. Agents working multiple carriers cannot apply one carrier's workflow to the next.

State insurance departments add their own layers. States that regulate Medicare Advantage marketing more aggressively — for example, states that maintain their own rules on appointment documentation for Medicare-related sales — may require retention periods longer than the federal minimum or specific disclosure language in the SOA. The federal floor is the starting point, but the local overlay is what a state market-conduct exam reads first.

The retention rule matters for the Friday appointment in practice. CMS requires retention of marketing materials and related appointment records for 10 years, per the recordkeeping standard in 42 CFR §422.504 and §423.504. Agents should treat every SOA as a 10-year record and not delete it after the appointment ends. The one exception is a plan-specific policy that sets a longer period; some carriers do.

For call centers, the documentation needs to travel with the agent. If the agent who booked the Monday appointment hands off to a different agent for Friday at 10 a.m., the SOA record and the scheduling timestamp must move with the file. An auditor reading the file does not care who placed the call; the auditor cares that the SOA was captured in time.

What to Do If the Consumer Refuses the Scope of Appointment

A refusal is not a dead end, and it is not a license to proceed. The compliant response is to stop the marketing discussion, document the refusal, and offer the consumer the option to receive plan information by mail or to call back on their own initiative. If the consumer subsequently initiates the contact, the inbound exception applies and the SOA can be captured on that recorded line.

An agent who proceeds with a plan-specific pitch after a refusal has moved from a documentation defect into a marketing-violation category. CMS's compliance program expects plans to monitor for that behavior, and plans pull call recordings for exactly this reason. The refusal, once documented, also protects the agent: a clear record showing the agent stopped and offered an alternative is the strongest file a complaint investigation can encounter.

For a Friday 10 a.m. appointment, a refusal during the Monday registration call ends the scheduling process. There is no appointment to attend, no SOA to chase, and the record shows the reason. Rescheduling after a refusal is not permitted unless the consumer initiates it, and the rescheduled call follows the inbound rules.

The operational lesson is that the SOA conversation is a sales gate, not a clerical step. Consumers who understand what they're authorizing tend to sign. Consumers who feel rushed into it refuse. The agent who explains the document in one clear sentence at the point of scheduling has a smoother Friday at 10 a.m. than the one who treats the signature as a speed bump.

FAQ

Can the SOA be captured on Friday at 10 a.m. at the start of the call?

No, for a telephonic appointment set in advance. CMS requires the SOA no later than 48 hours before the scheduled encounter for a telephonic marketing appointment, or at the point of scheduling if the booking happens inside that window. Capturing it at the top of the call is a violation for a scheduled Friday booking made earlier in the week.

Does the 48-hour clock start when the agent first speaks with the consumer?

It starts from the scheduled appointment time, not the first contact. An agent who spoke with the consumer Monday but set the appointment Thursday for Friday at 10 a.m. has no 48-hour buffer and must capture the SOA at the Thursday scheduling moment. Confusing first contact with appointment date is a frequent audit finding.

Is a beneficiary-initiated inbound call exempt from the SOA requirement?

It is exempt from the advance timing requirement, not from the SOA itself. The SOA must still be obtained before any plan-specific marketing begins, on a recorded line, and retained per the plan's policy. The exemption applies only when no appointment was scheduled in advance and the consumer initiated the contact.

What happens if the consumer reschedules Friday's appointment to Tuesday?

The SOA remains tied to the product types, not the time slot. Confirm the document is still on file and verify the plan's expiration rule, because carriers differ on how long an SOA stays valid. Also confirm the appointment record is updated so the scheduling timestamp aligns with the new encounter.

Can one SOA cover Medicare Advantage and stand-alone Part D?

Only if both product types are explicitly listed and the consumer signs or attests to both. A generic "any plan" authorization does not satisfy the specificity requirement. Agents who want to discuss both need both checked and the document retained as a single authorization covering two product types.

Does a caregiver booking the appointment satisfy the SOA requirement?

No. The SOA must be captured in a direct conversation with the consumer whose plan is being discussed, even when a caregiver scheduled the appointment. The first direct contact with the consumer should capture the SOA, ideally at confirmation and never later than 48 hours before a scheduled appointment.

What's the record retention period for an SOA?

CMS sets a 10-year retention standard for marketing and related appointment records under the Part C and Part D recordkeeping requirements. Some carriers extend that, so check the plan's agent handbook. Deleting an SOA after the appointment ends is a compliance risk even when the customer relationship is over.

This article is general educational information about Medicare marketing compliance, not a legal opinion or a substitute for the specific CMS regulations, plan policies, or state insurance rules that apply to a given agent or appointment. Marketing timelines and documentation requirements vary by plan, product type, and jurisdiction, so confirm the controlling requirements with the plan's compliance team or a qualified insurance regulatory professional before relying on this guidance. If a consumer's safety is at risk or an immediate emergency is involved, contact local emergency services.