Canonical: https://www.strataigize.com/lp/opportunities/customer-support-pilot/a/ Description: Plan customer support from approved sources, with human review and handoff. Paid audit; pilot builds are separately scoped and priced. For teams answering repeat customer questions # Answer repeat customer questions from your help documents. We automate routine reply drafts and send complex requests to your team with the conversation attached. **Teegan Johnson**, Founder & Chief Growth Officer.30-minute call. No charge. [Book a 30-minute call](https://www.strataigize.com/lp/opportunities/customer-support-pilot/a/#book) [Working example · Sample request Customer question**Does my old plan include exports?** Source check The article does not cover older plans. Keep the gap with the request.Try the sample support replies ](https://www.strataigize.com/lp/opportunities/customer-support-pilot/a/#support-boundary-demo) [What is included](https://www.strataigize.com/lp/opportunities/customer-support-pilot/a/#scope)[Ask a question first](https://www.strataigize.com/lp/opportunities/customer-support-pilot/a/#ask) Working with teams in Canada and the US Working example · Sample requests and policies. ## A useful answer includes knowing when to stop. Choose a request. Inspect the supported answer or the exception that reaches your team. Try a different support boundary A documented answerAn action outside scopeNo supporting answer Sample customer request > Where can I download last month's invoice? Supported reply > Open Settings, choose Billing, then Invoice history. Select the month and download the invoice. Sample help article: Download an invoice In Settings > Billing > Invoice history, select a month and choose Download. The decision ### Reply using the help article The approved article answers the request. In supervised use, the system can reply within the agreed limits. #### What lets this reply proceed? This request is allowed. The approved help document answers it without an account change. No account action is required to explain these steps. **Routine replies within your limits. A person handles exceptions.**No message, refund or account change happens in this example. Sample customer request > I paid twice. Refund the second payment today. Suggested handoff reply > I've noted your request about a possible duplicate payment. Our support team needs to check the charges before deciding what to do. Sample policy: Billing actions Refunds and payment changes require review and authorization by the support team. The decision ### Pass the request to a person The request asks for a financial action. The example agent has no authority to issue a refund. #### What travels with the request Conversation The complete request and suggested reply shown here. Reason for handoff A person must verify the charges. No refund amount, eligibility or timing has been promised. Next owner The support teammate assigned to this request type. **Routine replies within your limits. A person handles exceptions.**No message, refund or account change happens in this example. Sample customer request > Will our old plan include the new export feature? Suggested handoff reply > The available help articles do not confirm export access for your plan. Our support team needs to check before giving you an answer. Sample help article: Export access Export access is listed for the current Team plan. This article does not describe older plans. The decision ### This question needs your team The sources describe the current plan, but do not establish the customer's older entitlement. A confident guess would be misleading. #### What travels with the request Conversation The complete request and suggested reply shown here. Reason for handoff The older plan's entitlement is unknown. The reviewer needs the agreed account record or policy. Next owner The support teammate assigned to this request type. **Routine replies within your limits. A person handles exceptions.**No message, refund or account change happens in this example. This example shows use after the pilot's reviewed-draft stage and agreed tests. ## Customer support pilot - One support process for the request types, sources and help desk named in scope. - Replies linked to the source article, policy or account record, with missing answers sent to a person. - Draft replies your team checks and sends before supervised use begins. - A clear handoff with the full conversation, useful account details and a suggested reply. - Tests against real tickets, a comparison with the current process and a written handover. Pricing ## A paid audit. A separately scoped build. Audit The two-week audit is a paid assessment with a fixed fee. It reviews your ticket history, sources and handoffs to define the first build. Pilot build A separately scoped, fixed-fee pilot runs over 30 to 90 days. We agree the request types, systems, success measure and stopping rule before the build. Ongoing support Ongoing support is separate, with an agreed monthly fee and an initial three months, then month to month. Model costs per conversation are metered and reported separately. ### Requests your team handles repeatedly - Your team answers the same customer questions in a shared inbox or help desk. - You can name the first request types and the sources that explain the answers. - Someone on your team can check draft replies and take over requests that need a person. ### Actions your support team keeps - Extra request types, source connections, help desks or ongoing support beyond the agreed scope. - Refunds, cancellations and account changes beyond written limits. These stay with a person. Customer reply checklist Illustrative walkthrough ## From a repeat question to an answer or handoff A paid, fixed-fee audit. A separately scoped, fixed-fee pilot build. 1. Read the customer request Start with a request type agreed for the first support process. 2. Find the approved answer Use the named article, policy or account record. Keep the source with the answer. 3. Reply within the agreed scope Start with drafts your team checks and sends. Move to supervised replies after the agreed tests. 4. Pass exceptions to a person Attach the thread and useful account context. Leave refunds, cancellations and decisions outside the limits to your team. Illustrative support flow. The request types, sources, actions and handoff owner are agreed in scope. ## Preparing the support pilot 1. ### Choose the first requests Read the ticket history. Name the questions with written answers and the cases a person must always handle. 2. ### Review drafts with your team Test answers against your sources. Your team sends the replies and reviews edits before the system speaks to customers. 3. ### Hand off cases that need a person Use only the replies and actions agreed in scope. Track resolved requests, handoffs, first-answer time and customer ratings against the starting point. Relevant work ## See how a support pilot works Our published process starts with real ticket types and the sources behind their answers. Your team reviews drafts before the system starts supervised replies. [See the support pilot process](https://www.strataigize.com/services/ai-systems/customer-support-agents/) Use the steps to agree which requests to handle first and who takes over exceptions. ## Show us which customer questions keep coming back. Use a 30-minute call to describe the requests, your help desk and how the team answers today. Discuss the paid audit and what a first pilot would cover. You do not need to share customer tickets or account access to book. ![Teegan Johnson](https://www.strataigize.com/team/opt/team-teegan-head-384.webp) **Teegan Johnson**Founder & Chief Growth Officer Call agenda and calendar details - The repeat questions and the requests that need a person. - The help desk, answer sources and person who reviews replies. - What the audit would cover and how a pilot would be judged. 30 minutes with the Strataigize team, online. Times show in your timezone. Your calendar invitation confirms the organizer and time, and includes the meeting link. [Ask a question first](https://www.strataigize.com/lp/opportunities/customer-support-pilot/a/#ask) Prefer email? [teegan@strataigize.com](mailto:teegan@strataigize.com) ### Book a 30-minute call Choose a time on our booking page. It opens in a new tab and shows the times in your timezone. [See available times](https://meetings.hubspot.com/strataigize/consultation?utm_source=chatgpt&utm_medium=paid&utm_campaign=chatgpt_opportunity_customer_support_pilot&utm_content=ai05-a-v1) Ask about customer replies Teegan Johnson, Founder & Chief Growth Officer, will follow up by email. Fields marked optional can be left blank. ## Support questions Will it reply before our team reviews it? The pilot begins with drafts that your team reviews and sends. Supervised replies start after the agreed tests and review. Requests outside the written scope go to a person. What happens when the source has no answer? The pilot is built to hand the request to a person with the conversation attached when the approved sources do not support an answer. Can it work in our existing help desk? The published service supports Zendesk, Intercom and HubSpot Service Hub through their APIs. The audit checks your tools, access and needed connections before the pilot is priced. Does the audit include the working support agent? No. The paid audit defines the first support process and build scope. The pilot has its own scope and fee. Ongoing support and metered conversation costs are also separate.