Keep preferences separate from requirements.
What a customer wants is useful context. It does not establish what the site or installation needs.
Start with the request.
Prepare for
the right review.
Give your team the customer’s goal, the available project details, and the questions still to answer—before an electrician reviews the work.
Discuss your electrical workflow Build an example briefFrom a project idea to useful context
A better brief starts
with better information.
Choose the notes to include in this fictional lighting inquiry. See how each detail helps prepare the next conversation.
Planned lighting inquiryFictional example
“We’d like pendant lights over the kitchen island. Could we discuss what’s involved?”
For the electrician
A clearer starting point.
Requested workDiscuss pendant lighting for a kitchen island
Room details
Not included in this example brief yet.
Fixture preferences
Not included in this example brief yet.
Preferred timing
Not included in this example brief yet.
Qualified review comes next
Confirm the site, requirements, and suitability before agreeing scope, price, or a visit.
0 of 3 customer notes included
Customer preferences help prepare the discussion. This example does not assess an installation or send a request.
Your expertise stays central
Gather the information.
Keep judgment
with the electrician.
Explore AI controls Mark the details that are still unknown.
Missing site information or an unanswered technical question should remain visible for the right person to resolve.
Agree the work before making commitments.
Have the responsible person review scope, availability, and pricing before the customer receives a confirmed next step.
One useful workflow at a time
Choose where your team
needs clearer handoffs.
Start with a recurring request. Define the questions, current tools, and review points around the way your team works.
Planned work inquiries
Collect the project goal, location, and available details before your team discusses the next step.
Estimate preparation
Organize the customer’s information and open questions for the person reviewing the proposed work.
Questions about a job
Bring the client’s update back to the relevant work and identify the person who should respond.
Build the first workflow with your team.
Review the routine requests, the missing details, and the exceptions together before launch.
Before you start
A few practical questions.
Can we start with planned project inquiries?
Yes. A lighting project or another repeatable inquiry can be a useful starting point. We agree the questions, information sources, and team review before building the workflow.
Does a complete brief mean the work is approved?
No. The example brings customer notes together for discussion. Site conditions, technical requirements, suitability, and the agreed scope still need qualified review.
How are safety questions or uncertain requests handled?
We define when the request should move to an appropriate person, who receives it, and the fallback if they are unavailable. This intake example does not diagnose faults or provide electrical work instructions.
Can this work with our existing tools?
We review your phone, inbox, scheduling, and business software, then confirm any proposed connection and its limits. Booking, quoting, or changing records is separately scoped and tested.
Which details does your team
keep having to chase?
Bring one real inquiry. We’ll map a useful first workflow together.
Map your first workflow