These platforms do NOT sync automatically. Zapier is the only bridge between them. Never assume a change in one platform has updated the other.
| Phase | Name | Platforms | Staff Action? |
|---|---|---|---|
| 1Purchase | Agent subscribes | Kajabi + Zapier (Zap 1) + JourneyFuse | None required |
| 2Onboarding | eWebinar + MyAtlas unlock | eWebinar + Zapier (Zap 11, Zap 2b) + JourneyFuse | Monitor chat during session windows |
| 3First Booking | First entry in MyAtlas | MyAtlas + Zapier (Zap 10) | None unless email mismatch |
| 4IDV | Identity verification | ID Analyzer + Zapier | Bati if manual review or 2nd failure |
| 5Active | Fully verified agent | Dots payouts flowing | None |
Every outbound Zap to JourneyFuse uses a 3-step pattern: (1) OAuth trigger, (2) Kajabi API contact lookup by email to retrieve stable contact_id, (3) POST to JF endpoint. Never use member_id in place of contact_id. They are different fields.
-
1Kajabi processes payment ($39/month Founders Rate or current rate). Agent subscribes to Travel Agent Monthly Hosting Fee offer. No manual action required.
-
2Tag
idv-not-startedapplied by Kajabi at checkout. Marks agent as pending IDV. No access restrictions at this stage. -
3Atlas Academy, Atlas Agent Dashboard, and Atlas Community all unlock immediately. Available the moment the transaction completes. No waiting for IDV or eWebinar. Dashboard is at atlascoasttravel.com/dashboard.
-
4Welcome email fires. Subject: "You're in. (And this email actually made it.) ✈️" Contains Dashboard link, Academy link, and onboarding CTA. Includes Liquid conditional blocks for SoT states (FL, CA, WA, HI) and dual-agency agents.
-
5Zap 1 fires. Creates the agent's record in JourneyFuse. Does NOT provision MyAtlas access. MyAtlas unlocks in Phase 2 after eWebinar completion.
Atlas Academy (full curriculum), Atlas Agent Dashboard, Atlas Community, Welcome email. MyAtlas is NOT yet available.
Kajabi automation "TA Active Rejoined" fires automatically when a purchase is detected on an account with any cancelled tag. Actions in order:
- Removes tags:
TA Cancelled,TA Cancelled - Failed Payment,TA Cancelled - Pending Cancellation - Applies tags:
TA Active,TA Active (Rejoined) - Sends rejoiner welcome-back email
- The
TA Active (Rejoined)tag triggers Zap 3, which reactivates the agent's MyAtlas account
Note: Tags preserved from prior membership (IDV, Academy, onboarding completion, first-booking) are not removed on cancellation, so returning agents skip already-completed steps.
Terminated agents cannot rejoin automatically. Requires manual review and approval by Bati. See Cancellations SOP.
Agent registers via atlascoasttravel.com/onboarding, which redirects to the live eWebinar registration link. Registration confirmations and all reminders are handled natively by eWebinar. No Kajabi action required for registration.
| Detail | Value |
|---|---|
| Format | Simulive (pre-recorded with live chat) |
| Runtime | 60 minutes |
| Schedule | Monday 6:00 PM ET / Wednesday 11:00 AM ET / Saturday 10:00 AM ET |
| Completion threshold | 80% attendance triggers all completion webhooks |
| Chat monitoring | Donna, Shiela, or Nicole monitor Chatbase admin panel during each session window |
| No-show handling | eWebinar sends replay link + re-register invite automatically. No manual action required. |
| Post-session questions | Agent replies to recap email, which routes to Missive for team follow-up |
Zap 11 triggers on eWebinar new registrant. Applies onboard-scheduled tag in Kajabi. This tag suppresses the 48-hour nudge email so the agent does not receive a reminder to register when they already have.
Fires automatically 48 hours after purchase if the agent does NOT have the onboard-scheduled tag. Subject: "Hey, don't forget your onboarding session." Reminds agent that MyAtlas (booking tools) unlock after onboarding. CTA to register.
Trigger: eWebinar attendee reaches 80% attendance threshold.
- 1OAuth authentication with Kajabi
- 2Kajabi API
/contactslookup by email — retrieves stablecontact_id - 3Path A: If contact found: Kajabi form submission fires, which applies
onboarding completetag and sends the "You're In" confirmation email - 4Path B: If NO contact found: Alert email fires to [email protected] with subject "Action Required -- Onboarding Completion Could Not Be Processed." Staff must manually locate agent in Kajabi and apply the
onboarding completetag. This is the only scenario that requires manual staff action in this phase.
eWebinar fires a second, independent webhook directly to JourneyFuse (Tim configures this URL in eWebinar). JourneyFuse provisions the agent's full MyAtlas account and sends login credentials directly to the agent. This webhook fires in parallel with Zap 2b -- neither waits for the other.
Known issue: Agent first name may not populate in the MyAtlas invitation email greeting. Flagged to Tim Peterson. Not a functional issue.
Agent has: Atlas Academy, Atlas Agent Dashboard, Atlas Community, and MyAtlas (full booking access). The onboarding complete tag is applied in Kajabi. No further action required until the agent logs their first booking in MyAtlas.
onboarding complete tag is missing in Kajabi.- 1Locate the agent in Kajabi by name or partial email (the alert email contains the name and eWebinar email address)
- 2Compare the eWebinar email in the alert to the email on the Kajabi contact record
- 3If emails differ: correct the email in Kajabi first, then apply the
onboarding completetag manually - 4If emails match but contact wasn't found: the agent may have purchased with a different email or the lookup timed out. Apply the
onboarding completetag manually and flag to Melissa for investigation
Triggered when the agent logs their first booking in MyAtlas. JourneyFuse fires a webhook to Zapier. Zap 10 runs three actions in parallel.
As of May 26, 2026, Phase 3 architecture is confirmed and all component zaps are confirmed working in isolation. Full end-to-end smoketest of Zap 10 with a real first-booking event is a pre-launch requirement. This section reflects confirmed architecture.
Action A — First booking email: Kajabi sends "You just made your first booking. Let's get you paid." email + a Communities DM celebrating the milestone and directing agent to check inbox for two items (IDV link and Dots invite).
Action B — IDV: ID Analyzer API creates a DocuPass session. ID Analyzer sends the verification link directly to the agent. (2-minute photo ID + selfie flow.)
Action C — Dots: Dots API sends payout setup invite to agent. Dots and IDV fire simultaneously. Dots does NOT wait for IDV to pass. Commissions take months to settle, so IDV issues will surface before any payouts are due.
Mismatch handling: If the JF booking email does not match any Kajabi contact, Zapier routes an alert to Donna for manual reconciliation.
- 1Locate agent in Kajabi by name or cross-reference with JF
- 2Manually apply
idv-verifiedtag in Kajabi to unblock the agent's commission flow - 3Flag the email discrepancy for correction on the Kajabi contact record
- 4Manually trigger ID Analyzer DocuPass via the ID Analyzer dashboard if the IDV link was not delivered. Send link directly to agent.
Agent receives a unique verification link via email from ID Analyzer. They complete a photo ID + selfie (~2 minutes). ID Analyzer fires a result webhook to Zapier, which routes based on the result.
For detailed IDV error handling protocols, see: IDV Error Handling Protocols (Notion)
- 1Zapier applies
idv-verifiedtag in Kajabi - 2IDV pass email fires: "You're verified. One more step coming your way." Agent directed to /idv-verified landing page.
- 3Zapier calls Dots API: payout invite sent directly to agent
- 1Zapier applies
idv-reviewtag in Kajabi - 2IDV review email fires: "Your identity verification is under review." Agent reassured nothing is wrong, booking is not affected.
- 3Agent directed to /idv-review landing page (pulsing amber clock)
- 4Missive task created for Bati: "IDV Manual Review Required -- [agent name]"
- 5Bati resolves within 1 business day: If approved: applies
idv-verifiedtag in Kajabi + fires Dots invite manually. If more info needed: emails agent directly from Bati's account.
- 1Zapier checks for
idv-failed-1tag: not present, so this is the first rejection. Appliesidv-failed-1tag. - 2ID Analyzer sends retry link automatically. No Atlas Coast email needed at this stage.
- 3Agent directed to /idv-failed landing page with common rejection reasons and retry checklist. Gold callout clarifies the retry link comes from ID Analyzer, not Atlas Coast.
- 1Zapier detects
idv-failed-1is already present. Appliesidv-failed-2tag. - 2Second failure email fires: "We're stepping in to help with your verification." Human is handling it, no action needed, within 1 business day.
- 3Missive escalation task created for Bati: "IDV 2x Rejection -- Manual Help Required -- [agent name]"
- 4Bati contacts agent personally to work through verification. On resolution: applies
idv-verifiedtag + fires Dots invite manually.
Agent has idv-verified tag and a Dots payout account. Fully active. No further onboarding steps required.
| Item | Detail |
|---|---|
| Commission split (self-sourced) | 90% to agent / 10% to Atlas Coast |
| Commission split (Atlas-referred leads) | 80% to agent / 20% to Atlas Coast |
| Pay dates | 1st and 15th of every month via Dots |
| Minimum payout threshold | $25. Balances below $25 roll forward and never expire. |
| Tax documentation | Handled by Dots automatically. 1099 issued by Dots if applicable. |
| Commission owner | Betsy (CFO). All commission reconciliation questions go to Betsy. |
| Missing commission report | Agent submits form at atlascoasttravel.com/missing. Routes to Betsy in Missive. |
Tags are case-sensitive and must match exactly. A typo creates a new tag and breaks automation routing. Copy/paste from this page; never type from memory.
| Tag | Applied When | Applied By | Purpose |
|---|---|---|---|
| idv-not-started | Purchase complete | Kajabi (at checkout) | Marks agent pending IDV |
| onboard-scheduled | eWebinar registration | Zapier (Zap 11) | Suppresses 48-hour nudge |
| onboarding complete | eWebinar 80% attendance | Kajabi native (via Zap 2b form) | Confirms onboarding done. Triggers MyAtlas access. |
| onboarding-no-show | eWebinar no-show | Zapier (form submission) | Routes to nudge follow-up |
| Tag | Applied When | Applied By | Effect |
|---|---|---|---|
| idv-verified | Accept OR Bati manual approval | Zapier or Bati | Agent fully verified. Dots invite fires. |
| idv-review | Manual review result | Zapier | Routes Missive task to Bati. 1 biz day SLA. |
| idv-failed-1 | First rejection | Zapier | Allows detection of second failure to route escalation. |
| idv-failed-2 | Second rejection | Zapier | Routes Missive escalation to Bati. No more auto retries. |
| idv-manual-review | Manual process initiated | Bati | Tracks manual IDV review in progress. |
| idv-manual-approved | Bati approves manually | Bati | Records manual approval decision. |
| idv-manual-rejected | Bati rejects manually | Bati | Records manual rejection decision. |
| Tag | Applied When | Effect |
|---|---|---|
| TA Active | All active agents | Core active status flag |
| TA Active (Rejoined) | Agent re-subscribes after any prior cancellation | Distinguishes rejoiners. Permanent -- never removed. Triggers Zap 3 (MyAtlas reactivation). |
| TA Cancelled - Pending Cancellation | Cancellation initiated | Access continues through end of billing period |
| TA Cancelled | Billing period ends post-cancellation | Access fully revoked. Triggers Zap 4 (MyAtlas deactivation). |
| TA Cancelled - Failed Payment | Payment retry window exhausted | Triggers Zap 5 (MyAtlas deactivation). |
| TA Terminated | Terminated for cause | Triggers Zap 6. All tags removed, all offers revoked. Cannot auto-rejoin. |
| Tag | Applied When | Purpose |
|---|---|---|
| first-booking | First booking logged in MyAtlas | Tracks booking milestone. Preserved on self-cancel. |
| agent-referred | Referral field filled at purchase OR via /referredme within 45 days | Tracks referral attribution. Triggers 25% referral bonus. |
| dual-agency | Agent indicates dual agency at purchase | Activates dual agency block in welcome email. |
| agent-vet | Agent identifies as existing travel agent | Informational. Preserved on self-cancel. |
| agent-new | Applied at signup for new agents | Segment tracking. |
| Tag | Zap | JF Badge Slug | Effect |
|---|---|---|---|
| academy-complete | Zap 7 | academy-graduate | Activates Academy Graduate badge on agent directory profile |
| Coach | Zap 8 | coast-coach | Activates Agent Success Coach badge on directory profile |
| Booking Partner | Zap 9 | coast-partner | Activates Atlas Coast Partner badge on directory profile |
idv-verified, academy-complete, onboarding complete, first-booking, agent-referred, dual-agency, agent-vet -- so rejoiners skip already-completed steps.
All tags are removed and all offers revoked when TA Terminated is applied. Terminated agents cannot auto-rejoin. Requires manual team review and approval. See Cancellations & Terminations SOP.
For any Zap failures not covered here, log into Zapier, find the failing Zap's task history, check the error message, and escalate to Melissa. Do not attempt to modify Zap logic without explicit instruction.
| Zap | Trigger | Action | Status |
|---|---|---|---|
| Zap 1 | Kajabi offer purchased (Travel Agent Monthly Hosting Fee) | POST to JourneyFuse: create agent record. No MyAtlas access granted at this step. | Confirmed |
| Zap 2b | eWebinar 80% attendance threshold | Kajabi OAuth + contact lookup + form submission = onboarding complete tag + "You're In" email. Error path: alert to hello@ if email not found. |
Confirmed |
| Zap 3 | Kajabi tag added: TA Active (Rejoined) |
POST to JourneyFuse: reactivate existing MyAtlas account. | Confirmed (pending Tim: reactivation_flag field name) |
| Zap 10 | JF first-booking webhook fires | Three parallel: (A) first booking email via Kajabi, (B) ID Analyzer DocuPass session, (C) Dots payout invite | Architecture confirmed; pre-launch real-event test required |
| Zap 10a | ID Analyzer accept webhook | Apply idv-verified tag, send IDV pass email, send Dots invite |
Confirmed |
| Zap 10b | ID Analyzer review webhook | Apply idv-review tag, send review email, create Missive task for Bati (1 biz day SLA) |
Confirmed |
| Zap 10c | ID Analyzer reject; idv-failed-1 NOT present |
Apply idv-failed-1 tag. ID Analyzer sends retry link automatically. |
Confirmed |
| Zap 10d | ID Analyzer reject; idv-failed-1 IS present |
Apply idv-failed-2 tag, send second failure email, create Missive escalation task for Bati |
Confirmed |
| Zap 11 | eWebinar new registrant | Apply onboard-scheduled tag in Kajabi |
Confirmed |
- 1Check Zap 10 task history in Zapier to confirm whether a DocuPass session was created for the agent's email
- 2If session was created: confirm agent's email address is correct, ask them to check spam folder
- 3If session was NOT created: manually trigger ID Analyzer DocuPass session via the ID Analyzer dashboard, then send the verification link directly to the agent
Commissions accumulate but cannot be released until Dots setup is complete. Atlas Academy covers Dots setup. If agent contacts support: direct them to check inbox/spam for the Dots invite, or escalate to Betsy to re-send.
Check Kajabi for onboarding complete tag. If present, JF direct webhook should have fired. Contact Tim Peterson at [email protected] to verify whether the MyAtlas account was provisioned and whether the agent received a login email. Check JF admin to manually verify.
For full MyAtlas access troubleshooting, see: MyAtlas Staff SOP
Alert email fires to support team. Manually apply onboarding complete tag directly in Kajabi on the agent's contact record. MyAtlas provisioning may already be complete via the JF direct webhook (those run independently).
Agent replies to their eWebinar recap email, which routes to Missive for team follow-up. Donna handles all standard post-session questions. Technical questions about MyAtlas escalate per the MyAtlas SOP.
| Task | Owner | Platform |
|---|---|---|
| Purchase + provisioning (Phase 1) | Automated | Kajabi, Zapier, JF |
| eWebinar chat monitoring during session windows | Donna / Shiela / Nicole | eWebinar / Chatbase admin |
| Onboarding completion (Phase 2) | Automated | Zapier, JF, Kajabi |
| Zap 2b error: email not found in Kajabi | Donna | Kajabi, Missive |
| First booking + IDV / Dots trigger (Phase 3) | Automated | Zapier, ID Analyzer, Dots |
| First booking email mismatch | Donna | Kajabi, Missive |
| IDV manual review (Result B) | Bati | ID Analyzer, Kajabi, Missive |
| IDV second rejection (Result C x2) | Bati | ID Analyzer, Kajabi, Missive |
| Commission reconciliation (1st and 15th) | Betsy (CFO) | Dots, QBO, Missive |
| Missing commission reports | Betsy (CFO) | Missive, Dots, JF |
| Cancellation flow | Automated | Kajabi |
| Termination for cause | Melissa + Bati | Kajabi, Zapier, JF |
| Rejoiner -- terminated agent seeking to return | Bati | Kajabi, JF |
| JF / MyAtlas integration issues | Tim Peterson | JF, Zapier |
