Docs · Agents
Atlas, the omnichannel agent.
Atlas is the coordinator. He doesn't send anything himself, he decides who sends what next when a contact is moving through a multi-channel flow. Mira opens on LinkedIn, Eli emails, Vance calls, and Atlas threads the three so no prospect gets hit twice and nobody hounds someone who's already replied.
Quick facts
- Channel
- Whichever channel the next step calls for
- Plan tier
- Studio and Agency only
- Lives at
- /dashboard/team/atlas
- Engine
- Flow templates compiled to nodes/edges, executed on a cron tick
- Hand-off trigger
- Reply, opt-out, or booked meeting on any channel
- Setup time
- Whatever the underlying channels need first
What Atlas decides
Atlas reads the active flow, looks at where each contact is in the sequence, and decides for every cron tick whether to advance, wait, or stop. Advance means firing the next step (Mira, Eli, or Vance, whichever the template specifies). Wait means the cooldown between steps hasn't elapsed yet. Stop means the contact replied, opted out, or booked, no further sends from any channel for that row.
The four built-in templates
- Email + LinkedIn. Email first, then a connection note, then a LinkedIn follow-up, then a final email. Best for SaaS prospects with strong work-email coverage.
- Email + Call. Email open, two email follow-ups, then Vance calls. Best for higher-ticket lists where a phone conversation closes the loop.
- LinkedIn + Call. Connection, opening message, then Vance calls accepted-and-quiet contacts. Best for prospect lists without solid email coverage.
- Full omnichannel. Email, LinkedIn, call, in that order with cooldowns between, the most comprehensive of the four. The right pick when you want every available channel to fire.
Pick a template from the Omnichannel modal on the dashboard, customize the steps, hit Launch. Atlas instantiates the flow, enrolls the contacts, and the cron ticks the rest.
How Atlas avoids double-touch
- Per-contact state, not per-channel. Atlas tracks where each contact is across the whole flow, so when one channel logs a reply the others go quiet for that row, even if their step is already queued.
- Graceful skips. If an email account is in auth-failed, Atlas parks the email step until you reconnect, the rest of the flow keeps moving on the channels that still work.
- No duplicate enrollment. The same contact can't be enrolled in the same flow twice, the engine de-dupes at insert time.
What Atlas needs to wake up
Atlas only runs when more than one channel is in play, single-channel work belongs to the specialist that owns it. Concretely that means you need at least two of email, LinkedIn, and cold call wired up before launching a flow that hits more than one. Three of the four templates include an email step, so in practice an email account plus one other channel is the minimum that gets you to a Launch button.
Keep reading
Need help?
Ciela can walk you through any step. Or write to support@ciela.ai and we'll jump on the connection with you.