Become an Agent
Atlas Coast Travel Group — Staff SOP
Cancellations & Terminations
Scenarios 1 & 2 Owner: Donna Scenario 3 Owner: Bati (Bati-only) Last Updated: May 26, 2026 Version: 1.0 Zaps Covered: 3, 4, 5, 6
Termination for cause (Scenario 3) is Bati-only. Do not initiate, execute, or communicate a termination for cause without explicit instruction from Bati or Melissa. Donna handles Scenarios 1 and 2 only.
Three Scenarios at a Glance
ScenarioTriggerOwnerZapAgent Can Rejoin?
1. Self-Cancel Agent cancels their own subscription in Kajabi Automated (Donna monitors) Zap 4 Yes — at current Regular Rate. Founders Rate forfeited.
2. Failed Payment Payment retry window exhausted; TA Cancelled - Failed Payment tag applied Automated (Donna monitors) Zap 5 Yes — at current Regular Rate. Founders Rate forfeited.
3. Termination for Cause Melissa decision; Bati executes Bati only Zap 6 No — cannot auto-rejoin. Requires manual team review.
Core Policy (All Three Scenarios)

No 30-day notice required. No prorated refunds under any circumstances. Subscription fees are non-refundable. Commission eligibility ends on the last day of active membership. Dots account remains active after cancellation for pending payouts and tax documents. Documented in the ITA.

Self-Cancel (Agent-Initiated)
Owner: Donna — No manual action required unless agent contacts support

Agent clicks cancel inside their Kajabi account settings. Kajabi handles the cancellation natively: access continues through the end of the current billing period, then access is removed. Two automations fire at two different points in time.

Automation 1 — Immediate (Fires When Agent Clicks Cancel)
Cancellation Initiated Notification
Kajabi Workflow ID: 737887
Trigger: Subscription cancellation initiated — Travel Agent Monthly Hosting Fee
  • 1 Add tag: TA Cancelled - Pending Cancellation
  • 2 Send email: "We've received your cancellation request" — confirms access continues through end of billing period, what access ends when, Dots account stays active, open booking guidance, credential revocation timing, rejoin link
Automation 2 — End of Billing Period (Fires When Access Expires)
Access Revocation and Final Notification
Kajabi Workflow ID: 737903
Trigger: Subscription cancellation complete — Travel Agent Monthly Hosting Fee
  • 1 Add tag: TA Cancelled
  • 2 Remove tag: TA Cancelled - Pending Cancellation
  • 3 Remove tag: TA Active
  • 4 Remove tag: TA Active (Rejoined)
  • 5 Remove tag: onboard-scheduled
  • 6 Unsubscribe from: New Agent Signed Email Onboarding Sequence
  • 7 Revoke offer: Travel Agent Monthly Hosting Fee
  • 8 Revoke offer: Atlas Partners & Coaches
  • 9 Send email: "Your Atlas Coast membership has ended" — confirms access removed, commission eligibility ended, Dots stays active, open booking guidance, credentials revoked, rejoin link
Tags Intentionally Preserved on Self-Cancel

These tags are NOT removed so returning agents skip already-completed steps: idv-verified, academy-complete, onboarding complete, first-booking, agent-referred, dual-agency, agent-vet

Zap 4 — MyAtlas Deactivation
Zap 4
Self-Cancel: Deactivate MyAtlas Account
Trigger: Kajabi tag added: TA Cancelled
Action: POST to JourneyFuse with deactivation_flag: true — deactivates the agent's MyAtlas account
Pattern: OAuth + Kajabi contact lookup + JF POST
Confirmed working — May 26, 2026
If an Agent Contacts Support About Their Cancellation
  • 1
    Confirm their cancellation status in Kajabi. Check for TA Cancelled - Pending Cancellation (still in billing period) or TA Cancelled (access ended).
  • 2
    Refund requests: All subscription fees are non-refundable. Do not issue refunds without explicit approval from Melissa. Refer agent to the ITA at atlascoasttravel.com/ITA.
  • 3
    Open bookings: Agents are asked to service existing clients as a professional courtesy through their access end date. If unable, they should contact [email protected]. Atlas Coast will assign the booking to a Booking Partner. Escalate any open booking situations to Bati.
  • 4
    Rejoining: Agent can rejoin at atlascoasttravel.com/join. They will be billed at the current Regular Rate. Founders Rate cannot be reinstated.
  • 5
    Pending commissions: Dots account remains active. Any commissions Atlas Coast had received before the termination date will pay out in the next regular cycle. Commissions not yet received by Atlas Coast will not be paid after termination. Escalate disputes to Betsy.
