Customer onboarding portal with kickoff checklists

A customer onboarding portal is where each new customer works through their kickoff tasks and uploads the documents setup needs, while the onboarding team sees every account's progress and each customer sees only their own.

Pattern: Checklists

Describe it to EachEntry

“We sell booking software to clinics. Each new customer should get a kickoff task list and a place to upload documents, and see only their own onboarding, while our onboarding managers see every account.”

Viewing as

My kickoff tasks

Kickoff tasks

2 of 8 done
  • Add a task
Powered by EachEntry

In plain English

How EachEntry sets it up

EachEntry gives every customer and onboarding manager a sign-in of their own. Each customer sees only their own onboarding projects. It covers kickoff tasks & documents. Onboarding projects, kickoff tasks, documents, key dates, invoices, shared files and slotwise team live in EachEntry's own database, so there's no spreadsheet to keep in sync.

What it does

01

New customers check off kickoff tasks without a status call

Kickoff used to be a welcome email with twelve steps, and a weekly call to find out which ones had happened. In EachEntry each customer signs in to their own kickoff tasks, each with a due date, and checks them off as they go: appointment types chosen, front desk invited, reminder texts approved. The onboarding manager sees progress without booking another check-in.

ChecklistsDone by: Customer
02

Customers upload the order form and staff list straight to their onboarding

Documents used to arrive as attachments scattered across a month of emails. In EachEntry the customer uploads each file to their own documents list, picking what it is and which clinic it's for, and the onboarding team finds it on the account. Nobody searches an inbox for "staff_list_FINAL2.xlsx" the day before go-live.

File uploadsDone by: Customer
03

Each clinic signs in to its own onboarding and nobody else's

Sharing onboarding progress used to mean a tracker spreadsheet with every customer on it, which could never be sent to any of them. In EachEntry each customer signs in and sees only their own onboarding projects, go-live dates and status. The onboarding manager keeps one list of every account, and no customer glimpses another clinic's name.

Client-only accessDone by: Customer

Who sees what in a customer onboarding portal

Every person signs in to their own view. This is what each role in the demo gets.

Customer

Sees only their own onboarding projects.

Pages
Home, My kickoff tasks, My documents, My onboarding projects, Key dates, Help center
Can start
Upload document

Onboarding manager

Sees every onboarding project in the portal.

Pages
Home, Onboarding projects, Kickoff tasks, Documents, Key dates, Invoices

What’s in the customer onboarding portal template

The tables and fields EachEntry sets up for this portal. Describe your own version and change any of them in the editor.

Onboarding projects

  • Clinic (text)
  • Go-live date (date)
  • Status (choice: Kickoff, Setting up, Training, Live, On hold)
  • Onboarding manager (link)
  • Plan (choice: Starter, Practice, Group)
  • Clinicians (number)
  • Customer (link)
  • Manager notes (long text)

Kickoff tasks

  • Task (text)
  • Due (date)
  • Clinic (link)
  • Customer (link)
  • Done (yes/no)

Documents

  • Document (text)
  • Type (choice: Order form, Business associate agreement, Staff list, Logo & branding, Phone number transfer)
  • Clinic (link)
  • File (file)
  • Notes (long text)
  • Status (choice: Requested, Uploaded, Checked)
  • Needed by (date)
  • Customer (link)

Key dates

  • What (text)
  • Date (date)
  • Kind (choice: Kickoff call, Training, Go-live, Check-in)
  • Clinic (link)
  • Who and where (text)
  • Status (choice: Booked, Done)
  • Customer (link)

Invoices

  • Invoice (text)
  • Clinic (link)
  • Issued (date)
  • Due (date)
  • Amount ($) (number)
  • Status (choice: Issued, Paid, Overdue)
  • Customer (link)

Shared files

  • File (text)
  • Kind (choice: Setup plan, Training, Template, Agreement)
  • Shared on (date)
  • Attachment (file)
  • Customer (link)

Slotwise team

  • Name (text)
  • Role (text)
  • Email (text)

The parts behind this portal

Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How EachEntry builds a portal

Collect

1 part
  • File attachments

    Upload and view files on the record they belong to, not in a folder named FINAL v2.

Decide

1 part
  • Checklists

    A task list on each record, ticked off in its detail view, with progress shown. Use it for onboarding, inspections or opening duties.

Control

3 parts
  • Who sees which records

    Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. EachEntry sets this up from your description, and you can adjust it in the editor.

  • Passwordless sign-in

    A sign-in link by email, by default. Password sign-in if you'd rather.

  • Your brand

    Your domain, your colors, your logo. Members see you.

Frequently asked questions

A customer signs in with a link sent to their email and lands on Home. They see Home, My kickoff tasks, My documents, My onboarding projects, Key dates and Help center, and only the onboarding projects that are theirs. From there they can use “Upload document”.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your customer onboarding portal with EachEntry

Describe who signs in and what each person needs, and EachEntry builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited customers.

See pricing · How EachEntry builds a portal