01 — From a set of messages to an ongoing relationship
Anyone who writes in to Chatwoot becomes a contact, and the contact profile is where everything the team knows about that person lives in one place: basic identity details, the company they belong to, every conversation held with them across every channel, custom attributes, and free-form notes.
The value shows up most clearly when the same customer writes in again. Instead of starting from zero, the team opens the profile and immediately sees what was discussed last time.
Before answering anything beyond a routine question, it is worth a quick look at three things on the contact panel: the name to use in the reply, any previous conversation that may be relevant, and the custom attributes that look like minor detail but often change what the correct answer actually is.
- Identity — name, email, phone number, avatar, and locale
- Company — the organization a contact belongs to, useful for B2B teams
- Conversations — every conversation ever held with this contact, across all channels
- Custom attributes — fields the team defines to track what matters for this specific contact
- Notes — free-form notes about the customer, separate from private notes inside a conversation
02 — Custom attributes: small fields that make replies sharper
Standard fields such as name or email are the same for every business. Custom attributes are fields a team defines for itself, to track whatever actually matters to that business — a subscription plan, a signup date, an account ID.
Custom attributes come in two shapes: ones attached to a person, such as plan or signup date, and ones attached to a single conversation, such as an order number or a bug severity. Choosing the right one at creation time matters, because it decides whether the value follows the person or stays with that one conversation.
The real payoff is not storing the data. It is being able to use it immediately in the screens the team already works in.
- Fill canned response variables automatically, so a reply pulls in the customer plan without anyone typing it
- Drive filters, to view only conversations from a specific customer segment
- Drive automation rule conditions, to route important customers to the right team without manual work
03 — When dozens of conversations need handling at once
Most days the queue behaves. Some days it does not, and forty new conversations land at once from the same incident. Opening each one to do the same thing over and over is not a good use of time.
Bulk actions let a team select several conversations together and act on all of them at once: assigning an owner, adding or removing a label, or changing status across the whole batch.
The caveat is that bulk actions suit a decision already made about what to do with that group. They are not a substitute for reading and judging each conversation individually — if it is still unclear how a given conversation should be handled, opening it on its own is still the right call.
04 — Saved filters pay off more the longer they exist
Building a filter with several conditions — status open, a specific assignee, a particular label — and saving it as a folder means the same view is one click away next time, and it always reflects current data rather than a stale snapshot.
The same idea applies to the contact list under the name segment. "Every contact on the top-tier plan who wrote in this month" becomes a view that can be reopened at any time.
A simple rule of thumb decides when to save one: if the same search or the same set of conditions gets typed more than twice a week, that is the signal it belongs in a saved folder or segment.
