Reuse your best AI agents across client accounts

A reusable foundation with room for each client

An assistant bundle contains the portable settings needed to start configuring a new copy. The review shows current settings and dependencies, including configured voice and chat waits. Your team can see which tools will be shared, copied as definitions, connected to existing destination tools, or left out.

Destination bindings let you choose an active native calendar in the receiving account and map eligible custom tools to existing tools there. This is useful when two businesses follow the same conversation pattern but use different operational resources.

The new copy starts disabled. Source credentials, alert recipients, provider connections, phone assignments, and the source account’s booking references are cleared rather than carried into the receiving account. Your team completes the destination setup before enabling and publishing.

That gives an implementation team a repeatable handoff: reusable assistant configuration, a visible review of dependencies, and a separate decision about when the destination is ready.

One appointment approach, several local businesses

Consider an illustrative home services agency that manages separate Assistable accounts for several local operators. Its team has developed an appointment assistant that explains the service, asks the right qualifying questions, and keeps the conversation focused.

For a new location, the team wants to reuse those instructions and conversation settings. The new operator has its own calendar, service information, phone routing, and business tools. Those choices need local attention even when the overall customer journey is familiar.

The team imports the assistant into the new account, reviews the portable settings, and selects that location's active native calendar. If an eligible destination tool already exists, the team connects it during review. It then reconnects the appropriate knowledge, checks the instructions for local details, and configures the receiving account's phone assignments.

The result is a draft prepared for that business. A test conversation and a booking check can then establish whether the local setup behaves as intended before customer traffic reaches it. The import itself does not perform those tests.

For teams delivering AI agents as an agency, this makes the boundary between reusable work and client setup easier to see.

How to prepare a reviewed import

Start with a source assistant whose configuration you understand and a destination account you are authorized to manage.

1. Open the import in the destination account. From Assistants, open the import workflow and enter the source assistant IDs. Review whether custom tools should be included. Importing custom tools requires access to their source account.
2. Choose Preview import. Read the current configuration and dependency notes for each assistant. Check the prompt, voice and chat settings, configured waits, and tool handling. The preview reflects current source settings, so use it to assess what you are importing now.
3. Select destination calendars and tools. Under Destination calendars and tools, choose the receiving account's active native calendar where appropriate. Map eligible source tools to suitable existing destination tools. If no suitable resource is available, leave that setup for after import. Changed selections require a fresh preview.
4. Import the reviewed assistants. Confirm the reviewed selection to create disabled copies. Open each copy and work through its destination setup notes. Review instructions, reconnect knowledge or an Agent Flow when needed, and configure credentials, endpoints, recipients, phone routing, and other local settings where applicable.
5. Review, test, and activate. Check the destination configuration and test the customer journey you intend to use. Confirm that the right calendar, business data, and handoff receive the result. Complete the explicit enable and publish step when the assistant is ready for service.

Keep the local review specific. An appointment assistant needs a booking check; a service lookup needs a check of the returned information. A successful import establishes that the copy was created. Your deployment review establishes whether it is ready for its audience.

Carry the approach forward as your team grows

Workspace defaults use the same reviewed bundle approach for new assistants. New defaults remain disabled until destination setup has been reviewed and activation succeeds. Existing assistants are not automatically migrated by this process.

Treat your source assistants as maintained starting points. When your team improves an instruction or adjusts conversation timing, review the current configuration before the next import. Each receiving account still deserves its own setup and testing.

If the agent uses an Agent Flow, include reconnecting that flow in the destination review. If a customer interaction would benefit from a visual result, Card Builder provides a separate way to present connected tool results as branded cards. Review those connections within their own setup workflows.

Questions teams ask about reusable assistant deployments

Does importing an assistant make it live immediately?

No. Imported assistants start disabled for destination setup. Review the receiving account's configuration, test the intended workflow, then explicitly enable and publish when ready.

Which calendars and tools can I connect during review?

You can choose authorized, active native calendars in the destination account and eligible existing custom tools. The picker is not a general connector for every external booking system. Copied tool definitions can still need destination credentials, endpoints, recipients, or other configuration.

Does this copy the whole account or preserve a historical template?

The bundle carries portable assistant configuration. Phone numbers, credentials, source recipients, and the source account’s booking references do not transfer. Knowledge and Agent Flows may need reconnection. The preview shows current settings, not an immutable historical template.

Is the same import workflow available in Assistable Direct?

The reviewed batch workflow with destination bindings described here applies to standard accounts. Assistable Direct uses a separate workflow for importing one assistant at a time. Confirm the workflow for your deployment with the Assistable team.