Bodhi now supports multiple projects under a single client record — so your team can manage every system, job, and property without workarounds or duplicate contacts.
Why it matters
Every project your client has with you deserves its own journey, its own documents, and its own communication thread — tracked cleanly in one place.
When a client comes back for a battery add-on, a system expansion, or a new install at a different address, Bodhi can now track each project separately — without creating duplicate contacts or losing history.
Managing several service and repair visits for the same client? Each job gets its own project in Bodhi, with its own journey, messaging, and documentation — all tied to the same client record.
For commercial clients with multiple properties, each location becomes its own project. Your team gets a clear view of every system in a portfolio without the complexity of separate accounts.
Creating projects
New projects can be created automatically through your CRM, or manually from the installer inbox. Each new project gets its own journey, documents, and message thread — completely separate from other projects for the same client.
Project identification
Every project in Bodhi gets a Project Nickname — a clear, human-readable label that makes it easy to tell projects apart at a glance.
Nicknames are generated using the format: {Project Type} #{N} @ {Street}, {City}
For your team
The installer inbox makes it easy to navigate between projects and always know which system a conversation is about.
Clear context in every message
When a client has multiple projects, every message — in both directions — carries the Project Nickname so there's never any confusion about which project a conversation is about.
SMS
Every outbound SMS is prefixed with the Project Nickname in brackets. When the client replies, Bodhi routes the reply back to the correct project automatically.
Outbound emails include the Project Nickname in the subject line. When a client replies, Bodhi reads the nickname from the subject and associates the reply with the right project.
Client portal
Messages sent from the client portal are automatically associated with the project the client was viewing — or the one they selected in the compose area.
For clients
Clients with multiple projects get a clear, organized experience in their Bodhi portal — making it easy to stay on top of every system they have with you.
Common questions
Everything you need to know about how Project Hub works in practice.
No. Project Hub is automatically enabled for all Bodhi accounts. There's nothing you need to configure to get started. If you have an active CRM integration, new projects will begin flowing in automatically as they're created in your CRM.
Nothing changes. Each existing client record automatically becomes the first project under that client. All historical messages, documents, journey progress, and system details are preserved exactly as they are. No data is lost, and no action is needed from your team.
Bodhi matches the incoming email or phone number to the existing client and adds the new project under their record. No duplicate contact is created. The new project gets its own journey, nickname, and message thread — all linked to the same client.
No hard limit. Bodhi supports as many projects as needed per client — whether that's two solar installs, a battery add-on, or a full portfolio of commercial sites.
No. Single-project clients see the same experience as before. The project selector in the client portal only appears when there are multiple projects, and outbound messages won't include a Project Nickname unless the client has more than one project.
No. Clients log in once and see all their projects. Authentication is at the client level, not the project level. After logging in, they can switch between projects using the selector in the portal header.
On the Journey settings page. Each journey has a Project Name field — set it to whatever label fits your workflow (e.g., "Solar Project", "Battery Project", "Service & Repair"). Bodhi uses that label to generate Project Nicknames across the platform.
Yes. Every automated message — journey steps, NPS surveys, review requests — is associated with the project whose journey triggered it. The message displays the correct Project Nickname in both the installer inbox and the client's view, so there's no ambiguity about which system it refers to.
Yes. In the client portal, documents are grouped under headings for each project, making it easy for clients to find files for a specific system. In the installer inbox, documents appear in the selected project's section of the right pane, so your team always sees the right files for the project they're working on.
Yes. Internal notes in the installer inbox are tied to the selected project. Notes your team writes about one system stay with that project and don't bleed into another — keeping context clean when a client has multiple active jobs.