Add doc: label unhandled AI responses and open a support ticket

[SangeetaMishr]

Summary

• Closes Add detailed steps on Label the incoming message & Open a ticket with a human agent #550
• New Use Case doc showing how to chain the Label the incoming message and Open a ticket with a human agent flow actions in an AI fallback path — labeling unhandled queries (e.g. AI_unhandled) and immediately opening a support ticket for a human agent.
• Screenshots captured from a live sample flow (DOCS - AI Fallback Label and Ticket Example) on staging showing both nodes configured and connected.

Test plan

• Preview locally with yarn start and check docs/use-cases/label-unhandled-ai-responses-and-open-a-support-ticket (or equivalent generated slug) renders correctly
• Confirm images load and read-time badge/tags render as expected

Summary by CodeRabbit

• Documentation
  • Added guidance for handling unrecognized AI responses.
  • Documented how to label fallback messages and automatically open support tickets for human follow-up.
  • Included setup, testing, publishing, and tagging instructions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a documentation page describing how to label unhandled AI responses and open a support ticket for a human agent. It covers fallback conditions, sequential flow setup, ticket configuration, publishing and testing steps, verification of labels and tickets, and related tags.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: a new doc about labeling unhandled AI responses and opening a support ticket.
Description check	✅ Passed	The description directly describes the same documentation update and its AI fallback flow actions.
Linked Issues check	✅ Passed	The added doc addresses both requested steps: labeling unhandled messages and opening a ticket for human resolution.
Out of Scope Changes check	✅ Passed	The changes appear limited to the requested documentation page and supporting doc assets, with no unrelated scope shown.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

⚔️ Resolve merge conflicts

• Resolve merge conflict in branch docs/ai-fallback-label-and-ticket

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🚀 Deployed on https://deploy-preview-656--glific-docs.netlify.app

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/Use` Cases/Label Unhandled AI Responses and Open a Support Ticket.md:
- Line 1: Add a descriptive top-level H1 heading at the beginning of the
document before the existing blockquoted “2 minute read” callout, then insert a
blank line between the H1 and callout to satisfy the heading and spacing
requirements.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1c467db8-3987-45a6-bb16-fe819e4c8ae3

📥 Commits

Reviewing files that changed from the base of the PR and between 9be314b and 8c4d713.

⛔ Files ignored due to path filters (3)

• static/img/ai-fallback-ticket/ai-fallback-flow-overview.png is excluded by !**/*.png
• static/img/ai-fallback-ticket/label-unhandled-message.png is excluded by !**/*.png
• static/img/ai-fallback-ticket/open-ticket-after-label.png is excluded by !**/*.png

📒 Files selected for processing (1)

• docs/Use Cases/Label Unhandled AI Responses and Open a Support Ticket.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a top-level page heading before the callout.

The file currently begins with a blockquoted ### heading, triggering MD041 and MD022. Add an H1 title and a blank line before the read-time callout.

Proposed fix

+ # Label Unhandled AI Responses and Open a Support Ticket
+
> ### **2 minute read ...

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	> ### **2 minute read                                                                                                                     `Advanced`**
	# Label Unhandled AI Responses and Open a Support Ticket
	> ### **2 minute read                                                                                                   `Advanced`**

🧰 Tools

🪛 markdownlint-cli2 (0.23.0)

[warning] 1-1: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

---

[warning] 1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/Use` Cases/Label Unhandled AI Responses and Open a Support Ticket.md at
line 1, Add a descriptive top-level H1 heading at the beginning of the document
before the existing blockquoted “2 minute read” callout, then insert a blank
line between the H1 and callout to satisfy the heading and spacing requirements.

Source: Linters/SAST tools