JF fires its own "Thank you for your submission" email from [email protected] when a lead is received. This conflicts with Atlas Coast's own client confirmation email. Tim has been asked to disable this. Until he confirms it is off, clients may receive two confirmation emails. Do not send a manual third. Track this as an open item with Tim.
Kajabi handles everything client-facing: confirmation email, 24-hour follow-up sequence, 30-day feedback sequence, and internal Missive alert. JF handles the lead record, assignment, and partner notification. Kajabi's Missive alert is what tells your team to go work the JF Unassigned view.
| Element | Value |
|---|---|
| Trigger | Kajabi — New Form Submission — Atlas Booking Form (ID 2149574722) |
| Action | Webhooks by Zapier — POST |
| POST URL | https://myatlasgo.com/api/forms/atlas-28b6fe |
| Payload type | JSON |
| Critical domain rule | Must POST to myatlasgo.com domain. Posting to journeyfuse.com trips the bot check and submissions will not go through. |
| JF JSON Key | Maps From Kajabi Field | Notes |
|---|---|---|
first_name | First Name | |
last_name | Last Name | |
email | ||
phone | Phone Number | |
destination | Where do you want to go | |
notes | Budget question field | JF budget field is a fixed dropdown. Free-text budget rides in notes. |
Fire one test submission through atlascoasttravel.com/book. Confirm the lead appears in the JF Unassigned view under Leads. Tim Peterson confirmed he will verify the test on his end when notified.
The Missive alert (from Kajabi Email 7B to [email protected]) tells your team a new lead has arrived. The Unassigned view in MyAtlas is where you work it.
- 1Log into MyAtlas admin at journeyfuse.com
- 2Go to Leads in the left nav. The Unassigned view is a filter at the top showing only leads waiting to be picked up, with a live count.
- 3Each row has a one-click Assign button. Click it, select the Booking Partner, and set the commission split if it differs from the default (80/20 on Atlas-referred leads).
- 4The partner is notified instantly via email with Accept and Decline buttons, plus a simultaneous in-app alert.
All MyAtlas admin accounts can see the Unassigned view. Owner accounts (Melissa, Bati, Kelley, [email protected]) all receive lead alerts. Bati and Kelley are the primary assigners day to day.
| Lead Type | Split | Set At |
|---|---|---|
| Atlas-delivered lead (first booking from that client) | 80% partner / 20% Atlas Coast | Assignment in JF Unassigned view |
| Partner's own-sourced client | 90% partner / 10% Atlas Coast | N/A — not an Atlas lead |
| Returning client (second+ booking from same Atlas-referred client) | 90% partner / 10% Atlas Coast | N/A — partner earned that relationship |
Not every lead will come through the /book form. Clients sometimes email or call directly.
Option A (preferred): Gather the client's basic info and submit the /book form on their behalf, same as email leads above.
Option B: Create the lead manually inside MyAtlas. Go to Leads in the left nav, click Add Lead (or equivalent), enter the client details. The manually created lead follows the same assignment and notification logic as form-submitted leads.
| Action | What Happens | Staff Action |
|---|---|---|
| Partner accepts | Lead locks to them. Client relationship is theirs. No further assignment needed. | None |
| Partner declines | Lead drops back into the Unassigned view, flagged for reassignment. | Bati or Kelley reassigns to the next available Booking Partner. |
| Partner does not respond within 24 hours | Lead is reassigned. Per Partner expectations, 24-hour response is required. Repeated misses are grounds for removal from the program. | Bati or Kelley reassigns. Track the miss. Three misses = flag for Bati review. |
Booking Partners agreed to this at acceptance. A lead that receives no response within 24 hours is reassigned without exception. If a partner is going to be unavailable they must notify Bati or Kelley in advance so leads can be held or rerouted. This is not a courtesy — it is a program requirement in the ITA.
- 1Check Zapier task history for the /book Zap. Confirm whether the POST succeeded or failed.
- 2If the Zap failed: check that the POST URL is
https://myatlasgo.com/api/forms/atlas-28b6fe(myatlasgo.com domain, not journeyfuse.com). If the domain is wrong, update the Zap. - 3If the Zap ran successfully but the lead is not in JF: contact Tim at [email protected] with the test submission timestamp and Zap task ID.
- 4In the meantime, create the lead manually in MyAtlas so the client is not left waiting.
