Public Ticket Portal

The public portal lets customers create and reply to tickets from your Bnder Pages domain.

Common public paths include:

  • Create a project ticket: /ticket/{project_id}
  • Open a ticket thread: /ticket/thread/{token}
  • View customer tickets: /tickets
  • Request customer login: /tickets/login
  • Unsubscribe: /ticket/unsubscribe/{token}

A domain's landing project controls where visitors go when the URL does not already name a project. A project's branding domain controls the domain used in generated ticket links and emails. Configure both in Pages and ticket settings.

Custom domains become available after DNS ownership and SSL checks succeed. Existing ticket links keep the domain selected when the ticket was created, so review old links before deleting a domain.

Create a ticket

Depending on project settings, the public form can include:

  • Reporter email and name
  • Workspace sign-in with Discord or Slack
  • Title, description, type, and initial message
  • Template fields
  • Attachments
  • Related public knowledge suggestions

Workspace admins can allow anonymous creation or require customer login. When customer portal login is enabled, visitors also see My Tickets.

Ticket-type templates take precedence over the project-wide template. Only fields intended for reporters are shown. Required fields are validated before the ticket is created.

A project-specific customer link can preselect a customer. Public creation adds only the reporter as a notification recipient.

Reporter sign-in

Email is always available. Discord-backed workspaces can additionally offer Discord sign-in, while Slack-native workspaces can offer Slack sign-in.

Workspace sign-in uses a popup and does not require an existing Bnder app account. If the sign-in expires before submission, sign in again.

Knowledge suggestions

When enabled, related public documents appear while the reporter enters the ticket. Suggested documents open separately so the unfinished form remains available.

Attachments

Public forms and ticket threads support file selection and drag and drop. Workspace file-type, per-ticket size, storage, and malware-scanning limits apply.

Files waiting for a scan remain unavailable. Malware and failed scans block public access; workspace admins can retry failed scans. Admins can also configure cleanup of attachments from closed tickets.

Ticket threads

A thread link lets its recipient:

  • Read the public conversation
  • Reply to the support team
  • Add and open public attachments
  • Create another ticket

New public messages appear automatically while the page remains open. Internal notes, agent-only attachments, labels, priorities, assignees, and linked workspace items are never shown.

Each recipient receives an individual secure thread link. Do not forward it to someone who should not have access to the conversation.

Admins can disable public replies or uploads. Existing links remain readable and clearly show when an action is unavailable.

A new reporter reply reopens a resolved or rejected ticket.

Customer portal

When customer login is enabled, customers can request a sign-in link by email. The confirmation page does not reveal whether an email address belongs to a known customer.

Signed-in customers can:

  • View their own current and older tickets
  • Open a ticket and reply
  • Upload attachments when allowed
  • Create another ticket without re-entering contact details
  • Log out from the device

Unsubscribe

Ticket emails include an unsubscribe link. Opening it updates that recipient's notification preference. Invalid or expired links show an error and retry option.

For setup, see Ticket Setup. For domain configuration, see Pages.