[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"documentation:page:\u002Fdocumentation\u002Fgetting-started":3,"documentation:nav":222},{"id":4,"title":5,"body":6,"category":211,"description":212,"extension":213,"meta":214,"navigation":215,"order":216,"path":217,"seo":218,"stem":219,"updated":220,"__hash__":221},"documentation\u002Fdocumentation\u002Fgetting-started.md","Getting started",{"type":7,"value":8,"toc":198},"minimark",[9,13,18,23,31,35,48,52,55,104,111,115,123,127,152,156],[10,11,12],"p",{},"Joely is a customer support platform built for Tebex shops. Your team handles tickets from a staff dashboard, while your customers open and follow their requests on a branded customer portal, with optional Discord and GitHub integrations on top.",[14,15,17],"h2",{"id":16},"key-concepts","Key concepts",[19,20,22],"h3",{"id":21},"projects","Projects",[10,24,25,26,30],{},"Everything in Joely lives inside a ",[27,28,29],"strong",{},"project",". A project represents one shop or community: it has its own team, tickets, Tebex stores, branding, and settings. You can be a member of several projects and switch between them from the dashboard.",[19,32,34],{"id":33},"tickets","Tickets",[10,36,37,38,41,42,47],{},"A ",[27,39,40],{},"ticket"," is a single support conversation between a customer and your team. Every ticket has a status (see ",[43,44,46],"a",{"href":45},"\u002Fdocumentation\u002Ftickets\u002Fstatuses","Ticket statuses","), an optional priority, optional assignees, and a message thread that both sides contribute to. Tickets can be linked to one or more Tebex packages and to a GitHub issue.",[19,49,51],{"id":50},"staff-dashboard-vs-customer-portal","Staff dashboard vs customer portal",[10,53,54],{},"Joely has two distinct sides:",[56,57,58,74],"table",{},[59,60,61],"thead",{},[62,63,64,68,71],"tr",{},[65,66,67],"th",{},"Side",[65,69,70],{},"Who uses it",[65,72,73],{},"What it does",[75,76,77,91],"tbody",{},[62,78,79,85,88],{},[80,81,82],"td",{},[27,83,84],{},"Staff dashboard",[80,86,87],{},"You and your team",[80,89,90],{},"Manage tickets, reply to customers, configure integrations, view CSAT analytics",[62,92,93,98,101],{},[80,94,95],{},[27,96,97],{},"Customer portal",[80,99,100],{},"Your customers",[80,102,103],{},"Open tickets, reply, check purchases, answer satisfaction surveys",[10,105,106,107,110],{},"Customers sign in to the portal with their ",[27,108,109],{},"Cfx.re account",", no password to create. Staff accounts and customer accounts are fully separate, even when the same person owns both.",[19,112,114],{"id":113},"roles-and-permissions","Roles and permissions",[10,116,117,118,122],{},"Team members have roles (built-in or custom) that control exactly what they can do, from replying to tickets to managing integrations. See ",[43,119,121],{"href":120},"\u002Fdocumentation\u002Fteam\u002Froles-permissions","Roles & permissions",".",[19,124,126],{"id":125},"integrations","Integrations",[128,129,130,138,145],"ul",{},[131,132,133,137],"li",{},[43,134,136],{"href":135},"\u002Fdocumentation\u002Fintegrations\u002Ftebex","Tebex",": connect your stores, look up purchases, create coupons and gift cards from tickets",[131,139,140,144],{},[43,141,143],{"href":142},"\u002Fdocumentation\u002Fintegrations\u002Fdiscord","Discord",": DM notifications for customers and rich embeds for your server",[131,146,147,151],{},[43,148,150],{"href":149},"\u002Fdocumentation\u002Fintegrations\u002Fgithub","GitHub",": turn bug reports into GitHub issues without leaving the ticket",[14,153,155],{"id":154},"where-to-go-next","Where to go next",[157,158,159,164,171,178,184,191],"ol",{},[131,160,161,163],{},[43,162,46],{"href":45},": what each status means and who can do what",[131,165,166,170],{},[43,167,169],{"href":168},"\u002Fdocumentation\u002Ftickets\u002Flifecycle","Ticket lifecycle",": from creation to closure, including scheduled closure and deletion",[131,172,173,177],{},[43,174,176],{"href":175},"\u002Fdocumentation\u002Fai\u002Fassistant","AI assistant",": auto-responses, drafts, approval mode, and monthly limits",[131,179,180,183],{},[43,181,97],{"href":182},"\u002Fdocumentation\u002Fportal\u002Foverview",": what your customers can do",[131,185,186,190],{},[43,187,189],{"href":188},"\u002Fdocumentation\u002Fcsat","CSAT surveys",": how satisfaction surveys are triggered and collected",[131,192,193,197],{},[43,194,196],{"href":195},"\u002Fdocumentation\u002Fplans-limits","Plans & limits",": what each plan includes and how limits behave",{"title":199,"searchDepth":200,"depth":200,"links":201},"",2,[202,210],{"id":16,"depth":200,"text":17,"children":203},[204,206,207,208,209],{"id":21,"depth":205,"text":22},3,{"id":33,"depth":205,"text":34},{"id":50,"depth":205,"text":51},{"id":113,"depth":205,"text":114},{"id":125,"depth":205,"text":126},{"id":154,"depth":200,"text":155},"getting-started","What Joely is, how projects, tickets, and the customer portal fit together, and where to go next.","md",{},true,1,"\u002Fdocumentation\u002Fgetting-started",{"title":5,"description":212},"documentation\u002Fgetting-started","2026-06-07","-uVvBnbg1NMED8gxAb0gswzCtlUgCOgKwT2oTjACTkQ",[223,225,226,230,232,234,235,237,239,240,243,246,248,249,253,256,259,261,264,268,271],{"title":97,"path":182,"category":224,"order":224},null,{"title":169,"path":168,"category":224,"order":224},{"title":227,"path":228,"category":229,"order":216},"Account & security","\u002Fdocumentation\u002Faccount\u002Fsecurity","account",{"title":176,"path":175,"category":231,"order":216},"ai",{"title":189,"path":188,"category":233,"order":216},"csat",{"title":5,"path":217,"category":211,"order":216},{"title":236,"path":135,"category":125,"order":216},"Tebex integration",{"title":121,"path":120,"category":238,"order":216},"team",{"title":46,"path":45,"category":33,"order":216},{"title":241,"path":242,"category":229,"order":200},"Notifications","\u002Fdocumentation\u002Faccount\u002Fnotifications",{"title":244,"path":245,"category":231,"order":200},"AI knowledge base","\u002Fdocumentation\u002Fai\u002Fknowledge",{"title":247,"path":142,"category":125,"order":200},"Discord integration",{"title":196,"path":195,"category":211,"order":200},{"title":250,"path":251,"category":252,"order":200},"Portal customization","\u002Fdocumentation\u002Fportal\u002Fbranding","portal",{"title":254,"path":255,"category":238,"order":200},"Members & invitations","\u002Fdocumentation\u002Fteam\u002Fmembers-invitations",{"title":257,"path":258,"category":231,"order":205},"Writing AI-ready documentation","\u002Fdocumentation\u002Fai\u002Fwriting-ai-ready-docs",{"title":260,"path":149,"category":125,"order":205},"GitHub integration",{"title":262,"path":263,"category":33,"order":205},"Messages & conversation","\u002Fdocumentation\u002Ftickets\u002Fmessages",{"title":265,"path":266,"category":125,"order":267},"Tebex keys & security","\u002Fdocumentation\u002Fintegrations\u002Ftebex-keys",4,{"title":269,"path":270,"category":33,"order":267},"Configuring the ticket form","\u002Fdocumentation\u002Ftickets\u002Fconfiguration",{"title":272,"path":273,"category":125,"order":274},"Self-hosted Tebex Bridge","\u002Fdocumentation\u002Fintegrations\u002Ftebex-bridge",5]