Become an Agent
Atlas Coast Travel Group — Staff SOP
MyAtlas Error Handling & Zap Failure Protocols
Owner: Bati (critical / high) · Kelley / Donna (medium / low) Last Updated: May 26, 2026 Version: 1.0
How the Error Handling System Works

Every Atlas Coast Zapier flow that touches MyAtlas has an automated error path. When a Zap fails, an alert email fires to [email protected] with the agent's name, email, Kajabi ID, and the action that failed. Missive routes it to the responsible team member. This SOP defines what to do when each alert arrives.

Urgency Color Key

CRITICAL Escalate to Bati immediately regardless of time of day — active access control issue or terminated agent with live access.
HIGH Agent is paying and has no access, or IDV/Dots is blocked. Resolve same business day.
MEDIUM Email or tag sync failure. Resolve within 1 business day.
LOW Cosmetic only — no access or payment impact. Resolve within 1 business day.

JourneyFuse Support

For any issue requiring JourneyFuse involvement, open a support ticket via Tools → Support in the left nav of your JourneyFuse account. 12-hour SLA, usually faster during business hours. Do not email Tim directly for urgent matters — the support ticket routes to multiple team members.

MyAtlas Admin Panel Capabilities

Navigate to Settings → Agents in your MyAtlas admin account. All six actions below are self-serve.

ActionWhereWho Can Do It
Create new agent recordSettings → Agents → Invite or Bulk InviteBati, Kelley, Donna
Reactivate deactivated agentSettings → Agents → find agent → Reactivate buttonBati, Kelley
Deactivate agent (reversible)Settings → Agents → find agent → Deactivate toggleBati, Kelley
Block agent (permanent flag)Settings → Agents → find agent → Block toggleBati only
Apply badge to agent profileSettings → Agents → find agent → toggle badge onBati, Kelley, Donna
Remove badge from agent profileSettings → Agents → find agent → toggle badge offBati, Kelley, Donna
Never Use the Remove Button for Active Deactivations

The Remove button in Settings → Agents is a permanent removal. An agent removed this way cannot be recovered if they later rejoin. Always use the reversible Deactivate toggle for self-cancels and payment failures. Only use Block for terminations for cause.

Critical Scenarios

Active access control issues. Escalate to Bati immediately regardless of time of day.

Zap 6 — Critical
Termination for Cause — Deactivation / Block Failed
Owner: Bati only
What happened: An agent was terminated for cause but their MyAtlas account was not deactivated and/or blocked. Terminated agent may still have live MyAtlas access. This is the highest-risk scenario.
⚠ Bati-Only Action — Escalate Immediately

Do not attempt this as another team member. Alert Bati immediately regardless of time of day. Do not contact the terminated agent under any circumstances.

  • 1
    Escalate to Bati immediately. Text, call, or WhatsApp — do not wait for email.
  • 2
    Bati: Go to MyAtlas → Settings → Agents → find the agent → activate the Deactivate toggle AND the Block toggle.
  • 3
    Separately confirm the agent's Kajabi product access has been revoked — check their tags and offer grants in Kajabi admin.
  • 4
    Document all actions with timestamps in the agent's Kajabi contact notes.
  • 5
    Do not contact the agent. All communication with terminated agents goes through Bati → Melissa → Jeannette if legal involvement is needed.
Zap 4 — Critical
Self-Cancel Deactivation Failed
Owner: Bati (primary), Kelley (backup)
What happened: An agent self-cancelled their membership but their MyAtlas account was not deactivated. Cancelled agent still has active MyAtlas access they should not have.
  • 1
    Go to MyAtlas → Settings → Agents → find the agent.
  • 2
    Activate the Deactivate toggle (reversible). Do NOT use the Remove button — they may rejoin later.
  • 3
    Confirm access is removed.
  • 4
    Add a note to the agent's Kajabi record: MyAtlas access manually deactivated [date] — Zap 4 failure
Zap 5 — Critical
Failed Payment Deactivation Failed
Owner: Bati (primary), Kelley (backup)
What happened: An agent's subscription was cancelled after failed payment but their MyAtlas account was not deactivated. Agent with lapsed payment still has active MyAtlas access.
  • 1
    Go to MyAtlas → Settings → Agents → find the agent.
  • 2
    Activate the Deactivate toggle (reversible).
  • 3
    Confirm access is removed.
  • 4
    Add a note to the agent's Kajabi record: MyAtlas access manually deactivated [date] — Zap 5 failure
High Urgency Scenarios

Agent is paying and has no access, or IDV/Dots is blocked. Resolve same business day.

Zap 1 — High
New Agent Signup to MyAtlas Failed
Owner: Bati or Kelley
What happened: A new agent completed their purchase but their MyAtlas record could not be created. Impact: Agent has no MyAtlas access. All future Zaps for this agent (onboarding, badges, payout) will also fail until resolved.
  • 1
    Go to MyAtlas → Settings → Agents → Invite.
  • 2
    Manually create the agent record using the name, email, and Kajabi ID from the alert email.
  • 3
    Confirm the record was created successfully.
  • 4
    Add a note to the agent's Kajabi record: MyAtlas record created manually [date] — Zap 1 failure
  • 5
    Do not contact the agent until access is confirmed.
