When should a closed conversation generate a new card instead of reopening the previous one?

In Jestor, a WhatsApp conversation that's already been closed and receives a new message from the client automatically generates a new card, instead of reopening the previous record — this is the standard status logic for conversations within the native integration.

Why not automatically reopen the previous conversation?

Every conversation in Jestor follows a status logic: new conversation, in progress, closed, and archived. A closed conversation represents a service that's already been resolved. If the client writes again after that, it's usually a new matter or a new need — so the system creates a new card instead of mixing that new contact with the history of the previous service.

How does this status flow work in Jestor's WhatsApp?

A new incoming message automatically creates a card linked to the process connected to that number.
While the conversation is active, its status stays as new conversation or in progress.
Once resolved, the card moves to closed, and can later be archived.
If the client writes again after it's closed, a new card is generated.

Conversation status	What happens
New conversation	Card created from the first incoming message
In progress	Card keeps receiving message exchanges
Closed	Service resolved; a new message generates a new card
Archived	Conversation stored outside the active list

Why choose Jestor?

This status logic helps keep the CRM or support center organized, since each WhatsApp card reflects a specific service, with attachments, phone number, and contact name filled in automatically from the conversation.

Frequently Asked Questions

Can this status logic be configured manually? The conversation's status (stage) is configurable within the process linked to the WhatsApp number.

Does an archived card also generate a new card if the client writes again? Yes, the same closed-conversation logic applies to archived conversations.

Does this work for every connected number? Yes, the status logic applies to any WhatsApp number integrated with the account.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know 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