How Does the Internal Chat Linked to Each Contact Work Inside the Sales Force Template?

In Jestor, each contact in the sales template has its own chat, where the team logs internal conversations about that specific customer, separate from the contact's data and the external communication channel.

Why separate internal chat from contact data

Internal discussions about a deal — like "this customer is a priority" or team notes — shouldn't get mixed in with the contact's registration data. A dedicated chat keeps that exchange organized without cluttering the main form.

What the contact's internal chat offers

A conversation linked exclusively to that contact record
History accessible whenever that contact's card is opened
A clear split between the information section and the communication section
Also available on company registries, following the same logic

How to use the internal chat linked to a contact

Open the desired contact's card in the CRM
Switch to the chat/communication tab or section
Log notes or align next steps with the team
The history stays saved on that contact for future reference

Process automation with centralized context

Keeping the chat linked to the contact, rather than loose in another channel, prevents important deal information from getting lost in separate WhatsApp or email conversations, centralizing context right inside Jestor's CRM.

Table Summary

Feature	Where it lives	Visible to the customer?
Contact's internal chat	Inside the contact's card	No
Conversation history	Saved on the record itself	No
External communication channel	Separate from the internal chat	Yes, when applicable

Video Tutorial: Step by Step

Video: Sales Force System — video tutorial showing this feature in practice, right inside the Jestor interface.

Frequently Asked Questions

Is the contact's internal chat visible to the customer? No, it's an internal team communication, separate from the external contact channel.

Does this linked chat also exist on company records? Yes, companies have the same internal chat structure linked to the record.

Does the chat history stay saved permanently? Yes, it stays tied to the contact record and accessible whenever the card is reopened on jestor.com.

Get to Know Jestor

With Jestor, you can automate workflows, connect different areas, and build internal systems your way — all without code and with AI support. Check out Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize