CP leads with partner, SLA, and status — not weekly Excel

Definition

Channel-partner lead intake is the job of accepting a partner-origin enquiry, tagging the Booking with the partner, running qualification and visit booking on the developer Project, and sending status updates to the partner on WhatsApp or email instead of a Friday spreadsheet.

Channel managers live in Excel because CRM never stored the CP

Partners dump WhatsApp lists. Interns copy names. Nobody returns status. CoPulse: custom properties, workflow SLA notify, library template to the partner’s number. Partners do not need a second Organization if you only send them templates — or they can be a separate Project; you choose. Do not promise a CP login portal we did not ship.

Omnichannel sequence

CP WhatsApp/email in → qualify on buyer WhatsApp → voice visit → status out to CP on WhatsApp/email.

How it runs in CoPulse

Conversation agent for the buyer. Workflows for SLA and partner status sends. Campaigns only if you broadcast to many CPs. Autonomous not for partner politics. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.

Operator setup

Custom properties, CP status templates, router, wallet for partner updates.

Ramesh sends three buyers before noon

Each becomes a Booking with partner=Ramesh. Qualifier works the buyers. One books Sunday. Workflow sends Ramesh the visit-booked template. Friday Excel does not happen. Click-path: inbox CP thread, three Bookings, workflow log.

Developers ICP plus channel-partners ICP both link here. Illustrative blitz funnel on the buyer side. Pricing: buyer hops plus CP status sends on the Organization wallet.

Operators assemble this job on the Project. Click-path remains Setup → Customers properties and pipeline → Library CP-status templates → Studio → Router → Workflows on stage change → wallet. Keep the quotable definition in the brief for the team: Channel-partner lead intake is the job of accepting a partner-origin enquiry, tagging the Booking with the partner, running qualification and visit booking on the developer Project, and sending status updates to the partner on WhatsApp or email instead of a Friday spreadsheet. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, New enquiry, WhatsApp overlay, Channel partners, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the visit truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The Channel-partner leads playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.

Channel sequence (one job, not extra URLs)

CP job hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Buyer-side estimates from the blitz template. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.