The test
Can this value be the same sentence in every sub account, or is it a
record ID that only exists inside one of them?A tag name, a script line, a retry schedule: same everywhere. A calendar, a
pipeline stage, a transfer number: a different record in every sub account.
Shared, so the parent wins
Change these on the parent and every linked project gets them:
Workflow structure is shared for a reason worth naming: if the graph could
differ per project, those projects would be separate campaigns wearing the same
name.
Local, so the parent never touches them
Calendars, transfer numbers and pipeline stages are
bindings: they get connected per project,
and a project cannot go live until they are.
Phone numbers, live status and timezone are simply local. They are not bindings
and they never appear in a binding report.
Two answers this gives you
“I changed the script on one project and it went back.” Working as designed. The script is shared, so the parent is the only place it can be changed. Change it there and it reaches everyone. “I want this one client to say something different.” Then it is not the same campaign. Either the difference belongs in something already local, or that client needs its own campaign outside the master agent.One current limit
Advanced transfer routing is not supported on master agents. Routes are stored on the shared agent, so each project cannot have its own. A master agent that transfers should use the simple{{transfer_number}}
destination, with one bound transfer number per sub account.
In the API
- Get master agent state shows the parent and every linked project
- Get campaign on a child shows the synced fields beside the local ones
- Connecting each project’s own assets covers the local side