40

Can you summarize all this information? My manager wants us to review these notes: "35-minute call. Erik Lewis The customer had a previous website with us that he really liked (template, colors, images). The agent applied the color and template changes during the call and invited the customer to review the new website flow live in order to take notes on additional changes. However, the edits were not completed before the second call because the request was not submitted by the agent. What could have been done better: Since this customer is on the Growth plan, the agent could have offered more premium features instead of simply showing the updated website. Since we were already doing a revamp, we could have impressed him with some cool interactive custom sections. The customer requested a new page for “Bits,” and the agent mentioned adding it to the Services section. However, with the features available on the Growth plan, we could have created a dedicated page for this request. Additionally, one thing requested during the call—adding the number of years in business—was missing from the submission." "35-minute Call – Gabriely The customer had already reviewed the new website before the call and immediately brought up that a document he previously shared was not followed during the build. Throughout the call, the agent allowed the customer to take complete control of the conversation. The customer repeatedly shared his screen and restated the same points, but the agent did not check the CMS to verify whether the mentioned information had already been added. There was no indication that the agent was taking notes or guiding the conversation. Overall, it was a poorly managed call. Since it became clear that the edits would be extensive, the agent should have taken ownership of the call, asked clarifying questions, and worked with the customer to create a structured plan for the required updates. For example: Header: Customer wants slides and CTA buttons Home page: Which sections to include and what content Solutions page: Define sections and gather content Industry pages: Clarify structure and specific content ... and so on. While the request submitted by the agent made sense for her, it lacked the full context for the edits agent. T Additionally, the customer mentioned that CS (Customer Support) reached out and claimed the initial intake form (SmartIntake) was lost. This is not true — we had that information from the beginning. During the call, the customer also expressed a desire for a more interactive website. This would have been a great opportunity to explore custom code options and gather more specific details on what he envisioned. Unfortunately, after the second call, the customer submitted more requests, and the end result was a cancellation due to us not delivering the outcome he expected." "47-minute Call – Ariana PERFECT CALL The customer was frustrated because the page was missing much of the information she had submitted—most of which required custom code. Ariana did a terrific job conducting the meeting. She carefully reviewed the submitted information, managed the customer’s expectations, and offered appropriate solutions. She went through the document together with the customer, double-checking and comparing it against the page we had created. She remained calm, professional, and friendly throughout, even though the customer was visibly angry and frustrated. No improvements needed—she was spot on." "17min meeting - Amy Not a good start because the customer joined the call late, he said he was missing the call link, and tried to contact CS for it. The business name was wrong, and the customer expressed dissatisfaction from the start (important to note they filled the form with the name used by the build team), the customer was frustrated that the website looked cold and lacked the pics he shared. The customer didn’t want to proceed with the website presentation because it was not matching his vision, mentioned how deeply disappointed he was, and gave a vague instruction that “the website needs to be for his speaking services”. The DLC agent mentioned that they would review the information submitted to avoid having the customer repeat himself, but he said, “if I’m disappointed again, I will cancel”. This is the perfect opening for pushing for more details, especially because he also mentioned that he didn’t want the team to rush with the changes. It seems like opportunities for clarifying points were not properly used, which could’ve prevented the issues that created a second request. The main impression here is that the agent was afraid of pressing the customer for information, even when he was clearly interested in making this work by giving us enough time to fix things. Opening the raw data and reading the form with him would’ve clarified a lot of points. " "20ish min meeting - Astrid This was a case where the customer hated the whole website, and because of this, the meeting was totally focused on what they didn’t like. One of the main points that the customer mentioned multiple times was “I don’t want a basic website”, this impression is an important information that could’ve been provided to the team. Since she was unhappy with the results but willing to keep talking about the details they want to improve, the DLC agent could press a bit more on certain aspects, the lack of specific questions, sharing examples, and the proper flagging in the first request resulted in bad communication between the team and the customer. Just to make sure, I checked the follow-up after the first revamp and she mentions that the information was not used correctly, this might be a result of a communication that happened on the first meeting (DLC agent saying “you can email the information later but in the meantime, I will submit a request”; so no guidance or enough information gathered). The logo request mentioned was also not included in the first request. Considering all of the above, improvement could be made by: Agent sharing examples Understanding the information the customer is providing and making the correct questions (where would you like this? What is important to bring attention to?) Flagging the tone of the meeting on the request submission Collecting more visual examples of what they are after " "60 min meeting - Ariana A lot of good points here to use as reference: 1) the DLC agent proactively showed the example pages on the meeting as soon as the customer mentioned them; 2) when it was said the information was incorrect, the DLC agent also took the initiative to check the raw data to see what went wrong; 3) they did a check of all the information while on the call and confirmed with the customer what we had received and what they wanted to include. These organized not only enough content, but also clarified the points the build team misinterpreted during the initial phase. Ariana took ownership of the meeting and didn’t let the customer lead the conversation, this was a key point to ensure the PBE team would have information and that the customer would work together with us. " "25 minute call. Marsha clearly has good product and edits knowledge, but the level of detail could have been deeper in order for it to be a more fruitful call. Overall, the customer lead the meeting and was spitting out requests left and right, and Marsha would rein them in with what was realistically possible without making them upset - she's very good at this. The other improvement which she could have done was to show them some example sites in order to get a better feel for what they want. Script I'm thinking of so far would be along the lines of: ""Before we go any further your own website in detail, I’d love to quickly show you a few great sites we’ve built for other businesses similar to yours. This really helps because sometimes it’s easier to react to real visuals rather than imagining what something might look like. You’ll be able to see different layouts, styles, and features in action — and we can pinpoint exactly what you like (and don’t like) for your own site. Here’s the first one. Notice how we’ve handled [CTA / header image / about section] here. This second example is a bit different... it uses [full-width banners / bold colors / a more minimal design] for a cleaner look. And finally, here’s one with [dynamic moving section / styled images / product designs ] which can work really well for your type of business. When you look at these, which one feels closest to the style or structure you’d like for your own site? Is there anything in these designs that really stands out to you. Either because you love it or because it’s not quite your style? (Pause and encourage open feedback. Capture specifics like colors, fonts, layouts, image style, placement.) Great — now that I have a clear idea of your visual preferences, we can look at your own site with those in mind and make sure we’re moving toward exactly the look and feel you want."" " "34ish minute call. Marsha again, this time took a lead in the meeting as it was a customer that was more laid back and quiet, and had been with us a long time without the latest updates to her site. So this call was very much ""by the script"". Marsha did have great suggestions for the website and category specifically, again showcasing her great product and edits knowledge. However, it would definitely have benefitted from an example page showcase again, in order to guide the redesign that she was suggesting. Marsha also missed a few things that I would have suggested, such as a dynamic stats section, BUT if she had showed the plumbing example page that we have, she would have seen it and been able to ask the customer if they want something like that! Based on this so far, I'd suggest that for finding the right example site to show, they follow these steps: Onboarding Call – Example Website Selection Checklist 1. Match by Business Category Start here: Choose examples from the same or closely related category (e.g., plumber > can show plumber, electrician, etc. café > can show bakery, deli, etc.) If exact matches aren’t available, other ways to select are: - Service delivery style (e.g., in-person booking vs. e-commerce) - Target audience (e.g., local customers vs. nationwide buyers) - Website goals (e.g., lead generation, bookings, online store) 2. Match by Requested Features or Sections Review any pre-call notes or edit requests (or anything customer says during the initial part of the call) to identify: - Specific page requests (e.g., “About”, “Services”, “Blog”) - Design elements (e.g., image gallery, header image, logo, booking form) - Functional features (e.g., external links, CTA, widgets, 3rd party code) 3. Match by Design Style Preference If the client has mentioned preferences before (or e.g. they completely changed their logo or business) look for examples that match: - Bold & colorful vs. minimal & clean - Modern vs. classic/traditional - Focus on images vs focus on structure If showing 2 similar examples as the first 2 sites, I'd prepare a contrasting 3rd example to get a reaction (e.g., one modern/minimal, one bold/bright). 4. Include a “Best in Class” Example Pick one website that demonstrates top-level design quality for inspiration — even if it’s slightly outside their category. This helps set expectations for what’s possible with UENI’s design. 5. Keep It Quick & Impactful Show no more than 3 examples - enough to compare but not overwhelm. Also keeps the time within expectations. Each example should be easy to navigate during screen share and ensure it has already loaded before showing it. Also, when showing examples, always say: “These are just examples to spark ideas. Your site will be completely personalised to your brand and business.”" "38 minte call. Juan this time and in my opinion a bad match-up as this customer clearly had strong ideas in mind vs Juan who does not impose the possibilities of the website with the customer, nor is he someone who can bounce off/sell great ideas or designs to the customer. It was more of a Juan facilitates the customer meeting rather than an actual Website Expert Assistance call where he could also present improvements to the site based on the expert knowledge. Based on the final outcome at the end of the call, the customer likely had very different expectations to what the outcome would be like vs what was actually going to be achieved/notated by Juan. Again, example page should be used to showcase visuals and get buy-in from the customer. Based on how the call was going, this would definitely require a follow-up admin task from the agent to get the notes into the format we like best, e.g.:

