Shared ticket portal / internal ticket management between Boulevard and TAG/Chapter
WHAT IT IS:
A shared portal (Jira / Salesforce style) for submitting and tracking support tickets, rather than email threads.
USE CASE:
TAG runs its own internal support desk; studios escalate up through their RBM to TAG, and TAG escalates to the vendor. They want ticket status visibility they can pull themselves, plus ticket review as a standing item in the weekly technical call.
PROSPECT:
Chapter Aesthetics - 22 locations; on Zenoti (systems partner: TAG). Requested by: Alex Cross
PROSPECT BRIEF:
https://docs.google.com/document/d/1pVt5pETENFmy0BNeRdgKx6DXI2KQHGHR-1tu555qWoU/edit?tab=t.0
PRODUCT AREA (suggested):
Support / Enterprise
VERBATIM QUOTES (call timestamps):
"do you have like a portal where we can go and submit service, tickets, things like that cause currently right now with zenoti where we just send emails back and forth. So it's kind of hard to track where things are at. So those are two big hurdles that we have with zenoti."
GONG CALL (8/19):
https://us-9385.app.gong.io/call?id=1617315346930137713
RELATED / POSSIBLE DUPLICATES:
Also an ask from Alpha Aesthetics (customer-facing support ticket portal). Consider merging into one idea.
SOURCE:
Posted by Tiffany Messenger in #voiceoftheprospect-strategic on 2026-08-20: https://blvd.slack.com/archives/C0BHUAATRC6/p1787239563842089