Zap 3 — High
Rejoiner Reactivation Failed
Owner: Bati or Kelley
What happened: A returning agent completed their repurchase but their MyAtlas account could not be reactivated. Agent paid but has no access.
  • 1
    Go to MyAtlas → Settings → Agents → find the agent.
  • 2
    Click the Reactivate button to restore their access.
  • 3
    Confirm access is restored and they can log in.
  • 4
    Add a note to the agent's Kajabi record: MyAtlas manually reactivated [date] — Zap 3 failure
  • 5
    Do not contact the agent until access is confirmed.
Zap 10 — High
First Booking IDV or Dots Failed
IDV owner: Bati  |  Dots owner: Betsy
What happened: An agent logged their first booking but identity verification and/or payout account setup could not be triggered. Impact: Agent cannot be verified or receive commission payouts until resolved. Complete both steps regardless of which triggered the alert — do not assume one succeeded if the other failed.
  • 1
    For IDV failure (Bati): Log in to ID Analyzer and manually create a DocuPass session for this agent. Send them the verification link via [email protected]. Add the idv-pending tag to their Kajabi record.
  • 2
    For Dots failure (Betsy): Log in to Dots and manually send this agent a payout invite using the email in the alert.
  • 3
    Add a note to the agent's Kajabi record confirming manual resolution with date.
Medium Urgency Scenarios

Email or tag sync failures. Resolve within 1 business day.

Zap 12 — Medium
Kajabi Email Change to MyAtlas Failed
Owner: Donna
What happened: An agent updated their email in Kajabi but the change was not synced to MyAtlas. Impact: Email mismatch between systems. Future onboarding completion matching (Zap 2b) will fail for this agent.
  • 1
    Log in to MyAtlas → Settings → Agents → find the agent by their old email or Kajabi ID.
  • 2
    Manually update their email to match the new email shown in the alert.
  • 3
    Confirm the update saved correctly.
  • 4
    Add a note to the agent's Kajabi record: MyAtlas email manually synced [date] — Zap 12 failure
Zap 13 — Medium
MyAtlas Email Change to Kajabi Failed
Owner: Donna
What happened: An agent updated their email in MyAtlas but the change was not synced to Kajabi. Impact: Email mismatch between systems. Future automated flows will break for this agent.
  • 1
    Go to the agent's Kajabi contact record.
  • 2
    Manually update their email to match the new email from MyAtlas shown in the alert.
  • 3
    Confirm the update saved correctly.
  • 4
    Add a note to the agent's Kajabi record: Kajabi email manually synced [date] — Zap 13 failure
Zap 11 — Medium
eWebinar Registration Tag Failed
Owner: Kelley or Donna
What happened: An agent registered for an onboarding session but the onboard-scheduled tag was not applied in Kajabi. Impact: Internal tracking gap — agent may not be in the correct email sequence.
  • 1
    Go to the agent's Kajabi contact record.
  • 2
    Manually add the onboard-scheduled tag.
  • 3
    Verify they are enrolled in the onboarding email sequence.
Low Urgency Scenarios

Cosmetic only — no access or payment impact. Resolve within 1 business day.

Zaps 7, 8, 9 — Low
Badge Grant Failed
Owner: Kelley or Donna
What happened: An agent earned a badge (Academy Graduate, Coach, or Booking Partner) but it was not applied to their MyAtlas directory profile. Impact: Agent's public directory profile does not show their earned badge. Cosmetic only — no access or payment impact. No need to notify the agent.
  • 1
    Go to MyAtlas → Settings → Agents → find the agent.
  • 2
    Toggle the relevant badge on:
    • Academy Graduate → academy-graduate
    • Coach → coast-coach
    • Booking Partner → coast-partner
  • 3
    Confirm the badge appears on their public directory profile.
Zaps 8b, 9b — Low
Badge Revocation Failed
Owner: Kelley or Donna
What happened: A coach or booking partner's role was removed but the badge was not revoked from their public directory profile. They still appear as an active coach or partner. Impact: Public-facing inaccuracy on the agent directory.
  • 1
    Go to MyAtlas → Settings → Agents → find the agent.
  • 2
    Toggle the relevant badge off:
    • Former Coach → toggle off coast-coach
    • Former Partner → toggle off coast-partner
  • 3
    Confirm the badge no longer appears on their directory profile.
Escalation Quick Reference
ScenarioZapPrimaryEscalate To
Terminated agent has active accessZap 6BatiNobody — Bati handles directly
Cancelled agent has active accessZap 4BatiKelley
Lapsed-payment agent has active accessZap 5BatiKelley
New agent has no MyAtlas accessZap 1Bati or KelleyMelissa if unresolved
Returning agent has no accessZap 3Bati or KelleyMelissa if unresolved
IDV failed at first bookingZap 10BatiMelissa
Dots failed at first bookingZap 10BetsyBati
Email sync failed (either direction)Zaps 12 & 13DonnaBati or Kelley
eWebinar tag missingZap 11Kelley or Donna
Badge grant or revocation failedZaps 7–9, 8b, 9bKelley or Donna
When to Contact JourneyFuse Support

If any admin panel action fails or you cannot locate an agent's record, open a support ticket via Tools → Support in the left nav of your JourneyFuse account. Include the agent's name, email, and Kajabi ID. Do not email Tim directly for urgent matters. 12-hour SLA, usually faster during business hours.

Atlas Coast Travel Group — MyAtlas Error Handling SOP v1.0 — May 26, 2026 — Internal use only MyAtlas SOP →