ChatGPT said:
Here’s a condensed summary of all the cases and lessons learned from your notes, grouped into Positive Examples and Improvement Opportunities, followed by Key Takeaways.Positive ExamplesAriana – 47-min Call
Situation: Customer was frustrated about missing custom-coded information.
Actions:
Reviewed the customer’s submitted info in detail.
Compared side-by-side with the live page during the call.
Set realistic expectations and offered solutions.
Stayed calm and professional despite the customer’s frustration.
Result: Perfectly handled — no improvements suggested.Ariana – 60-min Call
Situation: Customer pointed out incorrect information.
Actions:
Showed example pages as soon as they were mentioned.
Checked raw intake data to identify issues.
Verified all info with the customer on the spot.
Took ownership of the meeting and structured it effectively.
Result: Clear, collaborative, and productive call.Improvement OpportunitiesErik Lewis – 35-min Call
Issues:
Edits not submitted after first meeting.
Missed opportunity to upsell Growth plan premium features.
Misplaced “Bits” request instead of creating a dedicated page.
Missed detail (years in business).
Better Approach: Submit edits promptly, showcase premium features, create proper page structures, and ensure all requests are captured.Gabriely – 35-min Call
Issues:
Customer led the conversation; agent didn’t verify info in CMS.
No structured plan for edits.
Didn’t explore interactive website features despite customer interest.
Request lacked context for edits team.
Misinformation not corrected (SmartIntake wasn’t lost).
Better Approach: Take control, clarify content needs per section, fact-check during the call, and explore advanced options.Amy – 17-min Call
Issues:
Call started poorly due to wrong business name and missed link.
Customer frustrated; vague instructions given.
Agent avoided asking clarifying questions.
Better Approach: Use opportunity to dig deeper, review raw form with customer, and clarify expectations early.Astrid – ~20-min Call
Issues:
Customer disliked entire site; key preference (“not basic”) wasn’t flagged.
Lack of probing questions, examples, or tone flagging.
Logo request missed in submission.
Better Approach: Show visual examples, ask precise questions, gather visuals, and note meeting tone.Marsha – 25-min Call
Strengths: Good product/edit knowledge, reined in unrealistic requests politely.
Gaps: Did not show example sites to clarify vision.
Better Approach: Use visual inspiration early to define style.Marsha – ~34-min Call
Strengths: Led call, made good suggestions.
Gaps: Missed example page opportunity; overlooked dynamic stats section idea.
Better Approach: Follow example site checklist to spark more ideas.Juan – ~38-min Call
Issues:
Customer had strong ideas; agent did not proactively guide or sell design possibilities.
More of a facilitation than an expert-led call.
Better Approach: Present strong suggestions, use visuals to align expectations, and prepare well-formatted notes post-call.Key Takeaways
Take Control of the Meeting
Agents should lead, structure discussions, and not let customers completely dictate the flow.
Always Show Visual Examples
Helps clarify vision, inspire ideas, and set realistic expectations.
Verify & Fact-Check in Real Time
Check CMS/raw intake data during calls to confirm what’s been received and implemented.
Capture All Details
No request should be missed; ensure edit submissions are complete and timely.
Flag Context for the Edits Team
Tone of meeting, customer preferences, and special requests should be clearly noted.
Leverage Premium Features
Especially with Growth plan customers — use opportunities to upsell advanced features.
Guide with Examples & Questions
Use structured questions and example site checklists to define style, structure, and functionality.
Manage Expectations Proactively
Be upfront about possibilities, timelines, and next steps.If you’d like, I can also turn this into a one-page “Best Practices & Pitfalls” quick guide your team could use before calls. That would make these points much more actionable.

