A Quick Hello — getting everyone on the same page

• To start, who are you and what role do you play in decisions about digital self-service and contact center transformation? Options: VP/Head of Digital CX, Director of Self-Service, Head of Customer Operations, Contact Center Director, Other
• What prompted you to explore a new self-service approach today—was it a specific event, a board mandate, or ongoing operational pressure? Options: Board mandate for cost reduction, Recent billing migration spike, CSAT/Survey results, Budget review, Exploratory improvement project, Other
• How urgent is this initiative on a scale from ‘nice to have’ to ‘mission critical’? Options: Mission critical (30–90 days), High priority (3–6 months), Medium priority (6–12 months), Low priority (12+ months)
• Who else on your team needs to be involved in discovery and pilot decisions (roles, not names)? Options: Head of Ops/COO, Billing/Product Owners, Engineering/Integration Lead, Security/Compliance, Customer Insights/Analytics, Customer Support Ops, Other
• Briefly, what would success from our first conversation look like for you?

Are we quietly accepting avoidable costs?

• When you hear 'reduce contact center costs by 25%', what stops you from thinking that's unrealistic—or what makes it feel doable? Options: Not confident in automation, Legacy systems block progress, Data access issues, Change management concerns, Feels achievable with right integrations, Other
• How did your last billing migration change contact volumes and channel mix—numbers, if available (e.g., % increase in calls, chats, or complaints)?
• Which of these outcomes feels most urgent to your board or leadership right now? Options: Cut cost per contact, Improve CES/CSAT, Stabilize live agent headcount, Reduce escalations and refunds, Avoid regulatory issues, Other
• What emotions are you and your team experiencing about current call volumes—overwhelmed, resigned, defensive, energized to fix it? Options: Overwhelmed, Frustrated, Resigned, Motivated, Anxious, Hopeful
• Tell me about one recent situation where costs spiked and you wish you had a different outcome—what happened and what was the impact?

Where do customers hit a wall and bail out of self-service?

• Is it possible most of your callers try self-service first but abandon it because the system can't complete transactions—how confident are you in that statement? Options: Very confident, Somewhat confident, Unsure, Unlikely
• Which contact drivers make up the top of your inbound volume today (select up to three)? Options: Billing/Charges, Payment failures, Account changes (plan/mods), SIM/Security issues, Service outages, Technical troubleshooting, Install/activation
• Pick the single highest-volume contact driver right now and describe the typical caller journey and where it breaks down.
• On average, where do customers abandon digital self-service—FAQ page, IVR, chatbot handoff, authentication step, or at transaction execution? Options: FAQ/KB, IVR, Chatbot handoff to agent, Authentication/identity step, During backend transaction, Other
• Do you have examples or transcripts of failed self-service attempts we could review during discovery? Options: Yes – full transcripts available, Yes – sampling available, No, but logs exist, No, not available

What would 25% fewer live calls actually unlock for you?

• If you reduced live-agent volume by 25–50%, what tangible outcomes would that enable—cost savings, reallocation of staff, improved SLAs, or something else? Options: Headcount reduction, Re-skill agents to higher-value work, Better SLAs/shorter wait times, Lower operational spend, Improved NPS/CSAT, Other
• Which metric is most critical for the business case you need to make (containment rate, CES, live-agent volume, or revenue impact)? Options: Containment rate, Customer Effort Score (CES), Live-agent volume, Cost per contact, CSAT/NPS, Other
• What minimum containment lift would you need to justify a pilot—e.g., 10%, 20%, 30%? Options: 10%, 15%, 20%, 25%, 30%+, Unsure
• Who makes the final go/no-go call for pilots that touch billing or provisioning—finance, CTO, head of ops, or compliance? Options: Finance, CTO/Engineering, Head of Ops, Security/Compliance, Product/Billing Owner, Other
• What would have to happen in the first 30 days of a pilot to convince leadership this is worth scaling?

What worries you most when automation touches sensitive account actions?

