Back to Resources
HOW TO USE BOOKWITS CHAT BEGINNER

Chat Module Guide

See the detailed walkthrough and examples

A beginner-friendly guide to Bookwits Chat: where to find it, how conversations work, inviting participants, sending messages/files, managing notifications, and handling permissions.
How to Use Bookwits
Detailed guide
Module overview
Learn how to start a conversation, invite participants, exchange messages and files, and manage conversation settings.
Written guide below
Why this module matters Chat gives your team one place to coordinate work with colleagues and clients, without switching tools or losing conversation history.

Chat: conversations, invitations, files and permissions

In this chapter (30)

Where to find this workflow and its controls

Choose Chat in the sidebar or the Chat tab of a client profile. The conversation list is on the left; use its search and All, Unread, Pinned or Archived views. New chat is above this list.

Choose Direct chat for exactly one other participant or Group chat for multiple participants. The participant picker has its own search and source tabs. A group needs a name; review any Invite required indication before creating it.

Open a conversation to use the message composer. Search messages, pin/mute/archive and conversation actions belong to that conversation's header. Per-message actions belong to the message, not to the whole channel. Do not assume inviting someone into a conversation shares the entire client file.

Owner, Admin and Member: access, restrictions and exceptions for this chapter

See the current application screenshots for this chapter

Where to find Chat

Go to: Chat from the main navigation.
From here you can
  • Start a new direct or group conversation
  • Search conversations
  • Filter to unread, archived, or all chats
  • Open a conversation and send messages/files
  • Open conversation details and manage settings

What Chat is (before you start)

In Bookwits, a conversation is the container for people, messages, files, and settings.
Two conversation types
  • Direct : one-to-one chat
  • Group : three or more participants
Participant states
  • Active : currently in the chat
  • Pending : invited but not accepted yet
  • Declined : invite declined
Beginner tip: treat each conversation like a mini workspace. Keep one topic per conversation so future follow-up is easy.

Quick Start (First 15 minutes)

If you are new, do these in order:
1
Create one direct conversation
2
Send a text message + add one reaction
3
Upload one file and one image
4
Create one group chat and invite a participant
5
Pin one chat and mute one chat

Working through the module

1) Start a direct conversation

A direct conversation is appropriate for a discussion with one other person. Check the recipient before sending files or client information, and reuse an existing direct thread when it already contains the relevant history.

For example, ask the reviewer a short question about Sarah’s October work in your existing direct conversation. If a decision affects an internal task, record the conclusion on that task as well. Chat keeps the conversation, but a message does not automatically reassign the task, change its status or fulfill a separate client request.

  1. Choose Chat in the left sidebar. Review the conversation list/search first; open an existing direct conversation if it already contains the discussion you need.
  2. Use the new-conversation control above the list. In the participant picker, select the direct-conversation option and search for the intended person. Compare their identifying details if names are duplicated.
  3. Select that one participant and start the chat with the dialog’s confirmation action. Read the conversation header before typing, so you do not put one client’s information into another conversation.
  4. Type the message in the composer at the bottom and send only when ready. Opening a conversation and composing a draft are separate from sending a message.
If a direct chat already exists with that person, reuse it instead of creating duplicates.
2) Start a group conversation

A group conversation gives several people a shared discussion and its own participant roles. Give the group a recognizable purpose and inspect its membership before posting. The group’s owner or administrator is a conversation role, not automatically the owner of every client mentioned.

For example, “Thompson onboarding team” can bring the preparer and reviewer together. Add the client only if that conversation should actually expose its contents to the client. An internal coordination group and a client-facing discussion should not be treated as interchangeable merely because both concern the same engagement.

  1. Open Chat and its new-conversation control. Choose the group option rather than starting several unrelated direct conversations.
  2. Select the intended participants and review the names before confirming. A group shares its discussion with multiple people; do not add another client simply because they belong to the same household or business.
  3. Enter a name that explains the group’s purpose, such as “Maple Grove — onboarding team”, then use the group-creation action. Check the resulting header and participant list.
  4. Send an introductory message explaining what belongs in this group. Use a separate conversation or request for information that should not be visible to every participant.

The group appears in your list and participants receive it in their chat view.

3) Invite people (including custom email)

An invitation proposes access; the recipient still needs to accept through the appropriate account flow. Check the address and conversation before sending. A pending participant is not proof that the person has joined or can see new messages.

For example, inviting a new colleague to an onboarding discussion is separate from sharing Sarah’s client record with that colleague. Review both permissions if the colleague can open chat but cannot find the client. If an invitation is expired or declined, inspect its state before resending rather than adding several near-identical email entries.

  1. Open the intended conversation and its details/participant controls. Read the current participants before choosing Add people. This changes access to a conversation, not membership in your staff team.
  2. Select an existing person or enter a custom email where the dialog offers that option. Verify the address directly; similarly named people may have different accounts.
  3. Review the people and conversation, then send the invitation with the explicit send control. Cancel the dialog if you were only inspecting it; entering an address is not a reason to send a real invitation.
  4. The recipient opens their own invitation and accepts with the invited account. Confirm the resulting participant state before assuming the person can read or respond in the conversation.
Invite statuses

Participants can be Active, Pending, or Declined until invite status changes. If someone declines or does not respond, you can resend or cancel the invite from Conversation details.

4) Send messages, files, and images
  1. In Chat, select the conversation in the list and check its header/participants. Read the recent messages so your response goes into the intended discussion.
  2. Write in the composer at the bottom. Use Reply on a particular message when the response needs that context, rather than starting an ambiguous new subject.
  3. If attaching a file/image, use the composer’s attachment control and check the selected file before sending. Wait for any upload result and remove an incorrect selection while it is still a draft.
  4. Send once and check the message’s visible state. A failed/not-sent state needs attention; Seen means it was read, not that a separate task or request has been completed.

Message appears immediately and updates other participants in realtime.

Use replies for context instead of sending separate "what is this about?" messages.
5) Use message actions
Common actions
  • Reply to a specific message (keeps context linked)
  • Edit your own message
  • React with emoji
  • Copy text
  • Forward to another existing conversation
  • Delete for me / delete for everyone (when allowed)
Important delete rule

If you sent the message, you can usually choose delete for me or delete for everyone. If someone else sent it, you can remove it only from your own view.

6) Manage chat settings
Settings you should know
  • Pinned : keeps a chat at top
  • Muted : silences popup noise
  • Archived : hides from active list
  • Delete for me : removes chat from your list only
  • Delete for everyone : owner-only permanent removal
Pin urgent chats. Mute noisy chats. Archive finished chats.
7) Understand permissions in group chats
Why this matters

Some actions depend on role (member/admin/owner).

Typical role actions
  • Rename group conversation (admin/owner)
  • Manage participant roles (owner has full role control)
  • Remove participants
  • Resend/cancel pending invites
  • Add people to existing group chats
  • Run high-impact conversation actions
8) Use search, forward, and message history tools
What to use
  • Conversation search: find chats by name and last message preview
  • In-conversation search: find messages inside one chat
  • Forward message: send one message into another existing conversation
  • Load earlier messages: scroll up for older history
Forward works only to existing conversations. If needed, create the target conversation first, then forward.
9) Manage files and images from one place
  1. Open the conversation containing the material and use its three-dot actions/details menu. Choose View attachments or View media where offered.
  2. Review the file name, sender and context before opening or downloading. Several periods can use the same file name, so inspect the document itself before using it as engagement evidence.
  3. Close the attachment/media view to return to the discussion. Downloading a chat attachment does not automatically file it into the correct company/year folder in Documents.
Why this helps

You do not need to scroll through long chat history to find files; Chat gives you a quick attachments/media center per conversation.

10) Understand message status and delivery states
What you will see
  • Sent : message reached conversation
  • Seen / Seen by X : other participants read it
  • Not sent : send failed
  • Retry : resend failed message quickly
  • Edited : message content was updated
  • This message was deleted : deleted for everyone
