1. Executive Summary

EGP already has four service_desk projects on the Atlassian Cloud tenant (EGPSUP, SUP, EGPSD, EQX) plus the Customer Success and SWAT Confluence spaces, but no public customer-facing Support Center is live and Support.EnRouteGrowthPlatform.io is unpointed. The recommended path consolidates onto a single canonical JSM project (EGPSUP, "EGP Support") with a themed out-of-box portal exposed at Support.EnRouteGrowthPlatform.io via Atlassian custom domain plus Cloudflare DNS, layered with the EGP knowledge base from Confluence (EGPCSDEFCON for paying customers, EKB for public-facing). Estimated 7 to 10 working days to go live end-to-end assuming JSM Standard license is on the tenant, no green-field rebuild required, and infra DNS access is granted on day 1.

2. What's Already Completed

Inventory pulled live from Atlassian MCP on 2026-05-18.

Jira service_desk projects already provisioned

KeyNameTypeState
EGPSUP (id 10686)EGP Supportservice_deskLive, 3 tickets (Adorn Spa DNS change 2026-03-18 to 03-20). Has Change issue type live. CANONICAL
SUP (id 10287)Supportservice_deskLegacy catch-all, archive candidate
EGPSD (id 10653)EGP Service Deskservice_deskDuplicate, has Customer Support category (port to EGPSUP)
EQX (id 10553)EGP Jira Service Management Alpha Launchsoftware (despite name)165+ alpha QA tickets from Jan 2026, rename to "EGP Internal QA"

Confluence spaces ready to back the portal

Domain / DNS

EnRouteGrowthPlatform.io is registered and operated on Cloudflare. support subdomain is currently unpointed (no CNAME).

3. Where We Left Off

4. Jira Space Details

4.1 Project consolidation decision

ProjectVerdictRationale
EGPSUPKEEP, canonicalAlready service_desk, already has Change + approval workflow, already has live tickets, name aligns with brand.
EGPSDArchive after migratingDuplicate of EGPSUP. Port "Customer Support" category to EGPSUP.
SUPArchiveGeneric 2-char key, predates EGP namespace.
EQXRename "EGP Internal QA"Software project type, keep for Aisha's web QA work, do not expose to customers.

4.2 Canonical JSM project

4.3 Issue types

  1. Service Request (default for "I want something")
  2. Incident (default for "something is broken")
  3. Problem (root-cause parent for repeat Incidents)
  4. Change (already live on EGPSUP-1)
  5. Knowledge (KB seed tickets promoted to Confluence EKB)

4.4 Request types

Request typeQueueDefault assigneeSLA
Report a bug or outageTier 1 IncidentAisha1 hr response, 8 hr resolve
Ask a billing questionBillingLeda4 hr response, 2 biz day resolve
Request a domain or DNS changeChangeSurafel (once licensed)1 biz day response, 5 biz day resolve
Request a new featureProduct IntakeMarc5 biz day response, triage only
Get help using EGPTier 1 GeneralAisha4 hr response, 1 biz day resolve
Onboard a new customer siteOnboardingSurafel1 biz day response, 10 biz day resolve
Submit a security or compliance concernSecurity (private)Marc30 min response, 4 hr triage

4.5 Queues

Q1 Unassigned · Q2 Tier 1 Incidents · Q3 Billing · Q4 Change · Q5 Product Intake · Q6 Security (restricted) · Q7 Awaiting Customer · Q8 Resolved last 30 days.

4.6 SLA + 4.7 Permissions

SLAs per 4.4. Calendar 24x7 for Incident + Security, biz hours ET for others. Customers portal-only with Organizations isolation; Agents (Marc, Aisha, Leda, Surafel) full project access; Security queue restricted to Marc only.

5. Domain and Portal

5.1 Bringing Support.EnRouteGrowthPlatform.io online

  1. Atlassian admin: Settings → Products → JSM → Customer Domains → Add Support.EnRouteGrowthPlatform.io.
  2. Atlassian issues a CNAME target (e.g. cdn-domain-XXXX.cdn.atlassian.com) and a TXT verification record.
  3. Cloudflare DNS: add DNS-only (not proxied) CNAME support → Atlassian target, plus TXT if requested.
  4. Atlassian provisions Let's Encrypt cert (15 to 60 min typical, up to 24 hr worst case).
  5. Set EGPSUP as the only published portal, configure announcement banner.
  6. Test https://Support.EnRouteGrowthPlatform.io.

5.2 Portal UI