• Would a single mistaken transaction by a virtual assistant be more damaging to trust than a handful of unresolved calls—how do you weigh brand risk versus containment? Options: Brand risk outweighs containment, Containment worth some brand risk, Depends on mitigation controls, Unsure
• Which transaction types do you consider high-risk and require extra controls (e.g., refunds, billing credits, plan changes, SIM swaps)? Options: Billing credits/refunds, Plan/upgrades/downgrades, SIM swaps/porting, Sensitive PII edits, Account deletions, Other
• What existing controls and audit trails do you have for backend transactions (detailed logs, approval gates, rollback capabilities)? Options: Detailed logs & audit, Manual approval gates, Partial logs, No strong audit trail
• How do you want to handle rollback or remediation if a self-service transaction goes wrong? Options: Automated rollback, Agent-assisted remediation, Financial reversal only, Case-by-case manual fix, Other
• What compliance or regulatory checks must any digital assistant meet before touching customer accounts? Options: KYC/identity verification, PCI/Payment controls, Data residency constraints, Audit & logging standards, None/Not sure

If we designed a small pilot that wins quickly, what should it prove?

• Which top three contact drivers would you like to include in a focused pilot? Options: Billing inquiries, Payment failures, Plan/account changes, SIM/security issues, Service outages, Technical troubleshooting
• How do you currently rank intents for pilot selection—by volume, cost-to-handle, customer friction, or ease of automation? Options: Volume, Cost-to-handle, Customer effort, Ease of automation/integration, Regulatory sensitivity, Other
• What acceptance criteria would make the pilot a clear pass/fail (specific numbers for containment lift, CES change, reduction in agent transfers)?
• What internal teams will need to support pilot integrations—API owners, billing/product, security, analytics—and who will be the day-to-day owner? Options: API/Platform Engineering, Billing/Product, Security/Compliance, Analytics/BI, Contact Center Ops, Other
• What level of data access and test accounts can you provision for a pilot (read-only logs, test billing accounts, sandbox APIs)? Options: Full sandbox with test accounts, Partial access / anonymized data, Read-only logs only, No access today

Do you trust your metrics—and if not, where do they break?

• How do you currently measure containment—by intent-level handoffs, session outcomes, or agent deflection—and which do you trust most? Options: Intent-level handoff tracking, Session outcome logging, Agent deflection counts, Estimations from sampling, Unsure
• How do you capture Customer Effort Score (CES) today—post-interaction survey, real-time rating, or inferred signals? Options: Post-interaction survey, Inline quick-rating, Inferred from behavior, No CES capture
• What systems will we need to integrate to validate containment and CES (CRM, WFM, billing, analytics, survey tool)? Options: CRM, Billing/Provisioning, WFM/Telephony, Analytics/BI, Survey platform, Other
• Are you open to a short, structured audit of your existing metrics so we can baseline containment and CES before the pilot? Options: Yes — schedule audit, Maybe — need approval, Not at this time
• Who will be responsible on your side for validating transactional integrity and accepting pilot results?

Who signs, who builds, and how fast can we move?

• Which timeline feels realistic to get a 60–90 day pilot running from contract to cutover? Options: <4 weeks, 4–8 weeks, 8–12 weeks, 12+ weeks
• What commercial or legal constraints typically slow your pilots (procurement cycles, procurement thresholds, vendor security reviews)? Options: Procurement cycle, Security review, Budget approvals, Data residency, Other
• What SLAs or integration commitments would you need from us for moving to pilot (availability, response times, rollback windows)?
• Who are the final approvers we should engage now to avoid late surprises (names or roles)?
• If we walked out of discovery with a one-page plan and a recommended pilot scope, are you able to champion it internally? Options: Yes — I'll champion, I need a co-sponsor, No — not my decision
• What would be a helpful next step from us after this discovery call (detailed proposal, pilot plan, technical kickoff, executive briefing)? Options: Detailed pilot proposal, Technical integration plan, Executive briefing, ROI/cost model, Other

• Experience Prep & Current-State Confirmation
• Consequence Mapping & Pilot Prioritization Workshop
• Live Solution Experience — Transactional Walkthroughs
• Transactional Integrity, Edge Cases & Risk Controls
• Validation & Acceptance Decision

