kintone is a fully integrated social collaboration and customizable business application cloud platform that allows internal and external teams to solve business process inefficiencies through database and work flow-driven custom apps, communication and collaboration. kintone can be used for custom CRM, Project Mangement, SCM and much more.
Attach marked campaign proofs to the right creative task.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
Add emailed reviewer edits to the right campaign asset task.
Your campaign team gets a revision subtask from reviewer email, linked to the asset task and carrying the requested edits.
Send each ready asset to its reviewer and log the handoff.
Your reviewer gets the current asset with a clear request, and your campaign task keeps the handoff in view.
Post today's due asset reviews with their next owners.
Your launch team sees reviews due soon, what is blocked, and who needs to act next, together in chat before the launch window.
Hand off ready campaign creative to its reviewer in chat.
Your named reviewer gets the asset and question in chat when your campaign task is ready for review.
Flag undecided campaign assets as launch dates approach.
Your brand lead gets the file and launch deadline in a private alert while the pending approval carries the escalation.
Put campaign requirements beside assets awaiting review.
Your reviewers see the brief beside the asset, with the brand decision they need to make clearly stated.
Put the current creative file in the campaign sign-off task.
Your brand reviewer gets the current campaign draft and the decision needed together on the review task.
Mark each campaign proof's current revision and reviewer deadline.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Check client access to the latest campaign proof before review.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
Route marked campaign proofs to the maker for revision.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Point campaign review tasks to the latest proof.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.