Capture + tags
Custom properties: partner_id, source=CP. Duplicate merge across partners.
CP intake, SLA, and status back to the partner
CP-submitted leads get SLA, source tags, and status back to the partner instead of disappearing into a shared spreadsheet. Developers still run Buyers & Tenants and Bookings on the Project; the partner needs a tagged source, an SLA clock, and a WhatsApp or email status — without handing them the whole omnichannel inbox.
- Source + partner tags
- SLA on new enquiry
- Status loop to CP
Spreadsheets make partners stop sending
If a channel partner cannot see whether their lead got a site visit, they send the next one to a competitor. You do not need to give them Agent Studio. You need source and partner on the deal, workflows that notify them on stage change, and a qualifier that still talks to the buyer on WhatsApp. Duplicate leads across CPs should merge, not create two Bookings. Wallet-only pricing means the developer Organization pays usage, not a seat per partner.
Omnichannel journey
Partner forwards on WhatsApp or a form; buyer is qualified on their own thread; voice confirms the visit; partner gets email or WhatsApp status — not the buyer's private chat.
- CP intake WhatsApp, form, or email. Tag partner. Start SLA on new enquiry.
- Buyer WhatsApp Separate conversation. Qualifier + visit offer. Do not CC the CP on every bubble.
- Phone Visit confirmation with the buyer.
- Status out Workflow emails or templates to the CP on Qualified / Visit / Booked.
How it runs in CoPulse
Intake can be a small agent or a form into CRM. Buyer-facing qualifier is the main conversation agent. Workflows notify the CP. Do not run autonomous blasts to the partner list as if they were buyers.
Buyer qualifier
Same RE Qualifier as developers, knowledge on the project.
Workflows
On stage change, message the partner channel with status only.
Router
CP intake vs buyer chat are different surfaces — do not let the FAQ agent reply to a partner dump as if it were a 3BHK question.
Operator setup
Developer Project. Partners are contacts or a CP list, not full users unless you invite them.
Pipeline + custom properties → Channels → Studio (buyer qualifier) → Router rules for CP vs buyer → Workflows for status templates → wallet. Gupshup WhatsApp.
Two threads, one Booking
Ramesh the CP dumps Priya on WhatsApp. Router sends that surface to intake, not to the project FAQ bot. Priya is qualified on her own number. Ramesh receives a status template when she hits Qualified and again when the site visit is booked — never her private bubbles. SLA is time-to-first-buyer-message, implemented as a workflow on CP-sourced new enquiry. If two CPs send Priya, duplicate-leads logic should keep one Booking. Partners do not need seats; the developer Organization wallet pays. Spreadsheets cannot do this loop, which is why they churn CPs.
Commission can live as a custom property; CoPulse will not pay it out. Invite a partner as a user only if you truly want them in inbox — most developers should not. Status templates must stay after the 24-hour window. Buyer qualification still uses project knowledge bases. This ICP is the trust layer on top of the developer pipeline, not a second CRM.
CP vs buyer hops
Two people, two threads, one Booking.
| Hop | Channel | What happens | Owner |
|---|---|---|---|
| 1 | WhatsApp / form | CP submits lead | Intake |
| 2 | Buyer qualified | Qualifier | |
| 3 | Phone | Visit confirm | Voice |
| 4 | WhatsApp / email | Status to CP | Workflow |
Playbooks for this team
Jobs are omnichannel. Each link is one URL, not a WhatsApp-only clone.
Frequently asked questions
Partners, SLA, and privacy.
Do partners log in?
Not required. Status via template or email is enough. Invite them as users only if you want them in the inbox — usually you do not.
SLA how?
Workflow on new enquiry with CP source. Measure time to first buyer WhatsApp.
Commission?
Store on the deal as a custom property. CoPulse is not a payout engine.
Autonomous to partners?
Avoid. They are not a dormant buyer list. Sends/reads metrics would not mean a visit booked.
Pricing?
Developer wallet. Pricing.
Same as brokers?
Brokers operate the inbox. CPs submit and receive status. See the brokers ICP for the shared-inbox motion.
Related
Parent hub, sibling teams, and product surfaces this ICP actually uses.
Real estate hub
Buyers & Tenants, Bookings, site visits — directory of ICPs and jobs.
Back to hub →Developers
The Project that owns inventory and wallet.
Open →Brokers
When the partner is actually running the buyer chat.
Open →Pipeline
Tags, stages, workflows on enter.
Explore →Wallet-only pricing
The developer Organization pays usage for buyer WhatsApp and CP status templates.
See pricing →Stop losing CP trust
Tag the partner, qualify the buyer, send stage updates — without a weekly Excel.
Get started free