Coach is the in-product conversational assistant your users talk to when they need clarity on what is happening in their business and what to do next. In the current app experience, users ask free-form questions, get guided answers in chat, open linked detail views, and continue with follow-up prompts that turn insight into concrete next steps.Documentation Index
Fetch the complete documentation index at: https://docs.narrativebanking.com/llms.txt
Use this file to discover all available pages before exploring further.
What’s new in v1.5.7
v1.5.7 makes Coach feel more like a clear business companion and less like a generic chatbot.
- Responses use a cleaner full-width layout instead of a narrow answer bubble.
- Daily briefing items appear as individual insight cards for easier scanning.
- Answers avoid repetitive scope disclaimers when the user is already asking a business question.
- Non-business answers are shorter and gently return the user to business topics.
- Coach leads with evidence and context rather than sounding like it is making the decision for the user.
- Coach is more careful around regulated financial, tax, and legal topics, where it should provide guidance and suggest professional support instead of advice.
- Source sections are shown only when useful source links are available.
- Coach should not claim it has created a project or completed an action unless that action is actually available.
- Partner deployments can configure coaching tone and partner referral language.
Functional flow
1. Initialize or restore a session
1. Initialize or restore a session
Load current conversation context and prior history when the user opens Coach.
2. Stream responses for each user message
2. Stream responses for each user message
Render assistant output incrementally so users see progress instead of waiting for one final payload.
3. Separate content and control handling
3. Separate content and control handling
Handle text chunks, completion signals, and runtime errors as different event types in the UI.
4. Run follow-up workflows after completion
4. Run follow-up workflows after completion
After each completed answer, enable feedback capture and optional guided next-question suggestions.
Integration considerations
Session model
Keep conversation state bound to authenticated user context so resumes and restores remain coherent.
Streaming lifecycle
Design the UI around in-progress, completed, and interrupted answer states.
Context binding
Attach conversations to relevant product entities so follow-up guidance stays grounded.
Feedback loop
Capture explicit user sentiment after messages complete to improve assistant relevance over time.
Common risk patterns
- Session restore drift after account or context switches.
- Duplicate client rendering when stream completion is not handled idempotently.
- Feedback double-submission when retries are not deduplicated.