You said:
Focus on these 2 and give me the main pointers, suggestions and your own recommendations: "25 minute call. Marsha clearly has good product and edits knowledge, but the level of detail could have been deeper in order for it to be a more fruitful call. Overall, the customer lead the meeting and was spitting out requests left and right, and Marsha would rein them in with what was realistically possible without making them upset - she's very good at this. The other improvement which she could have done was to show them some example sites in order to get a better feel for what they want. Script I'm thinking of so far would be along the lines of: ""Before we go any further your own website in detail, I’d love to quickly show you a few great sites we’ve built for other businesses similar to yours. This really helps because sometimes it’s easier to react to real visuals rather than imagining what something might look like. You’ll be able to see different layouts, styles, and features in action — and we can pinpoint exactly what you like (and don’t like) for your own site. Here’s the first one. Notice how we’ve handled [CTA / header image / about section] here. This second example is a bit different... it uses [full-width banners / bold colors / a more minimal design] for a cleaner look. And finally, here’s one with [dynamic moving section / styled images / product designs ] which can work really well for your type of business. When you look at these, which one feels closest to the style or structure you’d like for your own site? Is there anything in these designs that really stands out to you. Either because you love it or because it’s not quite your style? (Pause and encourage open feedback. Capture specifics like colors, fonts, layouts, image style, placement.) Great — now that I have a clear idea of your visual preferences, we can look at your own site with those in mind and make sure we’re moving toward exactly the look and feel you want."" " "34ish minute call. Marsha again, this time took a lead in the meeting as it was a customer that was more laid back and quiet, and had been with us a long time without the latest updates to her site. So this call was very much ""by the script"". Marsha did have great suggestions for the website and category specifically, again showcasing her great product and edits knowledge. However, it would definitely have benefitted from an example page showcase again, in order to guide the redesign that she was suggesting. Marsha also missed a few things that I would have suggested, such as a dynamic stats section, BUT if she had showed the plumbing example page that we have, she would have seen it and been able to ask the customer if they want something like that! Based on this so far, I'd suggest that for finding the right example site to show, they follow these steps: Onboarding Call – Example Website Selection Checklist 1. Match by Business Category Start here: Choose examples from the same or closely related category (e.g., plumber > can show plumber, electrician, etc. café > can show bakery, deli, etc.) If exact matches aren’t available, other ways to select are: - Service delivery style (e.g., in-person booking vs. e-commerce) - Target audience (e.g., local customers vs. nationwide buyers) - Website goals (e.g., lead generation, bookings, online store) 2. Match by Requested Features or Sections Review any pre-call notes or edit requests (or anything customer says during the initial part of the call) to identify: - Specific page requests (e.g., “About”, “Services”, “Blog”) - Design elements (e.g., image gallery, header image, logo, booking form) - Functional features (e.g., external links, CTA, widgets, 3rd party code) 3. Match by Design Style Preference If the client has mentioned preferences before (or e.g. they completely changed their logo or business) look for examples that match: - Bold & colorful vs. minimal & clean - Modern vs. classic/traditional - Focus on images vs focus on structure If showing 2 similar examples as the first 2 sites, I'd prepare a contrasting 3rd example to get a reaction (e.g., one modern/minimal, one bold/bright). 4. Include a “Best in Class” Example Pick one website that demonstrates top-level design quality for inspiration — even if it’s slightly outside their category. This helps set expectations for what’s possible with UENI’s design. 5. Keep It Quick & Impactful Show no more than 3 examples - enough to compare but not overwhelm. Also keeps the time within expectations. Each example should be easy to navigate during screen share and ensure it has already loaded before showing it. Also, when showing examples, always say: “These are just examples to spark ideas. Your site will be completely personalised to your brand and business.”"