• Define monitoring and escalation playbook owners and SLAs for pilot operations.
• Have numeric consequence metrics for each selected driver to measure ROI and urgency.
• Agree acceptance criteria (containment %, CES, live-agent reduction) per pilot driver.
• Establish risk guardrails that constrain what the solution may execute during pilot.
• Customer to provide AHT, contact volumes, escalation rates, and cost-per-contact for selected intents.
• Customer and vendor to finalize the list of top 3 pilot intents and document acceptance thresholds.
• Create an intent-to-transaction matrix mapping each pilot intent to the backend APIs/workflows required.
• Briefing: Rules of Engagement
• Prove end-to-end transactional capability for each pilot scenario in the customer's context.
• Demonstrate how containment and CES will be measured and capture preliminary measurements.
• Obtain explicit, scenario-by-scenario validation from the customer (forced confirmation).
• Capture issues requiring remediation and assign owners and timelines.
• Vendor to provide transaction execution logs and containment measurement snapshots for each scenario.
• Customer SME to review and sign off on each scenario's policy and authorization checks or list required changes.
• Create tickets for each discrepancy with owner and SLA for fixes prior to pilot launch.
• Architecture & Control Overview
• Verify transaction failure modes are understood and acceptable rollback/compensation works reliably.
• Agree security, privacy, and audit controls required for pilot and confirm compliance sign-offs.
• Introductions & Meeting Objectives
• Obtain explicit risk acceptance for the defined transactional scope of the pilot.
• Vendor to deliver test cases demonstrating rollback and idempotency; run validated failure tests in sandbox.
• Customer security/compliance team to provide checklist approval or required changes for PII handling.
• Document and publish monitoring dashboards and escalation contacts for pilot operations.
• Recap Objectives and Acceptance Criteria
• Reach a documented go/no-go decision or conditional approval for the pilot transactional scope.
• Agree remediation actions with owners and timelines for any gaps preventing approval.
• Confirm pilot operational owners, start date window, and schedule the Deployment group readiness meeting.
• If approved, finalize and sign the pilot SOW and schedule Pre-Deployment Readiness meeting.
• If conditional, list remediation items with owners and deadlines required before launch.
• Publish the final Acceptance Decision and distribute to stakeholders and operational teams.
• Produce a single-sentence current-state statement the whole room agrees is true.
• Establish explicit, quantified consequence for the current state to create urgency.
• Define the one-sentence future-state outcome and measurable acceptance criteria for the Experience.
• Confirm data, sandbox access, and named owners for pre-work.
• Customer to share top 10 billing/account-change call transcripts and anonymized sample accounts for scenarios.
• Customer IT to provision sandbox/API credentials and data mappings to the vendor test environment.
• Assign SMEs and schedule the Live Solution Experience date once pre-work is complete.
• Recap Current-State and Future-State
• Produce a ranked list of candidate intents and select the top 3 pilot drivers.
• Current-State Statement (Customer)
• Intent Journey Mapping
• Measured Outcomes from Walkthroughs
• Edge-case Scenario Tests
• One-sentence Reaffirmation of Current & Future State
• Consequence Quantification per Intent
• Evidence Review
• Scenario 1 Walkthrough — Billing Credit/Adjustment
• Rollback, Compensation, and Idempotency Demonstrations
• Gap Analysis and Remediation Plan
• Validation Checkpoint 1
• Consequence Quantification (Snapshot)
• Security, Privacy, and Compliance Controls
• Pilot Candidate Scoring & Selection
• Stakeholder Q&A and Forced Validation
• Decision: Go / Proceed with Conditions / Remediate
• Scenario 2 Walkthrough — Plan Change / Upgrade
• Define Acceptance Metrics per Driver
• Monitoring, Alerting, and Escalation Paths
• Future-State Definition & Acceptance Criteria
• Data & Access Checklist

• Integrate Virtual Assistant with Billing System
• Deploy Billing-Inquiry Conversational Flow
• Implement SIM Swap Transaction Handler
• Create Guided Troubleshooting for Broadband Outages
• Configure Knowledge Base with Top Drivers
• Enable Web and Mobile Chat Channels
• Connect SMS and Messaging Channels
• Implement Authentication and Account Linking
• Deploy Intent Recognition Models
• Install IVR-to-Chat Handoff
• Enable Live-Agent Escalation with Context
• Activate Self-Service Billing Credit Execution
• Integrate CRM for Account Updates
• Deploy Guided Plan Upgrade Workflow

Integrate Virtual Assistant with Billing System

• Which billing/OSS/BSS platform does your organization use? Options: Oracle BRM, Amdocs, SAP Billing, Netcracker, Custom/Proprietary, Other
• What type of integration does your billing system expose? Options: REST API, SOAP API, GraphQL, Message queue/event stream, Batch file only, No APIs / manual only
• Is there a sandbox or test environment we can use for development? Options: Yes, No, Partial/limited
• Which authentication method is required to call billing APIs? Options: OAuth2 (client credentials), API Key, Mutual TLS, Basic Auth, Other
• Which transactional operations should the virtual assistant be allowed to perform? Options: View bill/details, Apply billing credit, Update payment method, Change billing address, Plan change/upgrade, Cancel service, Other
• Expected monthly transaction volume (billing-related) to be handled by VA during the pilot? Options: <1,000, 1,000-10,000, 10,000-100,000, >100,000, Unknown

Deploy Billing-Inquiry Conversational Flow

• Which billing inquiry intents should be included in the pilot? Options: Top 1 intent (e.g., balance query), Top 3 intents, Top 5 intents, Custom list
• Which customer channels should this conversational flow be available on? Options: Web chat widget, Mobile in-app chat, SMS, WhatsApp, IVR-to-chat handoff
• Do you require the flow to display or collect Personally Identifiable Information (PII)? Options: Yes - display, Yes - collect, No
• Should the billing flow include immediate transactional execution (e.g., apply credit) or only guided resolution? Options: Immediate transactional execution, Guided resolution only, Hybrid (some actions exec), Unsure
• What containment target for billing inquiries would make the pilot successful? Options: 20%, 30%, 40%, 50%+, Custom target
• What languages and locales must the billing conversational flow support for the pilot? Options: English, Spanish, French, Other/Multiple

Implement SIM Swap Transaction Handler

• Does your backend support automated SIM swap via API today? Options: Yes - fully automated, Partial / requires orchestration, No - manual process
• What customer verification method is required before performing a SIM swap? Options: One-time passcode (SMS/Email), Security questions, Account PIN, Agent-assisted verification, Other
• Are there regulatory or KYC constraints we must enforce for SIM swaps in the pilot? Options: Yes - specify in next field, No, Unsure
• If rollback or reversal of a SIM swap is needed, what process must be followed? Options: Immediate automated rollback, Requires agent intervention, Accounting/ops approval, Rollback not supported
• Will SIM swap require linking to device identifiers (IMEI/ESN) or carrier provisioning systems? Options: Yes - IMEI required, Yes - carrier provisioning integration, No, Other

Create Guided Troubleshooting for Broadband Outages

• Which customer segments and service types should troubleshooting cover? Options: Residential broadband, Business broadband, FTTx (fiber), DSL/copper, All of the above
• Do you have diagnostics APIs or remote CPE control (reboot, ping, stats) available? Options: Yes - full diagnostics, Partial (limited metrics), No
• Which automated remediation actions should guides attempt before escalating? Options: Remote CPE reboot, Line test, Reset configuration, Provide self-service steps, Schedule tech visit, Other
• Should the troubleshooting flow collect network telemetry or logs as part of the conversation? Options: Yes - telemetry included, No - telemetry excluded, Only on customer consent
• What containment or defect reduction target would indicate the module is successful? Options: Reduce tech tickets by 10%, 20%, 30%+, Other/custom
• Are there peak times or outage surge scenarios we should load-test for the pilot? If yes, describe (open response).

Configure Knowledge Base with Top Drivers

• How many top drivers / KB articles do you want ingested for the pilot? Options: 10, 25, 50, 100, Custom number
• What are the primary sources for knowledge content? Options: Confluence / Wiki, Helpdesk export (CSV), Static HTML/FAQ, Support playbooks, Other
• Do articles require redaction or PII removal before ingestion? Options: Yes, No, Unsure
• Should we apply taxonomy tagging, canonicalization, and synonyms during KB ingestion? Options: Yes - full enrichment, Basic tagging only, No enrichment
• Who will own ongoing KB updates during and after the pilot? Options: Customer content team, Shared (customer + vendor), Vendor-managed
• Which languages must the KB support for retrieval and authoring? Options: English, Spanish, French, Other/Multiple

Enable Web and Mobile Chat Channels

• Which front-end chat channels should we enable in the pilot? Options: Website chat widget, Mobile in-app chat, Progressive Web App (PWA), Customer portal
• Which mobile platforms are targeted? Options: iOS, Android, Other
• Do you require SSO/session transferring between web/mobile and agent desktop? Options: Yes, No, Partial
• What concurrent chat session capacity should we design for the pilot? Options: <100, 100-500, 500-2,000, 2,000+
• Will chat support attachments (screenshots/log files) from customers? Options: Yes, No
• Do you require custom branding, UI flows, or accessibility (WCAG) compliance for chat? Options: Custom branding, WCAG accessibility required, Standard widget acceptable

Connect SMS and Messaging Channels

• Which messaging channels do you want active in the pilot? Options: SMS, WhatsApp Business, RCS, Facebook Messenger, Other
• Do you already have approved business accounts or sender IDs for these channels (e.g., WhatsApp Business API)? Options: Yes - all ready, Partially ready, No - need provisioning help
• Will you route messaging via a CPaaS provider (Twilio, Vonage) or direct carrier integration? Options: Via CPaaS, Direct carrier integration, Use internal gateway
• Are there message templating, localization or character-limit constraints we must follow? Options: Yes, No, Unsure
• Is opt-in/consent management and unsubscribe handling required for pilot compliance? Options: Yes, No
• Estimated monthly message volume per channel for the pilot? Options: Low (<1k), Medium (1k-50k), High (>50k)

Implement Authentication and Account Linking

• Which authentication methods must be supported for customers? Options: Username/password, OAuth2 / SSO, SAML, OTP / SMS, Token-based (API)
• Do you require account linking across channels (web, mobile, SMS, messaging)? Options: Yes - link across all channels, Link only between specific channels, No
• What identifier(s) should be used to match/link accounts? Options: Phone number, Account number, Email address, Customer ID (internal), Other
• Is risk-based or step-up authentication required for sensitive transactions? Options: Yes - step-up required, No, Only for certain transactions
• What session duration and re-authentication policy should apply during the pilot? Options: 15 minutes, 30 minutes, 60 minutes, Custom
• Will you provide identity provider (IdP) documentation and test credentials? Options: Yes, No, Partial

Deploy Intent Recognition Models

• Do you prefer prebuilt intents, custom-trained models on your data, or a hybrid approach? Options: Prebuilt only, Custom-trained on customer data, Hybrid (prebuilt + custom)
• How much labeled training data is available for the targeted intents? Options: >10k labeled examples, 1k-10k, <1k, None
• Which languages and regional dialects must the models support? Options: English, Spanish, French, Other/Multiple
• What confidence threshold should trigger automated containment vs. escalate to agent? Options: High (>=0.85), Medium (0.70-0.85), Low (<0.70), Custom
• How frequently should models be retrained or updated during the pilot? Options: Weekly, Monthly, Quarterly, Ad-hoc as needed
• Do you require dashboards and monitoring for intent performance (precision, recall, confusion matrix)? Options: Yes, No

Install IVR-to-Chat Handoff

• Do you currently operate an IVR and can it trigger a chat handoff? Options: Yes - supports handoff, IVR exists but no handoff capability, No IVR
• What should trigger an IVR-to-chat handoff? Options: Menu selection, Speech intent detected, Estimated wait time exceeded, Caller request, Other
• Is CTI/phone system integration available to pass call context and attributes? Options: Yes - CTI available, Limited CTI, No CTI
• What caller context fields must be passed to chat/agent (e.g., ANI, account ID, queue reason)?
• If chat is unavailable, what fallback should IVR use? Options: Queue for agent callback, Send SMS link to chat, Remain in IVR with estimated wait, Other
• Estimated daily IVR-to-chat handoff volume during pilot? Options: <100/day, 100-1,000/day, 1,000-10,000/day, 10,000+/day

Enable Live-Agent Escalation with Context

• Which agent desktop or CRM will receive escalations? Options: Salesforce Service Cloud, Zendesk, Genesys/CxEngage, Custom/Proprietary, Other

