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
Good news: Your resources will automatically delete after 2 hours from deployment. However, you can delete them now to stop any further charges immediately.
- Database content (RDS Aurora)
- Uploaded files (EFS storage)
- Any configuration changes you made
Step-by-step deletion
- Open the CloudFormation console
-
Find your stack
Look for a stack named:
ndx-try-council-chatbot-[timestamp]The timestamp is when you deployed. You can sort by "Created time" to find recent stacks.
-
Select and delete
Select the checkbox next to your stack, then click the Delete button.
-
Confirm deletion
Click Delete in the confirmation dialog. The stack status will change to
DELETE_IN_PROGRESS. -
Wait for completion
Deletion typically takes 5 to 10 minutes. The stack will disappear from the list when complete.
Costs stop after deletion
Estimated evaluation cost: Less than $0.50 for a 15-minute trial
Troubleshooting
Stack shows DELETE_FAILED status
This usually happens when resources can't be automatically cleaned up. Common causes:
- S3 bucket not empty: The bucket may contain files. Go to S3, empty the bucket manually, then retry deletion.
- Lambda functions in use: Wait a few minutes and retry. Sometimes functions take time to fully stop.
- Network interfaces still attached: These usually clear within 5 to 10 minutes. Retry the deletion.
To retry deletion: Select the failed stack and click Delete again.
I can't find my stack in the list
If your stack isn't visible:
- Check the region: Make sure you're viewing US East (N. Virginia) in the console header.
- Stack already deleted: It may have auto-deleted after 2 hours. No action needed!
- View deleted stacks: Click "View nested" dropdown and select "Deleted" to see recently deleted stacks.
Extending your evaluation time
If you want to continue testing beyond the 2-hour limit:
- Resources will auto-delete after 2 hours total (from deployment)
- Cost: approximately $1-2 per hour of active testing
- Maximum cost is capped by template configuration
You can redeploy the scenario anytime to start fresh with a new 2-hour window.
Still having trouble? Contact the NDX:Try team or report an issue on GitHub (opens in new tab).
Questions or feedback?
We'd love to hear about your experience with this walkthrough: