What will an edit cost?

A pivotal new chapter in customer support In today's rapidly evolving digital landscape, delivering seamless customer experiences is more important than ever. We are thrilled to unveil a groundbreaking initiative that will empower our customers to unlock the full potential of self-service. This isn't just a portal. It's a paradigm shift. At its core, this transformative journey is about fostering meaningful connections, streamlining workflows, and elevating every interaction. Together, we are reimagining what's possible, one click at a time. Let's dive in. On October 12, we will invite 24 existing customers to try a new support portal for two weeks. The pilot lets them download invoices and check the status of support requests. It does not support refunds, password changes, or adding teammates. Those tasks will stay on the current account page. Participation is optional, and customers can leave the pilot at any time. The wider release has no confirmed date. These details aren't just logistics. They're the foundation of a truly customer-centric ecosystem designed to meet people where they are. Why this matters: in a world where expectations never stop rising, clarity is the cornerstone of trust. The portal could reduce routine questions, but we do not yet know whether it will save customers time. We will measure task completion, time spent finding an invoice, and requests for help. A lower ticket count alone will not count as success. People may stop asking because they cannot find the contact button. That would be a problem, not evidence of improvement. It's worth noting that the goal is not to eliminate human support. It's to cultivate a frictionless experience that puts people at the heart of everything we do. Furthermore, our dedicated team is working tirelessly to ensure a robust and holistic approach to feedback. Support will read pilot comments each weekday. Engineering will investigate blocked invoice downloads before cosmetic problems. If a customer sees another customer's invoice, we will pause the pilot immediately and investigate. We will also pause if customers cannot reach support. These safeguards reflect our unwavering commitment to excellence, underscoring the critical importance of building a resilient foundation for sustainable growth. The future of support isn't on the horizon. It's already here. To navigate this exciting new chapter, account managers should send the invitation only to customers on the approved list. Please use the sentence "You can keep using the current support page" exactly as written. Do not promise faster responses or additional features. Send questions about eligibility to the support lead by Friday. We will share the pilot findings after the two-week trial, including problems and inconclusive results. No price changes are planned during the pilot. This is more than an experiment. It's a testament to the power of collaboration, a catalyst for innovation, and a bold step toward a brighter tomorrow. The journey ahead is filled with opportunity, and we cannot wait to embark on it together.

Hi everyone, As we head into the final month of the quarter, I wanted to take a moment to reflect on the progress we have made together. The customer portal project has brought several moving pieces into one place, and the next few weeks will be pivotal in turning that work into a reliable experience for customers. This isn't just a software launch. It's an opportunity to rethink how we support people after they sign up. The first version of the portal will let customers update their contact details, download invoices, and check the status of support requests. We are keeping the initial release focused. Password changes, team permissions, and subscription changes will continue through the existing account page until the second release. Please avoid promising those features during customer conversations, even if a customer has seen an early design that includes them. Testing starts on Monday with twelve customers who volunteered during the spring interviews. Each participant will receive a short set of tasks and a link to a feedback form. We will also offer two optional video sessions for people who prefer to talk through their experience. The research team will summarize the results each afternoon so engineering can distinguish problems that block a task from smaller issues we can address later. Why this matters: a seamless experience can reduce unnecessary support tickets and empower customers to find answers on their own. However, we should not assume that fewer tickets automatically means people are happier. We will look at task completion, abandoned sessions, and the comments customers leave alongside the ticket count. If customers stop asking because they cannot find the contact button, that is a failure, not an improvement. There are three decisions we need to make this week. First, finance needs to confirm which invoice fields can be edited after an invoice has been issued. Second, support needs to choose an owner for messages submitted outside normal business hours. Finally, product needs to approve the wording for requests that are waiting on a customer response. Please add your answers to the project document by Thursday afternoon, with a link to any relevant policy. For launch week, we will keep the old help page available and add a clear route back to it from the portal. Nobody should have to learn a new system to resolve an urgent billing problem. The support team will have a shared list of known issues, and engineering will nominate one person each day to handle reports that need immediate attention. We will postpone the wider release if the pilot reveals problems with invoices or account access. Thank you for the care you have put into the details so far. Small things like a clear error message or a sensible default can make a meaningful difference. Together, we can build a more intuitive and customer-centric experience while keeping the launch manageable. I will send the pilot schedule on Friday once we have the final participant list. Best, The portal team

A clearer home for your project notes We are excited to introduce a new chapter in the way your team captures ideas, shares context, and moves work forward. Our redesigned project notebook brings notes, decisions, and reference material into a single workspace. It's not just a place to store information. It's a foundation for more connected collaboration, designed to help you turn scattered conversations into shared understanding. The biggest change is the project overview. Instead of opening a long list of documents, you will see a short introduction, the most recent decisions, and the pages your team has marked as useful. You can change the order of those sections or hide one entirely. Existing projects will keep their current documents, permissions, and links. We will not move or rename your files as part of the update. Search now includes the text inside meeting notes and the descriptions attached to uploaded files. Results show a short excerpt so you can check whether a page is relevant before opening it. You can narrow a search to one project, one author, or a date range. The search box will remember those filters while you browse, but you can clear them with a single click whenever you want to look across the whole workspace. We have also added a simple way to mark a decision. Select a paragraph, choose the decision option, and add the name of the person responsible for following up. The original paragraph stays where it was written, while a link appears in the project overview. This helps preserve the surrounding discussion instead of turning every decision into a separate document that nobody remembers to update. Why this matters: knowledge should be an asset that empowers your team, not a maze that slows it down. When someone joins a project halfway through, they need more than the latest task list. They need to understand what the team considered, what it ruled out, and which questions are still open. Keeping that history connected to the work can make those first conversations more productive. The rollout begins with a small group of workspaces next week. Workspace owners will receive a notice before the new overview appears, and they can choose to wait until the following month if the timing is inconvenient. During the first two weeks, a switch in settings will let you return to the previous layout. Please tell us if you cannot find something you use regularly so we can understand what needs attention. Your existing plan includes these changes. There is no additional charge for the overview, improved search, or decision links. Storage limits and guest permissions remain the same. Administrators can read the setup guide for details about shared projects, archived pages, and the settings that control who can edit the overview. We believe great tools should get out of the way while helping people do their best work. This release is a meaningful step in that direction. Open a project, try a search, and let us know which part saves you time and which part still needs work.

Proposal: understanding the first month of customer use This proposal outlines a focused research project to understand why some new customers stop using the service during their first month. The aim is to identify the moments where expectations and experience diverge, then recommend a small set of improvements that the team can test. By taking a holistic approach to the customer journey, we can uncover actionable insights and create a more seamless onboarding experience. The project will focus on customers who created an account in the last eight weeks. We want to hear from people who became regular users, people who tried the service once, and people who started setting it up but did not finish. Comparing those experiences should help us avoid treating every inactive account as evidence of the same problem. Some customers may have completed a short task and simply have no reason to return yet. We propose twelve interviews, each lasting about forty minutes. Participants will be asked to describe what they hoped to accomplish, show how they approached their first task, and explain any points where they became uncertain. We will ask for specific examples rather than general ratings. A statement such as the interface was confusing is a starting point; the useful detail is what the person expected a particular button to do. Recruitment will happen through an invitation sent to eligible customers who have agreed to receive research messages. Participation will be optional, and declining will not affect their account or support. We will offer the same thank-you payment to every participant, regardless of whether their feedback is positive or negative. The invitation will explain how the interview notes will be used and whether the participant wants to allow recording. This isn't just about collecting feedback. It's about building a deeper understanding of the people behind the metrics. Alongside the interviews, we will review existing support questions and the steps customers complete during setup. These records can help us decide where to ask better questions, but they will not replace the conversations. A drop in activity tells us where something happened, not necessarily why it happened. The work will take four weeks. The first week covers recruitment and preparation. Interviews will run during the second and third weeks, with time between sessions to compare notes and adjust unclear questions. During the final week, we will present the findings and work with product and support to choose the next experiments. We will share observations during the project if a problem needs attention before the final report. The main deliverable will be a short report containing the recurring problems, the evidence behind them, and the limits of what we learned. Recommendations will name a specific change and explain how the team could tell whether it helped. We will also include cases that contradict the main pattern, since those differences may matter when deciding which customers an improvement will serve. Success means leaving the project with a few testable decisions rather than a long collection of interesting quotes. With the right insights, we can foster stronger customer relationships and set the stage for sustainable growth.