Client requests in one place instead of in e-mails
CS
A typical agency situation: a client sends a brief by e-mail, adds to it in a second e-mail and then asks how it is going. Answering takes 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 KoraGate handles it
In KoraGate a client gets their own access with the client role. They see only what they should see and submit requests directly in the system. You and your team have them in one place under Requests and can work with them next to regular tasks.
Three rules worth following
- One place for briefs. Tell clients that what is not in the system does not exist. It pays off from the very start.
- Status is visible. When a client sees that work is under way, they stop asking by e-mail.
- Separate from internal tasks. A client does not need to see who on the team handles what. Roles make sure they see only their own.
How to start
Create a workspace, set up a project for your first client and invite them. You can start for free. If you need a plan for more people, see the plans.