Give a new customer a clear kickoff

A signed customer needs a smooth transition from sales to the person responsible for delivery. Use the won opportunity to prepare and assign that first checklist.

Before you start

Use an authorized workspace with Client onboarding and Overdue commitments enabled in Plugins, a won opportunity, and valid task assignees. These plugins start disabled. Confirm the source opportunity belongs to the customer you intend to onboard.

Explore the fictional workspaces to see the shared interface. There is no dedicated demo for this industry; the example adapts existing capabilities rather than claiming a preconfigured industry product.

Work through this example

A fictional software customer has signed for an implementation. The team needs an administrator, a sample dataset and an agreed first workflow.

Prepare. Create tasks for administrator confirmation, approved data access and the first workflow’s acceptance criteria.

Assign. Name the delivery owner and set preparation dates relative to the agreed kickoff.

Check. Use the intended account and sample record to verify the first workflow before recording the handoff as complete.

Complete the workflow

1. Open Pipeline and inspect the won opportunity, customer and agreed scope.

2. Open Client onboarding and select that opportunity. Prepare these tasks: Assign the customer owner; confirm setup requirements; schedule a kickoff discussion.

3. Give each task a description, due date and valid assignee. The plugin accepts one to ten tasks in a plan.

4. Choose Review workflow, then Request approval. Check the exact owners and dates before selecting Approve & create tasks.

5. Inspect the execution result, then open the created tasks in Tasks & approvals. Run Overdue commitments later to review tasks whose due dates have passed.

Check the result

An onboarding checklist with clear ownership and dates. The tasks retain their source opportunity, and Tasks & approvals shows their saved state. Checklist creation is the start of delivery; update each task as the customer work happens.

Adapt it for your business

Add a customer-success App when milestones and adoption reviews need their own records.

For a coded variation, use Build an extension and include this example’s decision, owner and completion check in your development brief. Keep customer identity and task history in the shared services.

What to check

If the source or an assignee changed, correct the input and prepare a fresh preview. For an uncertain execution result, inspect the original receipt before retrying with the same request identity. Confirm the existing tasks before submitting another checklist.

Plugins must be enabled for their operations to run. Hosted infrastructure and connected providers may have costs; AI conversations use your configured model. Keep each human decision required by the action’s policy, and verify the result in the source screen before relying on it.