Walkthrough Complete - Council Chatbot
You’ve completed the Council Chatbot walkthrough
Great! You've deployed the demo
Now let's walk through what you just deployed and see it in action.
Start WalkthroughChoose your next step
Generate Evidence Pack
Create your business case documentation with what you've learned.
Generate Evidence PackWalkthrough complete
Congratulations! You've just experienced how AI can transform resident services. In 10 minutes, you've seen what would have taken weeks of research and demos with traditional software vendors.
What you've learned
💬 Natural conversation
The chatbot understood questions in plain English, not keywords. It handled location context, follow-ups, and different phrasings naturally.
Value: Residents get help without learning how to "search correctly"
📚 Council-specific knowledge
Responses came from your council's knowledge base, not generic AI training. Accurate, authority-specific answers without expensive customization.
Value: Trust and accuracy without building from scratch
⚡ Instant responses
Sub-3-second responses for complex queries. No menus to navigate, no pages to click through, no waiting on hold.
Value: 24/7 self-service that residents will actually use
💷 Cost-effective scaling
Serverless architecture means you pay per conversation, not per resident. Zero cost when idle, automatic scaling when busy.
Value: No upfront investment, costs match actual usage
Clean up your resources
Your chatbot resources will automatically delete after 2 hours, but you can delete them now to stop any further charges:
- Go to CloudFormation console
-
Find your stack:
ndx-try-council-chatbot-[timestamp] - Select the stack and click "Delete"
- Confirm deletion - this takes 2-3 minutes
Estimated cost so far: Less than £0.50 for a 10-minute evaluation
What if I want to keep exploring?
If you want to continue testing the chatbot:
- Resources will auto-delete after 2 hours total (from deployment)
- Cost: approximately £2-3 per hour of active testing
- Maximum cost: £10 (enforced by template configuration)
You can redeploy the scenario anytime to start fresh.
Questions or feedback?
We'd love to hear about your experience with this walkthrough: