Use case 03 / CRM & operations
A shared workspace for
CRM and project operations
We connect role-specific project work with existing CRM and planning systems so each participant can act with the context and access their task needs.
Explore the approach- Connect
- Coordinate
- Hand over
The short version
A custom CRM portal helps operations teams work across sales and delivery systems without forcing every participant through the same interface. We developed role-specific workspaces with project context, products, pricing, files and handoffs. The work connects Salesforce workflows alongside an existing Zoho CRM integration, with provider-aware routing, backend access checks and a separate connection to a planning system.
01 / The problem
Shared information, different responsibilities
A sales representative needs to move a project forward. An administrator needs to prepare the next commercial step. A delivery partner needs relevant product and pricing context. They may all refer to the same project while needing different actions and different levels of visibility.
A product recommendation is not necessarily the price entered for a project. A status change is not necessarily a completed handoff. A CRM login alone does not explain what the person should be allowed to do.
When those distinctions are unclear, people must fill in the gaps through messages, separate files and repeated checks.
02 / The idea
Design around the next responsibility
We treated the portal as a place to do focused operational work while keeping the existing systems connected. The interface should explain the relevant project and next action. Behind it, each request needs a clear destination, access rule and data responsibility.
A person's CRM provider and business role are separate facts. The provider determines which integration should handle the request. The role helps determine which workspace and actions are appropriate.
03 / The solution
Context, controlled changes and explicit handoffs
Route people to the relevant workspace
Authentication leads into routing that considers both provider and role. Salesforce-backed workflows coexist with the existing Zoho CRM connection. A role label alone does not silently choose the provider.
Within the project workflow, the interface brings together context, products, notes, files and relevant history. Access differs by role. For the scoped sales role, backend checks also consider assignment and project status before allowing project actions. Hiding an interface button is only one part of that decision.
Make the price decision visible
The product workflow distinguishes a recommended price from the entered sales price. A recommendation does not automatically become a completed project price. Missing prices remain identifiable during preparation.
Tracked price changes retain the previous and new values with a time and actor. Where that tracking applies, the product update and history entry are written together. The interface can then show the history beside the operational context, helping an authorised person understand the change without searching through a message thread.
Give readiness a recorded meaning
Preparing a product list and handing it to administration are different actions. The readiness step records who marked the project ready and when, then requests a workflow notification for the next responsible person.
The product list therefore has an explicit handoff point. Role-specific edit checks use the recorded state as part of the workflow. Notification history gives additional context, while the saved handoff remains distinct from whether an email reaches its recipient.
Connect the next system through a defined event
A separate integration handles a CRM event that can create a project in a planning system. It validates the incoming request, reads the current CRM record and checks the triggering status before preparing the downstream information.
After creation, it writes the planning reference back to the CRM. When that reference is already present, the handler skips another creation attempt. This is a specific safeguard around the recorded reference; failures still need visible handling, particularly if creation succeeds but the reference cannot be written back.
04 / Our skills
How our skills came together
CRM architecture separated provider identity, business roles and record ownership. Workflow analysis identified the points where a price becomes usable or a product list becomes ready for another person. UX work gave those decisions a place in the project workspace.
Application development connected the interface to server-side checks, saved updates and history. Integration engineering mapped defined actions to the appropriate CRM or planning provider. Together, those disciplines made the portal understandable while preserving distinctions that matter behind the scenes.
05 / What it enables
What the approach enables
The portal supports focused project work with role-appropriate context, explicit price decisions and recorded handoffs. Existing CRM connections can serve different workflows through defined routes. Selected events can carry work into a planning system and return its reference to the source record.
For an operations leader, the opportunity is to make responsibilities visible in the software: who can act, what they are changing and which system should receive the result.
06 / A little more detail
Questions & answers
Can a portal work with two CRM providers?
Yes. This approach keeps provider identity separate from business role and routes requests accordingly. Salesforce and Zoho CRM can support their respective workflows without treating every role as evidence of a particular provider.
Does everyone see the same project information?
No. Views and actions depend on the role and workflow. In this sales project flow, the backend checks assignment and project status as well as identity. Administrative responsibilities can have broader access.
Will connected systems always update instantly?
That should be defined per workflow. The planning connection creates a downstream project and writes its reference back after the relevant checks. It does not establish an instant, bidirectional mirror of every record or field.
Your next step
A similar challenge?
Let's talk.
Need a clearer handoff between your CRM and daily operations? Email info@digibox.hu with the step that keeps getting stuck.
A little about us