ChatGPT said:
Here’s a focused breakdown of those two Marsha calls with main pointers, suggestions, and my own recommendations.Main Pointers from the Two CallsStrengths
Solid product and edits knowledge — able to filter out unrealistic requests without upsetting the customer.
Comfortable leading a structured conversation when the client is quieter.
Offers relevant website suggestions for the business category.Gaps in Both Calls
No example websites shown — missed opportunity to visually align on design/style.
Some potential features (e.g., dynamic stats section) not mentioned because they weren’t visually prompted.
First call: Customer drove the meeting instead of Marsha steering toward a structured, prioritized plan.
Second call: Followed the script well but didn’t push creativity or new ideas beyond the usual.Suggestions from Notes
Incorporate Visual Inspiration
Use example sites early in the call to define look, feel, and structure.
Follow the “Example Website Selection Checklist”:
Match category or related industries.
Include requested features and functional elements.
Show contrasting design styles for reaction.
End with a “best in class” aspirational example.
Use a Guiding Script
The provided script works well for leading into example sites and prompting specific feedback.
Keep it interactive: Pause often and capture details on style, layout, and tone.
Spot and Suggest Extra Features
Proactively introduce features they might not have thought of (dynamic stats, animations, custom sections, widgets).
Use the example sites as a trigger to identify and pitch these.My Recommendations
Start Every Call With a Quick Inspiration Phase
Before reviewing their current site, show 2–3 curated example sites tailored to their business, goals, and style preferences.
This gets them excited, sets a visual benchmark, and makes later decisions easier.
Anchor the Conversation Around Prioritized Goals
When customers throw many requests at once (as in the first call), group them into:
Must-haves (non-negotiable essentials)
Nice-to-haves (features to include if feasible)
Future ideas (possible later updates)
This keeps scope realistic while still making them feel heard.
Keep a “Feature Idea Bank” Ready
Have a personal list of high-impact elements for common industries (e.g., dynamic stats for trades, testimonial sliders for service providers, product galleries for retailers).
Even if not mentioned, suggest them when relevant.
End With Alignment Confirmation
Recap the agreed visual direction, top features, and any inspirations they liked.
Explicitly confirm: “So if we deliver X style with Y features, that will meet your vision?”If you want, I can condense this into a “Marsha Playbook” — a short repeatable checklist/script for her to follow so she nails both the creative pitch and the project structure every time. That would make it easy to apply across all her calls without missing steps.