iReview
Get a clear decision on the right version
iReview is designed to keep client comments and the approval decision attached to the exact content version being discussed, in Arabic or English, so your team and your client share one record of what was agreed.
Does this sound familiar?
Client feedback arrives across email, chat and calls. Nobody can say for certain which version was approved, who approved it, or which instruction is the latest one.
What it costs the business
Work is repeated on the wrong version, delivery waits for clarification, and settling what was actually agreed takes time on both sides.
Built for
- Agencies and creative teams that need client sign-off
- Service teams that deliver documents or content for approval
- Account managers who carry the client relationship
From problem to gain
What changes when the work moves into one place.
The situation
- Work is repeated on the wrong version, delivery waits for clarification, and settling what was actually agreed takes time on both sides.
What your team does
- Comments on a specific version
- Recorded decisions
- Bilingual review
What it produces
- A decision linked to an identifiable version
- Comments kept with the content they refer to
- A shared record of what the client agreed
What you gain
- Less rework caused by scattered feedback
- A clear answer to who approved what
- Client review in the client's language
The difference it makes
Less rework caused by scattered feedback
How
Designed so comments are attached to the specific version they refer to, instead of being spread across messages.
A clear answer to who approved what
How
Designed to record each decision (approved, rejected or changes requested) with who made it and when.
Client review in the client's language
How
Designed as a bilingual review space where reviewers work in Arabic or English.
How it fits together
What it does
- Comments on a specific version
- Recorded decisions
- Bilingual review
What your team gets
- A decision linked to an identifiable version
- Comments kept with the content they refer to
- A shared record of what the client agreed
How your team uses it
Account manager
Shares a content version with the client for review
- Output
- A version waiting for the client's decision
- Next owner
- The client's reviewer
Client reviewer
Comments on the version, then approves it, rejects it or requests changes
- Output
- A recorded decision on that version
- Next owner
- The delivery team
Delivery team
Checks the recorded decision before starting the next stage
- Output
- Work that proceeds on the agreed version
- Next owner
- The account manager
Inside iReview
Comments on a specific version
Designed so the client comments on one identified content version and your team sees each comment in context.
Recorded decisions
Designed to record an approval, a rejection or a request for changes against each version, with who decided and when.
Bilingual review
Designed for reviewers on both sides to work in Arabic or English.
One shared reference before the next stage
Designed to give the delivery team one place to check what was agreed before the next stage of work starts.
How to start / What this requires
iReview is on the roadmap. As designed, it needs these in place before a client review starts. Access requirements, including how your team and your client's reviewers sign in, are confirmed during scoping.
First step
Start with a tailored demoWe walk through your own workflow with you and confirm which of the requirements below apply to your team.
What needs to be in place
- Content versions your team shares for review.
- Named reviewers on the client side for each piece of work.
- Team members set up with access to share versions and follow decisions.
What you gain by connecting it
Selected combinations, not every possible pair. Each connection shows how far it has been proven, so you can tell what has been shown working from what is still planned.
How to read the connection labels
- Demonstrated in testing
- Shown working in our testing, on code that is not yet released to customers.
- Configured per deployment
- Depends on setup for your deployment, such as a connected channel or approved knowledge.
- Planned
- Not built yet. Shown to explain the intended workflow.
Client review into approval
A recorded decision on the right version would start the next responsible action in iFlow (Roadmap), and content versions would be sent into iReview for that decision.
Works with
iFlow (8)RoadmapSee the full workflowConnections
- Content versioniReview
- Content version for review
- Planned
- iReviewiFlow
- Recorded decision starts the next action
- Planned
Client context from the customer record
The client's account and history in iConnect CRM (Controlled rollout) would sit beside each review.
Works with
CRM (1)Controlled rolloutSee the full workflowConnections
- CRMiReview
- Client context
- Planned
Suggested solutions
Complete workflows this product takes part in.
Good to know
We would rather you knew the current limits before a demo than after it.
- Roadmap: iReview is planned and not part of the current iConnect release. Request a demo to discuss how your clients approve work.
- There is no self-service sign-up.
- A recorded decision is a working record for your team and your client. It is not offered as legal evidence.
- Connections with iConnect CRM (Controlled rollout) and iFlow (Roadmap) are Planned.
Technical details
For technical evaluators: records, roles, inputs and setup, as far as current evidence supports them.
Show the technical details
- Decision record
- Designed to keep, for every version, the comments, the decision, and who made it and when.
- Languages
- Designed for reviewers working in Arabic or English.
- What a pilot would measure
- Time to decision, revisions caused by feedback on the wrong version, approvals linked to an identifiable version, and rework effort.
Questions and answers
What is iReview?
iReview is a planned iConnect product, built by iConsultants, where a client reviews a content version, comments on it and approves or rejects it, with each decision recorded. It is on the roadmap.
How is iReview different from iFlow (Roadmap)?
iReview is designed to record a client's decision on a specific content version. iFlow, which is on the roadmap, routes the next responsible action inside your team. A connection between them is Planned.
Does it work in Arabic?
It is designed for reviewers working in Arabic or English, so your client can review in either language.
Can I start using it today?
Not yet. iReview is on the roadmap and not part of the current iConnect release. Request a demo to discuss how your clients review and approve work today.
Discuss your client approvals
Tell us how your clients review and approve work today. We will reply to arrange a conversation.