Rollout guide

Use this playbook to launch Trame for a client with clear checkpoints, approvals, and operational readiness.

1) Prepare the workspace

• Create a dedicated workspace for the client; set at least two Owners.
• Add Admins (delivery leads) and Members (operators) as needed.
• Align naming: workspace name/slug should match the client’s environment.

2) Connect systems

• Identify which systems are in scope (email, chat, ERP/CRM, ticketing).
• Connect required toolkits and confirm they show Connected.
• Document connector scopes and who approved access on the client side.

3) Define the bottleneck and workflow

• Capture the business problem in plain language with the client.
• Generate a workflow draft and refine steps, required details, and constraints.
• Keep the workflow in Draft while you add required IDs, emails, and URLs.

4) Test in Draft/Pilot

• Run manual tests to validate each step and outputs.
• Switch to Pilot to test trigger-based runs with approvals on.
• Ensure approvers understand what “Approve” will execute (steps/tools).

5) Go Live

• Confirm connector health, trigger registration, and required details are in place.
• Promote the workflow to Live once the client signs off.
• Share a rollback path: pause the workflow, disable triggers, or disconnect the connector if needed.

6) Monitor and improve

• Watch early runs in Runs and Audit. Track failures and suggested improvements.
• Revisit approvals: keep sensitive workflows in Pilot even after go-live if risk is high.
• Update the workflow with client feedback and re-run tests after changes.

7) Handover to client teams

• Provide the client with role guidance (Owner/Admin/Member) and escalation paths.
• Document which workflows are Live/Pilot, their triggers, and data they touch.
• Establish a cadence (weekly/biweekly) to review run health and connector status.