Partner integrations

Luminous's view of three weeks of channel-partner leads: 186 in, 172 projects, 142 proposals sent back, 24 won, 21 hours median from lead to proposal. Below, every partner and every designer with the same numbers.

Leads arrive from M-Partner and are given to a designer in the same second, by territory and then in turn. One lead is past the 48-hour target and has been escalated; one designer's leave is already planned for.

The designer, Kavya Rao, sees a normal project in its first status, Customer Inquiry, with where it came from, the partner's fields locked, the address already on the map and a checklist of what is left.

Kavya generates the proposal: 8 Waaree 580 Wp panels, 4.64 kWp, ₹1,77,200 after subsidy. SurgePV sends M-Partner the share link and PDF, and the page shows every step, including three refused tries before it got through.

Luminous's Admin makes a key for M-Partner. It belongs to this organisation only, can do three things, expires in 12 months, and is shown once; SurgePV keeps only a hash.

Each M-Partner field lands in a real SurgePV project field, with the example lead beside it. Defaults set the status, designer, design profile and project name, and four rules hold a lead instead of creating it.

Pick the events M-Partner should hear about and the URL to call. A test lead runs the whole trip in the sandbox, from a staging lead to a signed proposal.ready, before anything goes live.

Every lead in and every event out, on one timeline. After the signing secret changed, M-Partner refused three deliveries; once Luminous IT updated it, one click re-sent the same event and it went through.

Luminous decides which partners can send leads, which states its design desk covers, how leads are assigned (here by territory, then in turn), the 48-hour target with reminders and escalation, and what gets held.

Three leads did not become projects: the same mobile from a second partner, an address that cannot be found, and a site outside the covered states. Side by side, the Admin attaches, creates or rejects, and M-Partner is told.

For an EPC that runs sales in Zoho, here Vardhan Energy Systems in Pune: pick the deal stage that starts a design and map the deal's fields. It is the same screen as M-Partner, marked Coming.

For a US EPC on HubSpot, Northwind Commercial Solar: deal stages and SurgePV statuses mapped in both directions, and one owner per field, so sales edits in HubSpot and designer edits in SurgePV never overwrite each other.

The public page an IT team builds against: authentication and scopes, rate limits, create, get and outcome endpoints with real examples, webhooks with signature checks, errors, sandbox and the rule that v1 only gets additive changes.

For the buyer's IT and legal teams: keys scoped to one organisation and stored hashed, organisations kept apart, signed webhooks, rate limits, what data is kept and for how long, and how the DPDP Act, 2023 roles split.

A Bihar partner sends a lead for a house in West Bengal, which the design desk does not cover. It is held, not created. The Admin can make it once, add the state, or reject it with a message that goes back to the partner.

M-Partner's receiver has answered 503 since 10:05. Leads still come in and designers keep working; 23 events wait and retry with the same ids. The page says who was told, when the next try is, and how to reach a partner in the meantime.

The Admin rotated the M-Partner key this morning. 69 calls since then still used the old key, so the page warns before it stops working on 3 Nov. Rotate and revoke are explained side by side, and signing-secret rotation now overlaps for 24 hours.