Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

AI Automation Society

206.4k members • Free

AI Automations Unlimited

32 members • Free

ACA

2.9k members • Free

Imperium Academy™

30.1k members • Free

AI Automation Agency Ninjas

18.7k members • Free

North Eden Community

265 members • Free

High-Ticket & Info Marketing

3.6k members • Free

Paid Ad Secrets

17.9k members • Free

Creators

16k members • Free

1 contribution to AI Automations Unlimited
The best way to manage multiple snapshots and bots
Snapshots are a little bit of magic Install them into your agency account and then push them through to a subaccount and you can magically have whole new workflows, forms, web pages and more. But sometimes it can be confusing. There's often a question about whether one snapshot will conflict with another and what will happen. And sadly it is possible if you are getting snapshots from different places. But I wanted to share some details about how I look/think about snapshots when I create them and build my bots. 1. I identify what custom fields and values I need for the bot, like a field for conversation history, or the first message to be sent 2. I create them with a naming structure that reflects the bot like "Reputation Convo History" or "Demo Tool - First Message" 3. I create folders for the custom fields and values 4. I repeat the same process for workflows - separate naming for each bot to minimise conflicts This way, I can have multiple bots installed into the same subaccount for a client without any conflicts. Hope it helps!
0 likes • 14d
I quickly ran into the same issue! I'm wondering, when someone is creating a snapshot, why not create it with tags and custom values already pre-names in an organized fashion that way? 🤔
0 likes • 14d
@Philip Wride you're on the ball mate!
1-1 of 1
Cesar Romo
1
5points to level up
@cesar-romo-9198
Act as if you had no limitations

Active 15h ago
Joined Nov 17, 2025
Fort Worth, TX