Keep every client decision with the right version and make the next action clear
Clients review the exact version you shared, their decision is recorded in one place, and your team can see the next action and who owns it.
Where included
- iConnect CRMControlled rollout
Does this sound familiar?
Drafts go to clients by email and chat. Feedback arrives on old versions, approvals are given in a call, and the team argues later about what was actually approved and who should act next.
Who is involved
- Account or project manager
- Client reviewer
- Team member who produces the work
- Manager who signs off delivery
From trigger to outcome
Follow the work from the first trigger. Each arrow names what passes along it and carries its evidence status in words, so a planned step never looks like a working one.
How to read the lines
- Dashed line: Planned
| From | To | What passes | Evidence |
|---|---|---|---|
| From:Content version | To:iReview | What passes:Content version for review | Planned |
| From:iReview | To:iFlow | What passes:Recorded decision starts the next action | Planned |
| From:CRM (Where included) | To:iReview | What passes:Client context | Planned |
Who acts at each hand-off
The people involved, in the order the work passes between them.
Account manager
Shares a specific version with named client reviewers
Result: A review tied to one version
Next owner: Client reviewer
Client reviewer
Comments on that version and approves or rejects it
Result: A recorded decision on the correct version
Next owner: Account manager
Account manager
Assigns the next action from the decision
Result: A next action with an owner
Next owner: Team member
What each product contributes
Each product's part in this workflow, with its current status.
- iReviewRoadmap
Is designed to keep each client review and its decision tied to the exact version that was shared.
- iFlowRoadmap
Is designed to carry the next action and approvals as a workflow. Starting it from a recorded review decision is planned.
- CRMControlled rolloutWhere included
Where included, holds the client account; giving reviews client context from it is planned.
What your business gains
- No argument about which version was approved
- Feedback on the right version, in one place
- A clear owner for the next action after each decision
Keep the decision with the correct content version and make the next responsible action clear.
A useful measure for a pilot
Review rounds per piece of work, and the time from sharing a version to a recorded decision.
What this requires
This workflow is on the roadmap. As designed, it needs these in place:
- Content versions your team shares for review.
- Named client reviewers for each piece of work.
- Team members with access to share versions and follow decisions.
- Agreed next-action rules for approved and rejected versions.
Evidence and scope
Every connection in this workflow is planned: sending a content version into review, a recorded decision starting the next action, and client context from the customer record. The map shows the intended workflow.
- Plannedit is not built yet. It is shown so you can see the intended workflow.
Each product shows its own status, and none is described as released for general use. Your demo confirms what applies to your deployment.
A suitable starting option
Client review and approval
Compare what this starting option includes, what it requires and what can be added. Packaging is agreed per deployment.
Questions about this workflow
Does a client decision start the next workflow on its own?
No. A recorded decision starting the next action is a planned connection. Your account manager assigns the next action.
Can content versions be sent for review from other tools?
Not yet. Sending a content version into review from another tool is planned. Your team shares the version for review.
Walk through one review round with us
Tell us how your clients review and approve work today. We show how a decision would be recorded on the right version and how the next action becomes clear.
Request a tailored demo of this workflow