A good AI workshop ends with a short list of use cases your team will actually build, an owner for each, and a date for the first check-in. If people leave with only a demo in their heads, the workshop failed.
This checklist covers four phases: planning, participant prep, running the session, and follow-up. For service businesses, the easiest place to start is the phone, because missed calls cost real revenue. That makes a tool like Answering Agent a practical demo subject.
Pre-Workshop Planning Checklist
Set Clear Workshop Goals
Decide on the deliverable before you book the room. Two useful targets are a shortlist of 3–5 AI use cases, or a 30/60/90-day roadmap with owners and success metrics. Tie each goal to something you can measure, such as call answer rate, staff time on the phone, or after-hours coverage.
Run 10–20 minute interviews or a short survey with stakeholders first. Their answers tell you whether to spend time on basics, on quick wins like lead capture and booking, or on calculating ROI for bigger bets. Leadership that is hesitant about AI needs to see that answer before the workshop starts.
Select and Invite Participants
Match the room to the content. A technical session loses business staff, and an overview session loses engineers. Ask directly, "Who shouldn't attend?"
Invite the people who will run the tools afterward, not just executives who want an overview. That usually means front-desk staff, operations managers, and whoever owns marketing or intake. For multi-location or franchise groups, bring the operators who can make adoption stick across sites. Ask everyone to clear their calendar for the full session.
Create Workshop Format and Schedule
Choose in-person, virtual, or hybrid based on where people are. Spend at least half the time on hands-on work. A half-day agenda:
- 15 minutes: welcome and goals
- 30 minutes: AI fundamentals
- 60 minutes: map current pain points
- 45 minutes: brainstorm use cases
- 30 minutes: prioritize with a 2×2 matrix
- 30 minutes: build the roadmap
Pre-load real context, such as the company description, pricing, and FAQs, so demos reflect the business. Plan at least four phone demos: a basic service inquiry, calendar-integrated booking, an off-script question, and an after-hours call. Standardize on one set of tools so troubleshooting stays simple.
Participant Preparation Checklist
Distribute Pre-Workshop Materials
Send materials one to two weeks ahead. Include:
- Business identity: company bio, service area zip codes, hours.
- Service details: service descriptions, price ranges, diagnostic fees.
- Operational rules: cancellation policy, payment methods, escalation rules.
- Demo support: sample call recordings and dashboard access for the Answering Agent demos.
Add a knowledge base of 20–30 FAQs and a glossary of the synonyms customers use ("breaker box" vs. "electrical panel"). For people new to prompting, give them a starter kit built on the CAREful framework: Context, Ask, Rules, Examples.
Upload every context file to the AI before you send it out to confirm it parses. Plain text works better than complex PDFs.
"Quality matters more than quantity. MIT Technology Review research shows that 30 well-documented FAQs outperform 100 poorly written ones." - NextPhone
Collect Participant Information
Use a pre-workshop survey to tailor demos and group exercises. Collect:
- Roles and responsibilities
- Call volumes and peak times
- Current tools, such as CRMs and calendars
Group people by role and experience. Put training time on the staff who will use the tool every day. Teams that skip that training tend to abandon the tool.
Provide Pre-Workshop Assignments
Ask participants to log phone activity for three to seven days. This gives you a baseline and makes the demos concrete. Track:
- Daily call volume
- Peak call times
- Most frequent questions
- Missed calls
Have them draft a minimum knowledge base: services, pricing, hours, and the top 10–20 FAQs. Ask for a first pass at custom AI call scripts using three steps: Identify (business name), Orient (what the AI can help with), and Engage (an open-ended question). Also ask for test scenarios that cover both routine calls and edge cases.
Last, collect a list of every tool connected to the phones, with logins, so integrations can be tested live.
Venue and Technical Setup Checklist
Set Up Venue and Equipment
For in-person sessions, mount tablets or touchscreens at eye level, roughly 59 inches (150 cm). Put a 40–60 inch display where everyone can see AI output and dashboards. Bring power strips, extension cords, and gaffer tape.
For virtual sessions, have everyone use the same model, whether that's ChatGPT, Gemini, or Claude, and set up a shared whiteboard. Test the network in advance and keep a 4G/5G hotspot as backup.
Collect integration logins before the day. That includes the CRM (HubSpot, Salesforce, Clio), the calendar (Google Workspace, Microsoft 365, Calendly), and field software (ServiceTitan, Housecall Pro).
Test Answering Agent Demo Features
Run a 10-scenario test before the session:
- Simple greeting
- Appointment scheduling
- Pricing question
- Emergency
- After-hours call
- FAQ
- Transfer request
- Wrong number
- Extended silence
- Non-English caller
Routine calls should resolve on their own. Complex ones should escalate to a person.
Confirm three things: bookings create calendar events, leads land in the CRM, and email or SMS notifications arrive within five minutes. Test both blind transfers and warm handoffs. Change business hours temporarily to check that after-hours greetings and routing switch correctly.
Log each scenario in a spreadsheet with the expected result, the actual result, and the fix. Review the first AI follow-up emails by hand before you turn on auto-send.
Prepare Backup Equipment
Bring a spare laptop with the software already installed, plus a hotspot. Keep offline fallbacks ready, such as recordings of successful calls and non-digital exercises.
| Technical Issue | Backup Action |
|---|---|
| Primary internet drops | Switch to a 4G/5G hotspot |
| AI tool unresponsive | Restart the app and check connectivity |
| AI hallucinations or errors | Play pre-recorded demo content |
| Integration failure | Fall back to manual entry or CSV |
If you plan to demo volume, place at least 10 simultaneous calls beforehand. Set a clear escalation rule, such as handing off to a person after two failed attempts or on any complex request.
Workshop Execution Checklist
Start with Introductions and Goals
Have an executive sponsor open with why AI matters to the business and one example of how they use it personally. That framing presents the tools as help for staff, not a replacement.
Take a quick baseline of everyone's comfort with AI. Get everyone logged in to the tools early so tech problems surface right away. Put the agenda and deliverables on screen. Then spend five minutes on a low-stakes warm-up, like having the AI name each team.
Lead Core Workshop Activities
Use diverge–converge–narrow. Split into teams of 2–4 and have each team brainstorm 15–20 use cases tied to their roles. Then use AI to cluster the ideas into themes.
Plot the themes on a 2×2 matrix of impact vs. feasibility, using three tests:
- Feasibility: Can we do this with current resources?
- Desirability: Does it solve a real customer need?
- Viability: Does it save money or earn it?
"AI success is rarely about the model - it's about stakeholder alignment, data readiness, and organizational momentum." - InitializeAI
Use silent brainwriting or round-robin sharing so quieter people contribute. After each activity, have the AI summarize decisions and next steps.
Conduct Hands-On AI Demonstrations
Walk through five live test cases with Answering Agent:
- Basic inquiry (hours, location)
- Appointment booking, with a check that the calendar synced
- Off-script question
- Transfer to a specific person or department
- After-hours call with the correct closed greeting
Show what happens after the call: the CRM entry updates and a follow-up email goes out. Point out the Identify–Orient–Engage greeting and keep it under 15 seconds.
Have participants upload their own service menus and FAQs so the demo reflects their business, not a sample.
"If attendees aren't creating something during the workshop, it's a lecture with a fancy price tag." - Rasmus Widing
Close by showing an escalation to a live person. Then show how to review daily transcripts and update the knowledge base from real calls.
Post-Workshop Follow-Up Checklist
Most workshop ideas die without an owner and a check-in date. Assign both before people leave.
Send Workshop Summary and Resources
Send the summary within 48 hours. Include a 30-day plan: Assessment (Week 1), Configuration (Week 2), Testing (Week 3), Launch (Week 4).
Attach:
- Service menu with descriptions
- Pricing sheet
- Starter FAQ of 20–30 questions, grouped by availability, pricing, process, and qualifications
- A testing spreadsheet and a KPI dashboard template covering answer rate and bookings
- Custom AI phone scripts and call-flow decision trees
- Industry glossary and emergency keywords
For healthcare or legal teams, include guidance on Business Associate Agreements and compliance workflows.
Gather Participant Feedback
Send a survey within 24 hours. Keep it to 5–10 questions and about 3 minutes, with mostly 1–5 ratings and 2–3 open-ended questions. Keep responses anonymous.
Collect feedback in three rounds:
- Within 24 hours: first impressions
- 2–4 weeks: implementation blockers
- 3–6 months: lasting change
Tell participants what you changed because of their feedback.
Schedule Follow-Up Sessions
Hold the first follow-up 2–4 weeks out. Then check in on a 30/60/90 schedule:
- 30 days: foundations and alignment
- 60 days: launch and execution
- 90 days: scale and standardize
"The workshop ends when implementation ownership is clear, not when participants leave the room." - Laura van Valen, Facilitation & Group Dynamics Expert
Pair participants as accountability partners and set up a group channel for questions between check-ins.
If you roll out Answering Agent, block 30–60 minutes a week to review about 10% of call transcripts and update the knowledge base. Weekly review catches gaps faster than monthly review.
Conclusion
The workshop works if it produces owned, dated next steps. Keep it hands-on and use the business's own data. Put follow-up on the calendar before the session ends.
For service businesses, the phone is a good first use case because the problem, missed calls and lost revenue, is easy to measure. Participants can hear real calls, watch the AI book appointments, and see leads captured without staff involvement.
FAQs
How do I pick the right AI use cases for my workshop?
Start with the workshop goal and your team's real pain points. Pick use cases that fit your industry, your current tools, and your constraints. Then rank them by impact and feasibility.
What should attendees prepare before the workshop?
Attendees should bring:
- Three to seven days of call logs: volume, peak times, common questions, missed calls
- A basic knowledge base of services, pricing, hours, and top FAQs
- A draft call script and a few test scenarios
- Logins for connected tools like the CRM and calendar
How do I measure ROI after launching an AI answering tool?
Compare call volume, missed calls, and call duration before and after launch. Track answered calls, captured leads, and booked appointments. Weigh the revenue from those conversions and any staffing savings against the cost of the tool.
Related Blog Posts
Book a walkthrough
See it handle your calls.
Book 20 minutes, or hear a sample call first.
