Configure, test, and activate Tiffany

Review the imported employee

Open the imported employee before enabling anything. Compare the profile with the import preview and resolve every warning. Confirm the employee belongs to the intended destination sub-account and has a clear internal owner.

• Review connector and plugin requirements without assuming a source connection exists.
• Review each generic playbook and remove any workflow the destination does not need.
• Review the disabled proactive schedule and choose the destination timezone, workdays, hours, interval, cooldown, and blackout dates.
• Keep channels unassigned until the Piece and destination memory pass testing.

Map connectors, apps, and Meta Ads

Lead360

Provides mapped CRM, conversation, opportunity, appointment, campaign, customer app, and reporting evidence.

E-Commerce

Provides mapped catalogue, service, membership, purchase, and customer activity records.

Automation Pieces

Provides destination workflow and run context after the administrator maps eligible workflows.

Sites Builder AI

Provides mapped sites, pages, funnels, forms, widgets, and campaign destinations.

No plugin required

Do not add an advertising or external plugin unless the destination support workflow requires it and its data access has been reviewed.

Add destination memory and learning

1. Open Memory Brain and review the pending collection guides created by the import.
2. Upload only current destination-owned knowledge into the appropriate folders.
3. Remove credentials, payment data, private notes, unnecessary personal data, and unsupported claims before review.
4. Approve the exact revisions and make them available through the normal snapshot workflow.
5. Create or update a Memory Set when the Piece should use a controlled subset.
6. Open the imported Piece, bind reviewed memory and the intended fresh Learning Collections, then save a new draft revision.

Validate and test in Arena

Validation checks the Piece contract. Arena testing checks how the draft behaves. Neither step proves that destination data, provider permissions, messages, prices, campaigns, or customer outcomes are correct.

• A website chat question handled by Tiffany Front Desk.
• An SMS or email campaign reply handled by Tiffany Lead Response.
• A Customer App booking that holds a selected slot until deposit or full payment succeeds.
• An internal report or campaign recommendation handled by Tiffany Operations with approval-gated effects.
• A request involving an unmapped payment, app, site, campaign, sender, or calendar resource, which Tiffany must stop and report.

Review the answer, cited evidence, tool trace, blocked operations, handoff behavior, and resulting draft. Correct the Piece or destination mapping and repeat the test before publication.

Publish and activate deliberately

1. Publish the reviewed Piece revision and record its owner and approval evidence.
2. Assign the published deployment to the imported employee.
3. Choose one controlled internal channel and run a final destination test.
4. Enable approved playbooks and schedules one at a time and verify their delivery destination.
5. Enable customer-facing channels, automations, app changes, campaign changes, or provider writes only after their separate consent, content, payment, and operational reviews pass.
6. Monitor early runs, approvals, errors, opt-outs, escalations, and business outcomes before expanding access.

Troubleshooting and safe removal

The archive fails validation

Download the official file again and compare its SHA-256 checksum. Do not edit the archive or change its internal files.

A connector or plugin needs review

The destination may not have the required provider, permission, feature, or resource. Connect an eligible destination account or disable the unneeded capability.

The Piece has no useful business context

This is expected until destination memory is reviewed, made available, bound to a new Piece revision, and tested.

A playbook or schedule does not run

Imported playbooks are generic and schedule blueprints remain disabled. Map resources, review the prompt and effect, choose an internal delivery channel, then enable the workflow deliberately.

Remove the imported kit

Disable channels, schedules, automations, and bindings first. Use the supported kit-removal action while the import ledger can still prove which draft resources were created. Later changes, shared use, publication, or run history can block automatic removal and require manual ownership review.