Take, route, and launch workflows from requests with Blissfully's ticketing tool
Blissfully's ticketing tool allows anyone at the company to submit requests using templates you control and provide. Combine tickets with workflows to escalate requests into workflows and keep clear records of why work happened.
The gallery with built-in ticket templates
Blissfully comes with three ticket types built-in:
- 3.Request something else: lets employees request anything that doesn't fit into either of the above ticket types.
If a built-in ticket template is not to your liking, you can add questions in the edit view. You can also choose a default assignee. Similar to tasks in a workflow plan, a ticket can be assigned to a role or a specific person/team.
Upon approval, the ticket will automatically trigger and generate their default workflows. You can disable this option by unchecking the automatic trigger under escalation workflow. When disabled, the ticket assignee/approver will have the option to manually trigger a workflow.
Request access template
If one of the built-in ticket templates is not applicable to or useful for your organization, you can uncheck the Published box to hide it from employees in their portal.
If the built-in ticket templates aren't sufficient, you can create new ticket templates. Start by clicking the "Create new template" button.
First, you'll need to decide if your ticket template is in relation to an app/vendor or not. For example, if you want to let employees request a change in the Owner role of an app, use the app-related ticket type.
Once you select the type and provide a title, move on to the next screen to see the minimum required information for a new ticket template.
The four fields every ticket must have
As with built-in tickets to edit, you will set a default assignee, either a role or a specific person/team.
Additionally, you may select an escalation workflow. When you publish the ticket template and an employee uses it to submit a request, the ticket assignee will have the option to launch that type of workflow as a next step. Escalation workflows link tickets to their ensuing workflows, leaving a paper trail and rationale for why a workflow was launched.
The final required field, the description, will appear below the title in the gallery. Employees will rely on the title and the description to understand what the ticket is for, so be specific!
The remainder of the ticket template contains as many of these form elements as you like:
- Section header
- Person select
- Document upload
- Yes/No dropdown
- Short answer
- Long answer
- Multiple choice
- Choose all that apply
- Date input
- Number input
By default, published ticket templates can be viewed by everyone in the organization. You can select specific teams and limit the ticket access to those teams.
Additional ticket template features
In the App/Vendor ticket template type, collect survey responses for a custom property and populate the value on your application detail page. Click on App Properties dropdown and select the property you'd like to collect information. Add a short description or prompt to help your employees understand the data you're looking for. Select whether or not the data field is required in order to move forward with the submission.
Once you complete the form, hit Save. The completed ticket template will appear in the gallery. Check the Published box to make it available to employees.