Skip to main content
Set up where client requests go, what clients can see, and which request forms they can use. This page is for MSP staff with Ticket settings access. Launch Center’s Set up tickets step has Statuses, Delivery and Display groups tabs. Request templates are an item in the Portal checklist.

Before you start

  • You need write or manage access to Ticket settings in Settings > Tickets. Without it, the Delivery and Display groups tabs offer Open ticket settings instead.
  • To deliver tickets to your PSA, connect it first. See PSA connection. Set up tickets opens after Connect your PSA.
  • Your rollout companies must exist.
  • Have a monitored email address for fallback delivery.

Set ticket statuses

On the Statuses tab, choose which PSA statuses close and resolve a ticket. When your PSA sets up inside Launch Center, this is the connection’s Configure tickets task. See PSA connection for its fields.

Set up ticket delivery

1

Open the tab

In Launch Center, open Set up tickets and click the Delivery tab. It shows the Ticket Delivery & Defaults card from Settings > Tickets > General.
2

Choose the delivery method

Set Delivery Method to PSA Integration to create tickets in your PSA, or Email (SMTP) to send them to an email address. The change saves right away.
3

Set the destination

For PSA delivery, choose the PSA Integration, then enter a Fallback Email Address that gets the ticket if the PSA connection fails. For email delivery, enter the Email Address (for email delivery). Each field saves when you click out of it.
4

Set the ticket defaults

Under Ticket Defaults, pick the routing values for your PSA, such as board or queue, priority, status, and type. Click Save Defaults.
5

Test it

Submit a test request and confirm it reaches the right place with the right defaults. A finished step does not prove a message arrived.
Set up tickets turns done when delivery has a valid destination and the PSA’s ticket configuration is done. For email delivery, that means a configured email address. For PSA delivery, it needs an active selected PSA. If the selected PSA is later disabled or paused, the step needs attention. See Ticket settings for every card.

Review ticket visibility

1

Open the tab

Click the Display groups tab. If you see Choose your PSA for tickets first, select the PSA on the Delivery tab. Display groups apply to your selected PSA.
2

Create a display group

Click Create Group. Enter a Group Name, choose Ticket Visibility (All Tickets, Same Location Only, or Own Tickets Only), assign the client roles, and choose the boards, ticket types, fields, and the statuses portal users may set. Save the group.
3

Test with client roles

Check a limited user and a client administrator against real tickets. Look at internal notes, closed work, and the statuses they can set. Do not assume one fixed set of status categories applies to every provider.

Make a request template available

1

Open the templates

In Launch Center, open Portal checklist and click Open settings on Ticket request templates. It opens Settings > Tickets > Templates in a new tab.
2

Create or pick a template

Create a template, or open an existing one. Follow How to create a ticket template for each field. Keep the switch labelled Template is active and available for use on.
3

Choose who can use it

Open Company Visibility in the template. Turn the template on for your rollout companies. Under Role Access, check that client roles can use it. A template that only staff can see is not available to clients.
4

Save

Save the template.
5

Submit it as a client

Sign in as a client, or use your approved review process. Open Home or Tickets, pick the template, and send a request. A draft is not a submitted ticket.
The checklist item counts enabled request templates and ticks itself once there is at least one. That count does not check each company. Every rollout company needs an enabled client-visible template that applies to it. A company-wide template covers a company only where it is not switched off for that company.

Troubleshooting

Frequently asked questions

No. Delivery supports email and PSA. Set the method and its destination.
No. It checks stored settings. Send a test request.
No. Each rollout company needs a client-visible template that is enabled for it.