The Leads area is Powerlily’s pre-sales pipeline. It brings together website enquiries, referrals, imports, API submissions, canvassing, manual entries, and Pericles-created leads before they become quotes and pro
List and board views
Use the list for searching, filtering, sorting, bulk work, and exports. Use the board to see leads grouped by pipeline stage and drag cards between stages. Powerlily remembers the view you last used.
Your company has one configurable lead pipeline. Stages can be renamed, reordered, recoloured, and classified as Open, Won, or Lost. Moving a lead into a won or lost stage completes it; moving it back to an open stage reopens it.
What a lead record contains
- Contact details, address, power bill, service size, source, and captured form answers
- Assigned owner, original setter, branch, territory, and referral details
- Stage, tags, notes, comments, tasks, events, reminders, and files
- Activity and stage history
- Links to the converted quote, project, and client when applicable
The setter records who sourced the opportunity. The assigned owner records who is responsible for it now. Reassignment does not erase setter credit.
Lead intake channels
Leads can enter Powerlily through manual entry, hosted or embedded forms, website form capture, the REST API, customer referral links, CSV imports, Lilypad canvassing, and Pericles-assisted creation.
The intake channel describes how Powerlily received the record. The source describes the acquisition source reported or assigned to the lead. Keeping them separate makes attribution reporting more useful.
Forms, custom fields, and attribution
Lead forms can contain built-in contact fields and company-defined questions. Required fields and conditional visibility rules are applied to submissions. Powerlily snapshots the form questions on the lead, so later changes to a form do not rewrite earlier answers.
Hosted and embedded forms can retain landing-page, referrer, UTM, click-identifier, form, and channel details. Website capture can observe an existing form and send recognised submissions into Powerlily without replacing the form.
Public intake can use origin restrictions, a honeypot, optional CAPTCHA protection, bounded captured fields, and duplicate controls. When a new lead’s email matches an existing company lead, Powerlily flags it as a possible duplicate for review.
Routing and ownership
A lead form can leave new leads unassigned, send them to one user, or distribute them across a persistent round-robin pool. Assignment notifications tell the new owner when work lands with them.
Canvassing preserves the setter while allowing the lead to route to a closer. Geocoded leads can retain territory context, and branch and record-scope rules still control who may view or receive a lead.
Searching, filtering, and export
Search across names, email addresses, phone numbers, addresses, and messages. Filters can narrow the visible pipeline by status, date, source, intake channel, form, branch, and other available fields. Filters never expand access beyond the user’s role, record scope, or branch visibility.
CSV export uses the complete filtered result set rather than only the current page. It includes pipeline and acquisition fields, ownership, core lead details, and collected custom-field answers.
Converting a lead
Convert a qualified lead when it is ready for design, pricing, and proposal work. Conversion creates or links the quote and project while preserving the original lead, attribution, setter, owner, and acquisition history.
A lead may also be converted by an automation. Actions before Convert to quote operate on the lead; supported steps after conversion continue against the resulting quote.
Automations
Lead automations can respond when a lead is created, assigned, enters a stage, receives a canvassing outcome, or remains inactive. A rule can assign an owner, add or remove tags, create tasks, notify staff, send email or SMS, call a webhook, move the lead, or convert it into a quote.
Insights
The Insights view reports visible lead performance, including volume, signed-quote conversion, sources, intake channels, forms, pipeline distribution, response activity, recent trends, and estimated pipeline potential. Analytics use the same access rules as the working views, so totals may differ by user.
A practical lead workflow
- Capture the lead and its attribution.
- Route it to the correct owner while preserving setter credit.
- Work tasks, comments, events, files, and follow-ups from the lead page.
- Move it through the configurable pipeline.
- Convert qualified opportunities into quotes and projects.
- Use filters, exports, automations, and Insights to review performance and reactivate stalled leads.
Related guides
- Creating Lead Forms and Capturing Website Leads. Configure hosted, embedded, and captured website forms.
- Canvassers in Lilypad. Capture and follow up with door-to-door opportunities.
- Workflows, Clients, and Quotes: How the CRM Fits Together. Understand what happens after conversion.
- Automating Your Workflow: Triggers, Steps, and Conditions. Automate routing and follow-up.
- Analytics, Reporting, and Performance Insights. Review pipeline and conversion performance.
