Customer Portal · Sales
One record. Your team works on it. Your client looks at it.
This is their room.
What Léa Dumont sees when she signs in: one quote waiting for her, one invoice due, one ticket her team is on, the project and its next date, the documents, and the thread with Mathilde. Every tile is a record your team is working on, read through her role.
What the client sees, and what they can do about it.
Six things a client keeps writing to ask about, each one a record your team already keeps, each one with the action the client is allowed to take on it.
Quotes to accept
The quote your team sent, with its lines and its validity, and the button that signs it. Nothing to print, nothing to scan back.
Invoices to pay
The invoice as it stands in your ledger: amount, due date, what is already paid, and the button that pays the rest.
Tickets
The ticket they raised, its state, the reply, and the visit planned for it, as your support team moves it.
Project progress
The milestones they were promised, which are done, which is next, and the date, read from the tasks rather than typed into an update.
Documents
The signed quote, the plan, the signed worksheet: on the record they belong to, in the version your team has.
Messages
A thread on the record, not an email that has to be found again. The client writes, your team answers, and the answer is on the project.
The same portal, for an architect's client and for a distributor's customer.
What adapts: which records the client sees at all, which fields of each, what they can do on them (approve, sign, pay, reorder, upload), and what the portal's home leads with. A client who follows one project for a year and a customer who reorders every week walk into two different rooms, built on the same records.
An architecture firm
The client follows one project by phase. Their room leads with the current phase, the drawings waiting for their approval round by round, the site photos, and the fee invoice for the stage just signed off. Their sign-off on a phase is what releases the next fee invoice.
A wholesale distributor
The customer reorders. Their room leads with their price list, their last order and a button that repeats it, what is in stock and what ships in three to five days, the delivery notes, and the month's statement with what is still open on it.
Accept, sign, pay. One quote, one sitting.
The quote your team sent is the quote the client opens. They accept it, sign it at the level the document asks for, pay the deposit, and the project appears in their room, because the acceptance, the signature, the payment and the project are four states of one record, not four emails. Your team sees each state land as it happens.
The contact, the shop, the chat and the contract: the same record.
The person who signs in is the contact on the company record in CRM. The order they placed in the shop is the order they follow in the portal. The chat they start becomes the ticket they track. The maintenance contract they renew is the subscription that raises next month's invoice. None of those is a portal object synced from somewhere: the portal is a role on the records the rest of your workspace runs on.
CRM
What the client does in their room, opened, signed, paid, asked, is activity on the company record, beside the calls and the emails. See CRM.
CRMeCommerce
The shop and the portal share the customer, the price list and the order, so an order placed at 23:10 is in the portal at 23:10, with its delivery state. See eCommerce.
eCommerceLive Chat
A chat started from the portal is a conversation on the contact, and the ones that need a technician become tickets without being retyped. See Live Chat.
Live ChatSubscriptions
The maintenance contract's renewal, its plan change and its monthly invoice, in the client's hands, on the contract record. See Subscriptions.
SubscriptionsBuilt for businesses whose clients keep asking where things stand.
Agencies, installers, architects, consultancies, distributors, maintenance contractors: the businesses whose client is in the relationship for months, has a quote to accept and an invoice to pay in the same fortnight, and writes on a Friday afternoon to ask whether the visit is still on. The answer exists. It is on the ticket, the project and the invoice, and somebody on your team is retyping it into an email.
The client portal tool you would otherwise buy shows your client a copy.
It has a login, a logo and a folder. The invoice in it was synced from your ledger, the progress in it was typed by your team, and the two drift.
The client signs in and sees their own things
- A spreadsheet
- A shared file
- A client portal tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, one link, one role
The invoice they pay is the one in your ledger
- A spreadsheet
- No
- A client portal tool
- Synced, or re-entered
- A suite module
- Yes, in their ledger
- Enobase
- Yes, the same record
The quote is signed and becomes the project
- A spreadsheet
- No
- A client portal tool
- Signed, then copied over
- A suite module
- Sometimes
- Enobase
- Yes, four states of one record
Progress without someone updating it
- A spreadsheet
- No
- A client portal tool
- Typed by the team
- A suite module
- Yes
- Enobase
- Yes, read from the tasks
The ticket they follow is the one your team works
- A spreadsheet
- No
- A client portal tool
- A second queue
- A suite module
- Yes
- Enobase
- Yes, the same ticket, their view
What they see is a rule, field by field
- A spreadsheet
- No
- A client portal tool
- Per app, per plan
- A suite module
- Per document type
- Enobase
- Yes, per role, on every view
Your own fields on what they see
- A spreadsheet
- Yes, uncontrolled
- A client portal tool
- Limited
- A suite module
- With a developer
- Enobase
- Yes, calculated ones too
Time to live
- A spreadsheet
- A day
- A client portal tool
- A week
- A suite module
- Months
- Enobase
- One to two weeks
| What you need | A spreadsheet | A client portal tool | A suite module | Enobase |
|---|---|---|---|---|
| The client signs in and sees their own things | A shared file | Yes | Yes | Yes, one link, one role |
| The invoice they pay is the one in your ledger | No | Synced, or re-entered | Yes, in their ledger | Yes, the same record |
| The quote is signed and becomes the project | No | Signed, then copied over | Sometimes | Yes, four states of one record |
| Progress without someone updating it | No | Typed by the team | Yes | Yes, read from the tasks |
| The ticket they follow is the one your team works | No | A second queue | Yes | Yes, the same ticket, their view |
| What they see is a rule, field by field | No | Per app, per plan | Per document type | Yes, per role, on every view |
| Your own fields on what they see | Yes, uncontrolled | Limited | With a developer | Yes, calculated ones too |
| Time to live | A day | A week | Months | One to two weeks |
Questions about Customer Portal
It is a window, so it shows what your workspace holds: contacts, documents and messages on their own. Turn Quotes, Invoicing, Project or Helpdesk on and their records appear in the client's room the moment they exist, with nothing to connect.