Phase 1: Out-of-box Atlassian Help Center with EGP palette (logo, primary #0B5394, banner, request-type icons). Phase 2 (post-launch, week 4+): Evaluate custom CF-Pages front-end (Path B) only if Marc decides the OOB UI feels too Atlassian-branded.

5.3 SSO

Customers: no SSO, email + magic link (Atlassian default). Agents: Atlassian SSO via @enroute.global Google Workspace. Do not put Cloudflare Access in front of the portal, it would block customers.

6. Runbook

#TaskOwnerEffortDepsDefinition of Done
T-01Audit JSM license tierVesta30 minAdmin accessTier captured
T-02Marc ratify consolidation planMarc15 minThis docMarc signs off
T-03License Surafel as AgentMarc + Vesta15 minT-02Surafel sees queues
T-04Migrate tickets out of SUP + EGPSDAisha2 hrT-02Source projects empty
T-05Archive SUP + EGPSDVesta10 minT-04Archived
T-06Rename EQX to "EGP Internal QA", restrictVesta30 minT-02Customers cannot reach
T-07Configure 5 issue typesVesta + Aisha2 hrT-03All 5 live
T-08Configure 7 request typesAisha3 hrT-07All 7 testable
T-09Configure 8 queuesAisha1 hrT-08Auto-routing live
T-10Configure SLAsAisha2 hrT-09Breach alerts fire
T-11Permission schemesVesta1 hrT-09Impersonation test passes
T-12Wire EKB to portalGemma1 hrT-08Search returns 5+ articles
T-13Wire EGPCSDEFCON as internal KBGemma30 minT-12Agents see CS articles
T-14Seed 10 founding KB articlesGemma6 hrT-1210 articles published
T-15Apply EGP palette + logoGemma2 hrT-08Brand-book match
T-16Atlassian custom domain configVesta30 minT-15CNAME + TXT targets in hand
T-17Cloudflare DNS recordsMarc or Surafel15 minT-16dig returns Atlassian target
T-18TLS cert + domain verify (wait)Vesta (monitor)up to 24 hrT-17HTTPS loads with valid cert
T-19Atlassian SSO for agentsVesta2 hrT-114 agents SSO works
T-20E2E smoke test all 7 request typesAisha3 hrT-19All 7 route correctly
T-21Customer onboarding email blastLeda + Gemma2 hrT-20Email sent, logins seeded
T-22Add Support link to main navSurafel30 minT-18Nav live
T-23GHL Conversations → JSM webhook bridgeSurafel4 hrT-20DM creates ticket
T-24Document in EGPSWAT runbookVesta2 hrT-23Runbook published
T-25Marc walkthrough + go-liveMarc30 minT-24Marc says "go live"

Total: ~38 person-hours plus a 24-hour TLS cert window. Calendar: 7 to 10 working days.

7. SWOT

Strengths

  • 4 JSM projects already provisioned
  • Confluence spaces stood up
  • Atlassian MCP live for automation
  • EGPSUP has live Change workflow
  • Brand domain ready on Cloudflare

Weaknesses

  • Surafel still unlicensed
  • SUP + EGPSD + EQX fragmentation
  • No KB articles seeded
  • No published portal
  • Customer onboarding never run

Opportunities

  • Customers expect a real Support Center for retention
  • JSM Help Center is enterprise-credible
  • Atlassian native custom-domain support is mature
  • EKB becomes public SEO surface

Threats

  • JSM license cost scales per agent ($22 to $50/agent/mo Standard)
  • Atlassian Cloud incidents would take EGP support down
  • Customers misusing portal for sales clogs queues

8. Five Solution Paths

Path A — Pure JSM out-of-box, theme-only   RECOMMENDED

EGPSUP becomes canonical, Atlassian Help Center is the portal, branded with EGP palette, exposed at Support.EnRouteGrowthPlatform.io via Atlassian custom domain. Lowest effort (7 to 10 days), uses what's already paid for, Atlassian handles TLS + uptime + auth + KB. Cons: Help Center UI is recognizably Atlassian, limited theming. Effort: 38 person-hours. Verdict: LAND THIS, iterate later.

Path B — JSM + custom CF Pages frontend

Same JSM backend, custom Next.js or Astro frontend on Cloudflare Pages talking to Atlassian REST API. Pros: fully custom UX, brand-perfect, embed billing + status + account widgets. Cons: 3 to 5 weeks dev, ongoing maintenance, reimplement auth + uploads + notifications. Effort: 120 to 180 hr. Phase 3 only.

Path C — GHL Conversations as customer surface, JSM backend, webhook bridge

Customers chat in GHL widget; webhook creates EGPSUP ticket; agent replies in JSM; mirror back to GHL. Pros: low-friction chat UX. Cons: fragile bridge, messy threading, no self-service KB, no SLA visibility. Effort: 50 to 70 hr. Useful as a Path A complement (T-23), not a replacement.

Path D — Hybrid: JSM portal for paying customers, GHL chat for prospects

Path A for paying customers (gated portal), Path C lite for prospects (GHL chat). Right tool for each audience. This is effectively Path A + T-23 = 42 hr. Adopt as Phase 1.

Path E — Build entirely on CF Pages + Worker + D1, skip JSM

Custom support system on Cloudflare. Max control, no per-agent fees, EGP-owned IP. Cons: 8 to 12 weeks rebuilding 20 years of Atlassian's roadmap. Effort: 400+ hr. Rejected.

9. Top 3 Risks of Recommended Path (A + D-lite)

1. JSM license tier insufficient. If tenant is on JSM Free (3 agents max), the 4-agent team cannot all be agents. Mitigation: T-01 verifies first; upgrade to Standard at ~$88/month for 4 agents.
2. Atlassian custom-domain TLS provisioning delay. Cert issuance can take 24 hr and occasionally fails first attempt. Mitigation: interim portal URL works the whole time; do not block launch on custom domain, swap when ready.
3. Customer queue contamination from sales inquiries. Once Support.EnRouteGrowthPlatform.io exists, prospects will use it for sales questions. Mitigation: add "Sales inquiry" request type that auto-routes to Leda + closes with a redirect to GHL sales chat.

10. Sprint 1 Jira Stories

Suggested keySummaryAcceptance criteria
EGPSUP-4Verify JSM license tier + provision Surafel as AgentLicense captured; Surafel logs in, sees Tier 1 Incident queue
EGPSUP-5Configure issue types, request types, queues, SLAs per section 45 issue types live; 7 request types submittable; 8 queues visible; SLA breach alerts fire to Marc in test
EGPSUP-6Bring Support.EnRouteGrowthPlatform.io online via Atlassian custom domain + Cloudflare CNAMEHTTPS loads portal with valid TLS cert; Support link added to main nav
EGPSUP-7 (stretch)Seed EKB with 10 founding KB articles + wire to portal search10 articles published, searchable from portal
EGPSUP-8 (stretch)E2E smoke test + document in EGPSWAT runbookAll 7 request types pass; runbook page published