Transferring an Agent
Sometimes an agent needs to change hands — for example, you built WhatsApp Reminder for a client and now want it to live in their organization. Transferring an agent moves it from one organization to another, cleanly and with the right safety checks. This page walks through how it works.
What transferring does
A transfer moves an agent from a source organization (where it lives today) to a destination organization (where you want it to live).
The most common reason is handover: an agency builds an agent and then transfers it to the client's own organization so the client owns it going forward, including its credit usage and billing.
Important: a transfer is a real move, not a copy. After a successful transfer the agent no longer appears in the source organization — it lives entirely in the destination.
Who can transfer an agent
The person making the request must be an Owner or Admin in the source organization. Builders, Members, and Billing users do not see the Transfer Agent option.
Requirements
Before a transfer can complete, all of these must be true:
| Requirement | Why |
|---|---|
| Requester is Owner or Admin in the source organization | Only they may give an agent away. |
| Requester has Owner, Admin, or Builder role in the destination organization | You can only send an agent somewhere you actually belong and can work. |
| A destination organization is selected | The system needs to know where the agent is going. |
| Contributors without a role in the destination | Any agent contributor who does not have Owner, Admin, or Builder in the destination organization will be removed during the transfer. |
Warning: that last point matters. If a contributor isn't part of the destination organization (with a suitable role), they lose access to the agent once it moves. Plan ahead so the right people keep their access.
Where to find it
Open the Organization page → click your organization → open the Agents tab → on the agent's card, click Transfer Agent. (This button only appears for Owners and Admins.)
The transfer page shows:
- The agent's information (so you confirm you're moving the right one).
- A requirements info box restating the rules above.
- An organization selector — a radio list of organizations you could transfer to. Eligible destinations are selectable; ineligible ones are shown disabled with a No eligible role label (meaning you don't have Owner/Admin/Builder there).
The transfer flow
- On the transfer page, select the destination organization from the radio list.
- Click Transfer Agent.
- A Transfer Validation dialog appears. It runs and displays checks:
- Source-org role check — confirms you are Owner/Admin in the source.
- Destination-org role check — confirms you have Owner/Admin/Builder in the destination.
- Per-contributor list — each current contributor is marked Will retain access or Will be removed. If anyone will be removed, a warning is shown so there are no surprises.
- Review the results. Click Confirm Transfer — this button is only enabled when all checks pass.
- On success you are taken to the destination organization's Agents tab, where the agent now lives.
Worked example
Tim Marketing Acme built the WhatsApp Reminder agent for Sehat Clinic and is ready to hand it over. Dina, an Admin at Acme, is also a Builder in Sehat Clinic's organization.
Dina opens Acme's organization → Agents tab → the WhatsApp Reminder card → Transfer Agent. She selects Sehat Clinic from the radio list (it's selectable because she's a Builder there), then clicks Transfer Agent.
In the Transfer Validation dialog both role checks pass. The contributor list shows dr. Budi as Will retain access (he's a Builder in Sehat Clinic too), while a temporary helper who isn't part of Sehat Clinic is marked Will be removed. Dina clicks Confirm Transfer, and the agent now appears under Sehat Clinic's Agents tab.
Next step
Continue to Audit Trail.