Guide · Workflow on stage change

Workflow when the visit is done

Example: visit done triggers EMI WhatsApp, stage update, and an RM task via automation workflows. That is an event, not a bot personality. If you try to do it with the inbound qualifier, you will send EMI PDFs to people still asking BHK. Agents → Workflows listens for pipeline stage change on the Project.

Event in, actions out
Template must already exist
Not the qualifier

Start free Post-visit follow-up playbook

Definition

A stage-change workflow is an event-driven automation that runs when a CoPulse pipeline stage (for example Visited) is set: send an approved library template, update a CRM property, create an RM task, or start another configured action. It does not hold a conversation and it does not use autonomous success metrics.

Why chatbots make bad stage machines

Qualifiers want to be helpful and fire EMI during New enquiry. Growth drips fire on clocks, not on Visited. Autonomous wants a list. None of those is ‘when this card moves.’

Post-visit-followup playbook is the job. This guide is the workflow mechanic.

HowTo: Visited → EMI + RM task

Stage must be real (ops marks Visited, not a read receipt). Template approved. Workflow attached on the Project.

Make Visited mean attended Gate/RM. No-show guide otherwise.
Approved utility template EMI / next steps. Not a launch teaser.
Agents → Workflows Trigger: stage = Visited. Actions: send template, create task, optional property.
Handoff path If they reply with objection, inbox RM. Checklist guide.
Do not also blast them from a drip the same hour Three systems. Coordinate.

How it runs on the platform

Workflow runtime. Conversation agent only after a reply. Autonomous not required. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: Saturday 12:40 gate marks Visited

Six families came. RM moves cards to Visited. Workflow sends utility EMI WhatsApp (window may be open from morning confirm — if closed, template still required). Creates RM tasks. Insights 48h loan-cold cue is still an operator cue later, not this workflow. If a family was a no-show, they never hit this trigger — recovery playbook instead.

Leasing Project: trigger Viewed → application link, not EMI. Rental vs sales guide.

Stage × example workflow

Ideas, not a hidden pack we invent per industry goal kit (G10).

Stage event	Typical send	Task	Do not
Visited	EMI / next steps utility	RM price follow-up	Launch marketing
Site visit booked	T-24h reminder	Ops roster	Mark Visited
Qualified	Optional brochure after fields	—	Saturday without cap
Loan disbursal	Docs utility	RM banker	Auto Booked
Dormant	Usually autonomous/campaign, not this	—	EMI as if they visited

Honest limitations

Workflows do what you configure. No adaptive branch from outcomes (G2). Template must exist (G1). Industry goal kits stub (G10). SMS not live.

Keep this Workflow on stage change article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Agents → Workflows. Pipeline Visited. Library utility. Inbox. Post-visit-followup playbook. Canonical playbook: Post-visit follow-up playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Three runtimes. Visited stage. AI agents.

Frequently asked questions

Admins looking for ‘if visit then WhatsApp’ in the qualifier prompt.

Is this the same as a Growth drip?

No. Drips are clocks. Workflows are events. Both may send templates.

Can a workflow stop an autonomous task when Visited?

Not as a shared contract (G18). Pause tasks as an operator if needed.

Who marks Visited?

Ops/RM. Reads and STT do not.

EMI before they visited?

Wrong trigger. Keep it on Visited.

Property managers?

Different actions. Do not copy EMI.

Wallet?

Each send meters. Preview if you bulk-move stages. Pricing.

Hub, sibling guides, canonical playbook, product, pricing.

Fire on Visited, not on a hopeful chatbot

Agents → Workflows, utility template, RM task — post-visit playbook.

Get started free