Failed Payment Cancellation
Owner: Donna — Monitor Missive for payment failure alerts; escalate if agent disputes

Kajabi automatically retries failed payments on a native retry schedule. If all retries are exhausted without a successful charge, Kajabi applies the TA Cancelled - Failed Payment tag, which triggers Zap 5 to deactivate MyAtlas. Tag and offer handling mirrors the self-cancel flow.

Payment Retry Window

Kajabi's native payment retry schedule handles all retries automatically. Atlas Coast does not manually extend payment grace periods. If an agent contacts support saying their card was declined, direct them to update their billing information at atlascoasttravel.com/billing before Kajabi exhausts all retries. Once the TA Cancelled - Failed Payment tag is applied, access has already been removed.

Zap 5 — MyAtlas Deactivation on Failed Payment
Zap 5
Failed Payment: Deactivate MyAtlas Account
Trigger: Kajabi tag added: TA Cancelled - Failed Payment
Action: POST to JourneyFuse with deactivation_flag: true — deactivates the agent's MyAtlas account
Pattern: OAuth + Kajabi contact lookup + JF POST
Confirmed working — May 26, 2026
If an Agent Contacts Support After a Failed Payment Cancellation
  • 1
    Verify the cancellation in Kajabi. Look for the TA Cancelled - Failed Payment tag on the contact record.
  • 2
    If agent wants to reinstate: They must rejoin at atlascoasttravel.com/join with an updated payment method. The TA Active Rejoined automation handles reinstatement. Founders Rate cannot be reinstated.
  • 3
    If agent disputes the charge failure: Direct them to update billing at atlascoasttravel.com/billing. Do not manually restore access without Melissa's approval.
  • 4
    Pending commissions: Same policy as self-cancel. Escalate disputes to Betsy.
After Scenarios 1 or 2

Agent has TA Cancelled or TA Cancelled - Failed Payment tag. MyAtlas deactivated via Zap 4 or 5. Completion-related tags preserved. Dots account remains active. No further action required unless agent contacts support.

Termination for Cause
Restricted Access — Staff SOP
Termination for Cause
Owner: Bati — Executed by Bati or Melissa only. Donna does not initiate or execute terminations.
Before You Do Anything

The decision to terminate belongs to Melissa. Bati executes on Melissa's instruction. No other staff member initiates, executes, or communicates a termination. If you receive a complaint or observe something that might warrant termination, surface it to Bati in Missive. Do not contact the agent about termination.

What Happens When Bati Applies TA Terminated

Bati applies the TA Terminated tag to the agent's Kajabi contact record. Kajabi Automation #28 fires immediately and executes a full sweep.

Automation #28 — Termination for Cause
TA Terminated for Cause — Full Sweep
Kajabi Automation #28 — Published
Trigger: Tag added: TA Terminated
  • 1 Remove ALL active membership tags (TA Active, TA Active (Rejoined), onboard-scheduled, and all other tags in the sweep)
  • 2 Revoke ALL offers (Travel Agent Monthly Hosting Fee, Atlas Partners & Coaches, and any other active offers)
  • 3 Unsubscribe from all email sequences
  • 4 The TA Terminated tag fires Zap 6, which deactivates and blocks the agent's MyAtlas account
What Not to Say to the Agent

Do not communicate the reason for termination in writing unless Melissa and Jeannette (outside counsel) have reviewed the language. Do not reference specific incidents, complaints, or policy violations in any agent-facing communication without that review. Bati handles all agent communication on terminations personally.

If the agent contacts support after termination, acknowledge their message and route it to Bati immediately. Do not discuss the reason, dispute the decision, or offer any next steps on behalf of the team.

Zap 6 — MyAtlas Block on Termination
Zap 6
Termination: Deactivate and Block MyAtlas Account
Trigger: Kajabi tag added: TA Terminated
Action: POST to JourneyFuse — deactivates and blocks the agent's MyAtlas account. Unlike self-cancel, a terminated agent cannot auto-rejoin.
Pattern: OAuth + Kajabi contact lookup + JF POST
Confirmed working — May 26, 2026
Documentation Requirements
StepActionWho
Before terminationMelissa documents the basis for termination decision in writing (Notion or Missive). Jeannette consulted if there is any legal risk.Melissa
ExecutionBati applies TA Terminated tag in Kajabi. Records the date and context in Missive.Bati
Agent communicationBati sends a brief, factual communication to the agent. No specifics without Jeannette review.Bati
Open bookingsBati identifies any open bookings under the terminated agent. Assigns to a Booking Partner for servicing. Agent does not receive commission on post-termination bookings.Bati
CommissionsBetsy confirms whether any commission payments were already in the pipeline. Earned commissions received by Atlas Coast before the termination effective date are paid in the next cycle. Nothing after.Betsy
Credential revocationIATAN and CLIA access under Atlas Coast umbrella ceases on termination effective date. No further action required — these are tied to active membership status.Automated
Rejoin requestsTerminated agents cannot auto-rejoin. Any rejoin request requires manual review and explicit approval from Bati and Melissa.Bati / Melissa
Open Item

Automation #28 is published and confirmed in place. A final verification pass with Cowork is still outstanding to confirm the complete tag sweep list and ensure no active tags are missed. Until that verification is complete, Bati should manually spot-check the agent's Kajabi contact record after Automation #28 fires to confirm all offers are revoked and all active tags are removed.

Refund Policy
ScenarioPolicy
Agent cancels mid-periodAccess continues through end of billing period. No refund for unused portion. No exceptions.
Agent rejoins after cancellationBilled at current Regular Rate. Founders Rate cannot be reinstated under any circumstances.
Agent disputes a chargeDirect to billing at atlascoasttravel.com/billing. Escalate to Melissa for any chargeback or bank dispute — do not engage via Stripe or Kajabi without her instruction.
Termination for cause — refund requestNo refund. Bati handles all communication. Do not discuss or negotiate refunds without Melissa and Jeannette approval.
Sub-$25 Dots balance at cancellationDots account remains active. Balance rolls forward and pays out when $25 threshold is met. Dots account is never closed by Atlas Coast.
Never Issue a Refund Without Explicit Melissa Approval

Subscription fees are non-refundable per the ITA. Any refund request must be escalated to Melissa before any action is taken. Do not commit to or decline a refund on behalf of the team — acknowledge the request and route it to Melissa via Missive.

Commission Eligibility on Exit
SituationWhat Happens
Commission eligibility endsOn the agent's last day as an active member (end of billing period for self-cancel; effective date for termination).
Commissions already received by Atlas Coast before terminationPaid out in the next regular payout cycle (1st or 15th). Betsy confirms and processes.
Commissions in transit (supplier has not yet paid Atlas Coast)Not paid after termination. Atlas Coast can only pay what it has received.
Dots account after cancellationRemains active. Agent retains access to payout history and tax documents (1099 if applicable). Atlas Coast does not close Dots accounts.
Open bookings at terminationAssigned to a Booking Partner by Bati. Departed agent does not receive commission on bookings completed after their termination date.
Chargeback recovery after terminationIf a chargeback is received after termination for a booking the agent made, Atlas Coast will seek direct repayment. Escalate to Bati/Melissa for any terminated agent chargeback.
For Agent Questions About Commission on Exit

Direct agents to: Atlas Agent Dashboard > How Commissions Work, or to submit a specific question via [email protected]. Commission disputes route to Betsy. Do not quote specific commission amounts or make commitments about payment timing without Betsy confirming.

Tag State Reference
Exact Spelling Required

Tags are case-sensitive. A typo creates a new tag and breaks automation routing. Copy/paste from this page; never type from memory.

Cancellation and Termination Tags
TagApplied ByApplied WhenEffect
TA Cancelled - Pending CancellationKajabi Automation 1Immediately on cancellation clickSignals access is still active but cancellation is in flight. Removed when billing period ends.
TA CancelledKajabi Automation 2End of billing periodAccess fully revoked. Triggers Zap 4 (MyAtlas deactivation).
TA Cancelled - Failed PaymentKajabi (native payment failure)Payment retry window exhaustedAccess revoked. Triggers Zap 5 (MyAtlas deactivation).
TA TerminatedBati (manual)Termination for cause decision executedFull tag sweep + offer revocation via Automation #28. Triggers Zap 6 (MyAtlas block). Cannot auto-rejoin.
TA Active (Rejoined)Kajabi TA Active Rejoined AutomationCancelled agent purchases againClears all cancelled tags, restores TA Active. Triggers Zap 3 (MyAtlas reactivation).
Tags Preserved vs. Removed by Scenario
TagSelf-CancelFailed PaymentTermination for Cause
TA ActiveRemovedRemovedRemoved (sweep)
TA Active (Rejoined)RemovedRemovedRemoved (sweep)
onboard-scheduledRemovedRemovedRemoved (sweep)
idv-verifiedPreservedPreservedRemoved (sweep)
onboarding completePreservedPreservedRemoved (sweep)
academy-completePreservedPreservedRemoved (sweep)
first-bookingPreservedPreservedRemoved (sweep)
agent-referredPreservedPreservedRemoved (sweep)
dual-agencyPreservedPreservedRemoved (sweep)
agent-vetPreservedPreservedRemoved (sweep)
Zap Reference
Zap 3
Rejoiner: Reactivate MyAtlas Account
Trigger: Kajabi tag added: TA Active (Rejoined)
Action: POST to JourneyFuse with reactivation_flag: true — reactivates the agent's existing MyAtlas account
Pattern: OAuth + Kajabi contact lookup + JF POST
Note: Pending Tim Peterson confirmation that reactivation_flag is the correct field name. May need update after Tim responds.
Confirmed working — May 26, 2026 (field name pending Tim)
Zap 4
Self-Cancel: Deactivate MyAtlas Account
Trigger: Kajabi tag added: TA Cancelled
Action: POST to JourneyFuse with deactivation_flag: true
Pattern: OAuth + Kajabi contact lookup + JF POST
Confirmed working — May 26, 2026
Zap 5
Failed Payment: Deactivate MyAtlas Account
Trigger: Kajabi tag added: TA Cancelled - Failed Payment
Action: POST to JourneyFuse with deactivation_flag: true
Pattern: OAuth + Kajabi contact lookup + JF POST
Confirmed working — May 26, 2026
Zap 6
Termination for Cause: Deactivate and Block MyAtlas Account
Trigger: Kajabi tag added: TA Terminated
Action: POST to JourneyFuse — deactivates and blocks the agent's MyAtlas account. Unlike Zaps 4 and 5, this blocks automatic rejoin at the JF level.
Pattern: OAuth + Kajabi contact lookup + JF POST
Bati-only: This Zap fires only when Bati applies the TA Terminated tag.
Confirmed working — May 26, 2026
Escalation Summary
When to Escalate and to Whom
Bati: All termination for cause decisions and execution. Open bookings at termination. Any rejoin request from a terminated agent. Any situation Donna cannot resolve independently with a standard self-cancel or failed payment case.
Melissa: Refund requests of any kind. Chargeback or bank dispute notifications. Termination decision (Bati executes; Melissa decides).
Betsy: Commission payout questions at cancellation. Any dispute about what was earned or paid before termination date.
Tim Peterson ([email protected]): If MyAtlas is not deactivated after Zap 4, 5, or 6 fires. Check Zap task history in Zapier first; if the Zap ran successfully and MyAtlas is still active, contact Tim directly.
Atlas Coast Travel Group — Cancellations & Terminations SOP v1.0 — May 26, 2026 — Internal use only MyAtlas SOP