COMMUNICATION AND NOTIFICATIONS
Keep the Conversation With the Work, Without Mixing Internal and Client Communication.
Most client work is discussed in three places at once and recorded in none of them. Bikabo attaches the conversation to the work, and keeps the client side and the internal side structurally apart.
Two Conversations, and They Do Not Meet.
This is not a permission setting that could be misconfigured. Internal discussion and client conversation are different kinds of record, and the roles that do the work cannot reach the client side at all.
Your team sees
Internal discussion
- On an Engagement, or on a specific Task.
- Open to the people actually assigned to that work, worked out live from current assignments.
- Mentions that notify a colleague on exactly the Task that needs them.
- Attachments that stay internal unless someone deliberately shares them.
Your client sees
Client conversation
- A general thread, plus one per Engagement.
- Held between the Client and the people responsible for the relationship.
- Nobody working on delivery holds a permission that reaches it.
- Nothing arrives here unless someone on your side sends it.
Client, Then You, Then Your Team.
A client message arrives. Somebody internal needs to weigh in. A reply goes back. Each of those is a deliberate step, and none of them puts your team in front of your client by accident.
1. The client writes
Into the general thread or the one for their Engagement, where the people who own that relationship will see it.
2. You forward it internally
A new internal message carrying the client's context, so the team can answer the question without being handed the client.
3. You reply, in your words
A client-facing draft prefilled from what your team said, edited by you, sent only when you confirm it.
Discussion Sits Where the Work Is.
A question about a Task belongs on that Task. A question about the Engagement belongs on the Engagement. Somebody picking the work up next week reads the thread that goes with it rather than scrolling a channel.
Who can see an internal discussion is worked out from who is actually assigned to that work right now, not from a list of participants somebody remembered to maintain.
Mentioning a colleague notifies them on exactly the Task that needs them. A mention can only reach someone who was already entitled to that work, so it can never be used to hand out access.
Notifications That Respect Who You Are.
Events are grouped into categories: messages, tasks and reviews, client money, staff payments, scheduled work, and account security. Each person chooses in-app and email delivery per category.
Who gets told is decided by who is entitled to the underlying record, so a notification never becomes a side channel that leaks something the app itself would withhold. Sensitive values, such as Secure Access Details, never travel in a notification or an email.
In-app notifications appear immediately. Email is queued and retried, so a mail failure never blocks the work that produced it.
What a Conversation Is Not.
Chat is where people talk. It is not where the business keeps its record of what happened, and Bikabo does not let it become that by default.
- A message approving work is not a review. Review is its own decision, by a named Checker.
- A message about a blocker is not an Action Request, which is tracked and resolved.
- A message saying it is done is not delivery, which is what the Client actually sees.
- A message containing credentials is not Secure Access Details, which are encrypted, masked and audited.
Questions About Communication
No. The path is client to your business, and your business to your team. Assistants and Checkers cannot hold the permissions that reach a client conversation, so this is not a setting that could be left switched the wrong way.
Forward it internally. That creates a new internal message quoting the client’s context, without adding anyone to the client conversation.
You open a client-facing draft prefilled from the internal message, edit it into the words you actually want to send, and send it. Nothing goes out until you confirm the exact wording, and both messages stay linked so the trail is readable later.
No. Attachments are internal by default and become client-visible only when someone selects them deliberately. Relaying the text of a message never relays the files with it.
No, and this is deliberate. A review decision, a blocker, a delivery and a set of access credentials each have their own record. Talking about them in a thread does not create one.
Yes. Notifications are grouped into categories, and each person chooses in-app and email delivery per category. In-app notifications always appear immediately.
No. There is no WhatsApp, no SMS, no external email client integration, no AI rewriting of messages, no daily digest and no quiet hours. Notifications appear in the app, and by email where that category is enabled.