• Statement of Work (SOW)
• Pilot Order Form / Pilot Agreement
• Commercial Terms & Pricing
• Data Processing Agreement (DPA) & Privacy Addendum
• Integration Service Level Agreement (Integration SLA)
• Acceptance Criteria & Go/No-Go Matrix
• Data Access & Test Environment Access Statement
• Security, Risk Controls & Liability Schedule
• Change Control & Escalation Procedure
• Roles & Responsibilities (RACI) Annex
• Payment Schedule & Invoicing
• Termination, Rollback & Exit Plan
• Intellectual Property & Model Usage Agreement

• Executive Results Review & Go/No-Go
• Pilot Analytics Deep-Dive
• Operations Readiness & Risk Mitigation
• Customer Experience & Brand Safety Review
• Scale Strategy & Roadmap Planning Workshop

• Create a prioritized CX remediation backlog with owners and target completion dates.
• Perform reconciliation of containment calculations against raw channel logs and report discrepancies.
• Produce a validated KPI definitions document to be used in scale reporting.
• Schedule follow-up analysis to investigate any high-impact anomalies within 7 business days.
• Operational Impact Review
• Validate operational capabilities and confirm that integration SLAs and rollback plans are production-ready.
• Identify and assign remediation for any operational gaps with clear owners and dates.
• Agree on monitoring and incident escalation procedures to protect brand and customers at scale.
• Update and distribute production runbooks and rollback playbooks to ops and SRE teams.
• Implement agreed monitoring dashboards and alert thresholds in the production environment.
• Complete any required compliance remediations and confirm certification before scale.
• CES Drivers & Customer Feedback Summary
• Agree which CX issues must be fixed before or during scale to avoid brand or legal exposure.
• Prioritize a short list of high-impact CX improvements with owners and timelines.
• Ensure CES insights are embedded into the scale acceptance criteria and success metrics.
• Opening & One-Sentence Current State
• Draft customer-facing messaging for any changes that might affect caller experience during rollout.
• Train support agents on updated escalation handling and publish guidance notes.
• Compare Scale Scenarios
• Produce a validated scale roadmap with clear milestones, gates, and ownership.
• Secure resource and budget commitments required to execute the roadmap.
• Set explicit success criteria and a governance cadence to monitor progress post-scale.
• Create a detailed project plan (Gantt) for Phase 1 scale including dependencies and owners.
• Submit budget request and resource plan to finance with justified ROI assumptions.
• Schedule weekly program governance meetings and monthly executive checkpoints.
• Align executives on whether the pilot met the business case and select a scale strategy (go/modify/stop).
• Ensure the decision is backed by agreed metrics and a clear rationale tied to consequence.
• Assign executive owners and near-term actions to operationalize the decision.
• Publish an executive summary deck with metrics, recommendation, and decision record.
• If 'go', authorize formation of the Scale Program team and appoint a program lead.
• If 'modify', document required metric thresholds and remediation plan before re-evaluation.
• Measurement Definitions & Data Sources
• Confirm that containment, CES, and live-agent metrics are accurate, reproducible, and trusted.
• Identify and prioritize any data or measurement gaps that must be closed before scaling.
• Agree on the exact KPI calculations and reporting cadence for the scale phase.
• Business Consequence Summary
• Integration & SLA Readiness
• Containment by Intent & Channel
• Define Scope & Priorities for Phase 1 Scale
• Sample Interaction Forensics
• Rollback & Risk Controls
• Roadmap, Milestones & Gates
• Top-Line Pilot Metrics
• CES & Customer Journey Impact
• Sensitive Cases & Brand Risk Assessment
• Live-Agent Volume & AHT Effects
• Monitoring, Alerts & Runbooks
• Agent Feedback & Escalation Causes
• Resource, Budget & Commercial Requirements
• Recommendation & Scale Options
• Data Quality, Anomalies & Edge Cases
• Success Criteria & Reporting Cadence
• Compliance, Security & Data Governance
• Executive Q&A and Decision
• Prioritized CX Backlog & Quick Wins
• Validation & Reconciliation Plan
• Immediate Next Steps
• Final Commitments & Next Actions
• Operational Gaps & Remediation Plan