Let’s Talk: Building Chat Inside Agency Handy
Over the past few months, one of the most common requests we’ve received has been:
“We want communication to happen right inside Agency Handy.”
So here we are — we’ve started working on Chat. At first, the plan was simple: let clients and admins/superadmins talk directly inside the platform. But the moment we thought of adding B2B access + call-to-action (CTA), new questions came up.
Company or Person?
If you send a message to a company, should it be visible to everyone in that company, or only to the specific team member you picked?
This one decision changes the entire privacy vs. collaboration balance.
1-to-1 vs Group Chats
Now think about this:
If you’re already in a 1-to-1 chat and later assign a team member — should that person:
-
Be added to the same chat (but then privacy is gone), or
-
Get a new chat (but then too many chats start piling up)?
The same question applies to B2B too. How would you want this to work?
Message Control
Should we allow:
-
Edit, so people can fix mistakes but edits aren’t tracked?
-
Delete, so you can remove messages but break the flow?
We’re planning to give only one of the two — because if we give both, there’s no reliable way to track what actually changed. Which one matters more to you?
Strategy: How Long to Keep Conversations?
Here’s the practical side: storing chat data isn’t free.
We’re thinking of keeping messages for the last 90 days.
Question is — should this be:
-
A fixed system rule, or
-
Something the user decides?
Either way, we’ll be transparent: storing every single message forever isn’t possible, especially with LTD pricing. But we want you to have control and clarity.
For our first version (MVP):
-
Simple 1-to-1 chat with clients.
-
Ability to add a team member → turns into group chat.
-
Replies + reactions built-in.
Future Phase: deeper links to Orders, Tickets, Requests.
- Now it’s your turn — how do you imagine B2B chat working inside Agency Handy-
- What setup would make your daily workflow smoother?
We’re building this together, and your answers will shape the direction ![]()