Update Gupshup Setup with username retrieval instructions

[SangeetaMishr]

Added instructions for retrieving Gupshup username.

Summary by CodeRabbit

• Documentation
  • Updated pre-onboarding setup documentation with current information.
  • Added new FAQ entry with step-by-step guidance on obtaining your Gupshup username, including instructions for contacting support and required details to include in requests.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the Gupshup Setup documentation file by refreshing the "Last Updated" metadata from October 2025 to January 2026 and adding a new FAQ entry explaining how to find your Gupshup username with step-by-step instructions.

Changes

Cohort / File(s)	Summary
Documentation Update docs/2. Pre Onboarding/02. Gupshup Setup.md	Updated metadata date to January 2026 and added new FAQ item detailing steps to obtain Gupshup username via email support, including required account details and helpful tip.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Update and rename 02. Setup an organisation on GupShup.md to 02. Gups… #433: Modifies the same Gupshup Setup documentation file and introduces/expands FAQ content with similar structural updates.

Suggested reviewers

• Fawas003
• mahajantejas

Poem

🐰 With whiskers twitching, I hop with glee,
These FAQs now help users find their key,
Gupshup secrets in January's light,
Documentation blooms, oh what a sight! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and accurately describes the main change: adding username retrieval instructions to the Gupshup setup documentation, matching the file modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Gupshup-Account-Setup.md

---

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 and usage tips.}

[github-actions]

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/2`. Pre Onboarding/02. Gupshup Setup.md:
- Around line 246-255: Replace the plain email text "partner.support@gupshup.io"
with a mailto link, fix the nested list indentation to 2 spaces for the two
bullets under "Include the Following Details" (the org name and Gupshup app
name), and remove or soften the hard SLA phrase "The Gupshup team will reply
with your username and any guidance, within 24 hours." (e.g., change to "The
Gupshup team will typically reply with your username and guidance" or omit the
timeframe) so the doc passes MD034/MD007 lint rules and avoids an unsupported
promise.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix markdown lint issues and avoid a hard SLA.
The email should be a mailto link (MD034), nested list indentation should be 2 spaces (MD007), and the “within 24 hours” promise is risky unless confirmed.

✅ Proposed edit

-- Send an Email to partner.support@gupshup.io mark a copy to Glific Support Team (to help speed up the process)
+- Send an email to [partner.support@gupshup.io](mailto:partner.support@gupshup.io) and CC the Glific Support Team (to help speed up the process)
 
 - Include the Following Details
 
-    - Your organization name
+  - Your organization name
 
-    - Your Gupshup app name (find it in your Glific instance: Settings → Gupshup)
+  - Your Gupshup app name (find it in your Glific instance: Settings → Gupshup)
 
-The Gupshup team will reply with your username and any guidance, within 24 hours.
+The Gupshup team will reply with your username and any guidance.

🧰 Tools

🪛 LanguageTool

[style] ~246-~246: Consider using “email”.
Context: ...p support team by email. Here’s how: - Send an Email to partner.support@gupshup.io mark a copy ...

(SEND_AN_EMAIL)

---

[style] ~246-~246: Consider using a different verb to strengthen your wording.
Context: ... a copy to Glific Support Team (to help speed up the process) - Include the Following D...

(SPEED_UP_ACCELERATE)

🪛 markdownlint-cli2 (0.20.0)

[warning] 246-246: Bare URL used

(MD034, no-bare-urls)

---

[warning] 250-250: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

[warning] 252-252: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

🤖 Prompt for AI Agents

In `@docs/2`. Pre Onboarding/02. Gupshup Setup.md around lines 246 - 255, Replace
the plain email text "partner.support@gupshup.io" with a mailto link, fix the
nested list indentation to 2 spaces for the two bullets under "Include the
Following Details" (the org name and Gupshup app name), and remove or soften the
hard SLA phrase "The Gupshup team will reply with your username and any
guidance, within 24 hours." (e.g., change to "The Gupshup team will typically
reply with your username and guidance" or omit the timeframe) so the doc passes
MD034/MD007 lint rules and avoids an unsupported promise.