11) Invite acceptance flow (recipient view)
What recipient does
  1. Open the conversation invitation from your own email and review the sender and conversation. If the invitation is unexpected, confirm it with the firm through a known channel before proceeding.
  2. Sign in with the account matching the invited email when prompted. Use the registration option on the invitation if you need a new account; do not use another person’s account to accept for yourself.
  3. Return to the invitation and choose Accept invitation if you intend to join, or Decline if appropriate. Signing in alone does not necessarily accept it.
  4. After the success confirmation, use Go to chat and check the conversation that opens. Joining this chat does not automatically grant access to the firm’s unrelated clients or internal tasks.
Important behavior

Expired or revoked links cannot be accepted. Sender must resend a new invite.

Conversation rules that prevent common mistakes

Direct chat = one participant only To include more people, create a group conversation.
Group chats require at least two selected people + group name Bookwits enforces this to keep groups clear and searchable.
Duplicate emails are blocked in group creation The same email cannot be added twice in one group selection.
Starting a chat with an archived direct conversation reopens it If a direct thread already exists but was archived, Bookwits restores it instead of creating a second duplicate direct chat.

Notifications and unread behavior

Unread counts Conversations with unread messages update your unread totals automatically.
Popup notifications New messages can appear as toasts with quick open. Multiple events are grouped to reduce repeated popups.
When no popup appears (by design)
  • You are already viewing that same conversation in Chat
  • The browser tab/page is active and visible for that chat
  • Conversation is muted
Deletion toasts If a conversation is deleted for you or for everyone, Chat shows a dedicated deletion notification so the change is clear.

Troubleshooting (Common Beginner Issues)

"I invited someone but they are not in the chat yet"
  • Check if they are listed as Pending
  • Resend invite from participant actions
  • Confirm they used the same account/email for acceptance
  • If invite expired, cancel and send a new invite
"I am getting too many chat notifications"
  • Mute low-priority conversations
  • Archive old conversations
  • Keep only critical chats pinned
"I cannot perform a participant action"
  • The action may require admin/owner role
  • Ask group owner/admin to apply the change
"My message says Not sent"
  • Click Retry on the failed message
  • Check connection and try again
"I can’t add this email to the group"
  • A duplicate email is not allowed in one group
  • If this is an existing member, use that existing profile

Glossary

Direct conversation: One-to-one chat between two people.
Group conversation: Chat with multiple participants and role-based controls.
Pending invite: Invitation sent, not accepted yet.
Declined invite: Recipient declined. You can resend or cancel the invite.
Muted: Conversation still active, but notifications reduced.
Archived: Conversation moved out of main active list.
Delete for me: Removes chat/message from your account only.
Delete for everyone: Permanently removes chat/message for all participants.

Keep conversation roles separate from firm roles

A group conversation has its own owner/admin/member controls. Being the manager of a client does not by itself mean you own every conversation about that client. Open conversation details to see who is active, pending or declined and which actions you can perform.

Send, verify and retry responsibly

  1. Choose the intended conversation and read its participants before writing.
  2. Use Reply to connect your answer to the relevant message; attach the correct file or image.
  3. Send and review its visible state. Not sent requires a retry; Seen indicates reading, not approval or completion of a separate request.
  4. Before retrying after a connection problem, check whether the message already appears. Keep unrelated client material out of the conversation.

Understand what pin, mute and archive do not do

Pinning helps you find a conversation. Muting reduces notifications. Archiving removes it from your active list. None changes the other participants’ access or completes a related task. Use the All/Unread/Pinned/Archived views and clear conversation search when a chat appears to be missing.

Choose the scope of deletion and forwarding

Delete for me affects your view; Delete for everyone has wider consequences and is permission-dependent. Read the action carefully before confirming. Forwarding sends content into another existing conversation: inspect that destination’s participants first, especially when the original message contains client information.

Work with records and attached files

Use the available Link record control to add useful client-work context. Use the conversation’s attachments/media views to find earlier files without scrolling the entire history. A file sent in chat is not automatically the document that completes a separate upload request; keep required deliverables in the workflow that requested them.

Example: preserve a decision without confusing a message with approval

Sarah posts a question in the task conversation and attaches a supporting image. Jordan replies to that specific message so the answer remains connected to the question. Before forwarding it to a reviewer conversation, check the destination participants; a useful internal explanation can still contain information inappropriate for another client’s group.

If Sarah writes “Looks good” in chat but the task has a Review and approve action, ask her to use the actual action when that is the required decision. The chat provides context; it does not necessarily submit the approval. Likewise, Seen indicates that a message was read, not that the recipient agreed or finished a separate request.

Use mute to reduce notifications and archive to tidy your active list. Neither revokes the other person’s access or deletes the conversation for everyone. If a send fails, inspect Not sent and the visible history before retrying. Deleting for me affects your view; broader deletion has a different consequence. Read the chosen scope rather than assuming every Delete action is harmless cleanup.

Current application screen examples

Chat: conversation search, status filters and New chat
Chat: conversation search, status filters and New chat. Application screen with illustrative sample data. The controls shown here use the English interface. Open the full-size screenshot

Start the right kind of conversation

  1. Open Chat in the left navigation. In the conversation panel, choose New chat; the empty conversation area also offers a New chat button. Both open the same composer.
  2. Choose Direct chat for exactly one other person, or Group chat for at least two selected people and a group name. Make this choice before selecting participants.
  3. Use Search by name or email, then the Team members or Clients + Contacts source. Wait for the choices to load and compare the person’s identifying details before selection.
  4. In Direct chat, selecting the person starts the conversation immediately. Do not select someone merely to preview the form or test a search result.
  5. For Group chat, select the intended people, enter a useful group name and review the whole participant list before Create group. A name such as “September bookkeeping questions” explains the purpose better than “New group.”
New chat: an unsaved group draft and the Custom participant source
New chat: an unsaved group draft and the Custom participant source. Application screen with illustrative sample data. The controls shown here use the English interface. Open the full-size screenshot

The illustrated group draft has a name but no selected people. It is not a created conversation. Cancel leaves the composer without creating that group. Reopening New chat starts again with Direct chat, so check the mode rather than assuming the previous Group choice was retained.

Use Custom invitations deliberately, not as a search workaround

The Custom source lets you enter an email for someone not listed. Review the address before Add and the subsequent creation/invitation actions: the person joins after accepting the invitation email. This is not the same as selecting an existing colleague. Do not invite a second account simply because the desired person has not loaded or because a search has no result yet.

Example: an internal question for a colleague normally belongs in a Direct chat with that colleague. A discussion that includes a client and several firm participants needs a deliberately reviewed Group chat. Before posting documents or personal details, open the conversation’s participant information and confirm who can read them. Chat conversation, task comments and the client-task request actions remain different places; a message alone does not submit or approve a request.

Owner, Admin and Member: permissions for this workflow

Staff roles affect the people directory: Owner/Admin can find team-wide client/contact choices; a Member normally uses shared clients, with existing direct-chat relationships also able to remain in the directory. An existing conversation is not a grant to the full client profile. Conversations themselves require participation; workspace management does not mean every private chat is readable.

Group roles are a different permission system. A staff Member who creates a group may be that group’s Owner without becoming the workspace Owner. A workspace Admin is not automatically an Admin of every chat group. Open the group’s conversation details to see its participants and roles.

  • Group Member: participates in the conversation but does not get the group’s name/image or participant-administration controls. Personal pin/mute settings and Delete for me are not shared group administration.
  • Group Admin: can manage permitted group details, add people and handle permitted participant/invitation actions. Removing a participant requires a lower group role; an Admin cannot remove a peer Admin or the group Owner.
  • Group Owner: can change participant roles, promote/demote group Admins, transfer ownership and use Delete for everyone. If other active people remain, transfer ownership before leaving the group. Delete for me does not delete the conversation for everyone.

Compare all staff roles, feature restrictions and exceptions

Want help setting up Chat workflows for your team? Book a demo and we’ll help you design a clean chat structure for client communication, internal collaboration, invites, and notification control.