.svg)
What a customer onboarding portal is
A customer onboarding portal is the place a new business customer signs in to during the weeks between signing and going live. It shows the plan for their account, explains each stage, collects the information your team needs, and keeps every question and request in one visible thread. The customer always knows what's next, and your implementation team always knows what's waiting.
Your onboarding, seen by the customer running it
Take Corvane, a company that makes warehouse management software for distributors. Halden Supply, a building materials distributor with six warehouses, has just signed. Priya is Halden's operations manager, and the rollout is hers.
Week 1, Monday, 9:00 am: her plan, for her company
Priya opens the welcome email and signs in. Waiting for her: Halden's onboarding plan, the stage they're in right now (setup), the three guides that matter this week, and the two things Corvane needs from her before Friday.
Tuesday, 2:20 pm: the scanner question, settled in a minute
Her warehouse lead wants to know which handheld scanners work with Corvane. Priya types the question into the portal. Back comes a reply drawn from Corvane's hardware guide, with the page linked, and she forwards it to him before he's back on the floor.
Thursday, 10:40 am: she gets the import right herself
Her product list won't load. The error points to a date column. Priya searches it, finds the import guide for her exact file type, reformats the column and tries again. It goes through. Corvane's team never had to hear about it.
Friday, 11:15 am: handing over what Corvane needs
The plan asks for her warehouse locations and the people who need accounts. Priya fills in the setup form in the portal, one row per site and a role for each user. She gets a confirmation right away, and the request shows as received, then in progress, then done.
Week 2, Tuesday, 3:50 pm: a question only a person can answer
Halden wants to switch from its old system over a weekend. That's a judgment call, so Priya types it into the portal chat, and it reaches Tomas, her implementation lead, with Halden's account, current stage and her earlier requests attached. Tomas replies by email because it's a longer answer, and Priya sees his reply in the portal thread as well.
End of the month: the onboarding team closes a gap
Corvane's onboarding manager checks what new customers searched for and couldn't find. Label printer setup comes up again and again. The team writes the guide, labels it for the setup stage, and every customer who reaches that stage sees it first.
What your new customers can do
See their own plan
Each customer's portal is personalized to their account: the products they bought, the stage they're in and their role. An admin sees the full plan. A warehouse lead sees the guides for their part of it.
Answer setup questions themselves
Customers type a setup question as they'd put it to a colleague, and the reply is built from your approved setup guides, with the source linked, in their language. They keep moving between calls with your team instead of waiting for the next one.
Hand over what you need, once
Forms ask for exactly what each stage requires, like locations, user lists or system details. Customers get a confirmation, and your team gets clean information instead of a reply-all thread.
Reach their implementation lead
If something calls for a person, customers write from the portal chat or by email. It goes to the lead on their account, with the stage and history attached, so nobody asks them to explain again.
Know where every request stands
Each form, question and request carries a status in the portal. Nobody has to write in to ask what's open.
What your implementation team gets
Every customer's forms, questions and chats arrive in one shared inbox, in queues by account, stage or product. Your team sees what's unassigned, claims work, and passes it to a colleague or a specialist with an internal note the customer never sees. Replies go back by chat or email, wherever the customer wrote. Analytics show the searches that came up empty and which requests have waited longest, so you know where onboarding slows down.
What changes when onboarding runs here
Customers stop waiting for the next call to keep going. Setup guides are there at whatever hour they're working, so calls with your team go to decisions, not how-to questions.
Information arrives once, complete. Each stage's form asks for exactly what your team needs, so nobody rebuilds a user list from four emails.
Every account's history travels with it. When a lead hands a customer to a specialist, the stage, requests and notes go along, so the customer never starts over.
A gap one customer hits gets fixed for every customer after. Unanswered searches show you which guide to write, and you label it for the stage where people need it.
Your whole onboarding program sits in one place. Plans, guides, forms and conversations live together instead of in slide decks, shared drives and inboxes.
Where the assistant helps and your team leads
The assistant answers new customers from your approved onboarding content and links the guide behind every answer. Decisions, like a cutover date or a change in scope, go to the implementation lead, along with everything the customer already said. The assistant can open a request if you permit that, and a log records each action. What customers hear stays your team's call.
How to build your customer onboarding portal
- Gather your onboarding content. Connect the guides you already keep in Confluence, Notion, Google Drive or SharePoint, or create new ones in MatrixFlows. Tag each one by product and onboarding stage.
- Connect your accounts. Bring in customer accounts, contacts and their current stage from HubSpot, Salesforce or Gainsight, so each portal knows whose it is.
- Lay out the plan. Decide what customers see at each stage and add the forms each stage needs, with your logo and colors, at your web address.
- Set up your queues. Create queues for your implementation team and choose who covers which accounts.
- Turn on the assistant. Choose the onboarding content it answers from, what it's allowed to do, and the moments it brings in a person.
- Invite your next new customer. Send the welcome email with sign-in, or use single sign-on for larger accounts.
Works with your onboarding stack
HubSpot, Salesforce and Gainsight for accounts, contacts and onboarding stage, Confluence, Notion, Google Drive and SharePoint for setup guides, email and web chat for customer conversations, and Microsoft Teams or Slack for customers who'd rather talk there. The rest connects by webhook or API, with over 30 connectors to choose from.
Related
- Onboarding SaaS customers at scale
- Client collaboration portal, the version for agencies with outside clients
- SaaS help center for customers once they're live
- Forms that collect what each stage needs
- Customer enablement and support on MatrixFlows
- A guide to the best customer portal software
| Customer onboarding portal on MatrixFlows | The usual onboarding | |
|---|---|---|
| The plan | Personalized to the account, its products and its current stage | A kickoff slide deck that's out of date by week two |
| Setup questions | A plain question gets an answer with the guide linked | Saved up for the next weekly call |
| Handing over information | A form per stage, with confirmation | Spreadsheets passed around by email |
| Reaching a person | Portal chat or email, straight to the account's lead with history attached | Whoever was copied on the last thread |
| Knowing what's open | Every request shows its status | Asking the project manager for an update |
| Hand-offs inside your team | Claimed and passed on with internal notes | Forwarded emails and lost context |
| Improving the process | Unanswered searches show which guide is missing | Hearing about it in the churn review |
Bringing new customers live belongs to your customer operations, and MatrixFlows runs those too: support after go-live, partner programs and service for your own staff.