> ## Documentation Index
> Fetch the complete documentation index at: https://docs.custral.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Implementation

> Onboard new customers with tasks, workflows, and shared pages.

Implementation teams use Custral to run a repeatable onboarding flow for every new customer. The project record, its task checklist, the automations that move it forward, and the customer-facing pages all live in the same workspace.

<Note>Custral's [Playbooks](/comms/playbooks/overview) are live-call scripts, not onboarding runbooks. To model a repeatable onboarding process, use an object with staged status plus [tasks](/team/tasks/overview) and [workflows](/automation/workflows/overview), as below.</Note>

## What implementation runs on

<CardGroup cols={2}>
  <Card title="An onboarding object" icon="cube" href="/data/objects/overview">
    Model each engagement as a record with a [status](/data/properties/select/status) property for its phase (Kickoff → Config → Go-live) and relations to the account.
  </Card>

  <Card title="Tasks" icon="check-circle" href="/team/tasks/overview">
    Assign steps with owners, due dates, and priority: created by hand or automatically. Every task links back to its record for context.
  </Card>

  <Card title="Workflows" icon="bolt" href="/automation/workflows/overview">
    Fire when a deal closes to create the onboarding checklist, then send reminders and status updates as each phase completes.
  </Card>

  <Card title="Sequences" icon="list-ol" href="/automation/sequences/overview">
    Time-based nudges (a day-1 welcome, a day-7 check-in) with explicit waits between steps.
  </Card>

  <Card title="Shared pages & documents" icon="file-lines" href="/surfaces/views/types/document">
    Build customer-facing [pages](/surfaces/overview) with live data and collaborative [documents](/surfaces/views/types/document) for plans and specs.
  </Card>

  <Card title="Scheduling" icon="calendar-check" href="/comms/scheduling/overview">
    Let customers self-book kickoff and training calls from a shared availability link.
  </Card>
</CardGroup>

## Set it up like this

<Steps>
  <Step title="Model the process">
    Create an Onboarding [object](/data/objects/overview) with a [status](/data/properties/select/status) property per phase and a [relation](/data/properties/select/relation) to the customer account.
  </Step>

  <Step title="Automate the checklist">
    A [workflow](/automation/workflows/overview) fires when a deal closes and creates the account's [tasks](/team/tasks/overview) with owners and due dates.
  </Step>

  <Step title="Drive it forward">
    Use a [sequence](/automation/sequences/overview) for the timed nudges, and workflows to notify the team as each phase completes.
  </Step>

  <Step title="Track every account">
    Build an onboarding [dashboard](/surfaces/views/types/dashboard) (a board or table of accounts by phase) and report on cycle time.
  </Step>
</Steps>

## Related

* [Tasks](/team/tasks/overview) · [Task types](/team/tasks/types)
* [Workflows](/automation/workflows/overview) · [Sequences](/automation/sequences/overview)
* [Surfaces & pages](/surfaces/overview) · [Documents](/surfaces/views/types/document)
* [Scheduling](/comms/scheduling/overview) · [Dashboards](/surfaces/views/types/dashboard)


## Related topics

- [Embed blocks](/dev/embeds/overview.md)
- [Use Cases](/start/use/overview.md)
- [Views Overview](/surfaces/views/overview.md)
- [Permissions Overview](/team/permissions/overview.md)