Client briefs in one place instead of in e-mails
CS
A typical situation in an agency or a small company: a client sends a brief by e-mail, adds to it in a second e-mail and then asks how it is going. Answering costs you a quarter of an hour of searching your inbox. It can be done better.
Why e-mail is not enough for briefs
- The brief is scattered across several threads and everyone in the company sees a different one.
- Nobody knows who is working on a request or what state it is in.
- When someone leaves a project, the information leaves with their mailbox.
How to organise it in KoraGate
Create a separate project for each client, folders in it by type of work, and rewrite every brief as a task with a description, a deadline and an assignee. Add attachments right to the task. Use the "Waiting" status for things that depend on materials from the client. The whole team sees what is next, and everyone sees only what their role allows.
KoraGate is not a client portal: you manage briefs inside your own team. Help from Codecron (a bug, a question, billing), on the other hand, you handle right in the app through Requests.
Three rules worth following
- Brief straight into a task. As soon as a brief arrives, rewrite it as a task. What is not in the system, nobody keeps an eye on.
- Status is visible. When anyone on the team opens the task, they know whether it is being worked on or waiting for the client, and can answer a question in seconds.
- History in one place. Comments (from the Team plan) and attachments stay with the task, not in one person's mailbox.
How to start
Create a workspace and set up a project for your first client. You can start for free. If you need a plan for more people, see the plans.