The Hook Use this workflow to add, edit, copy, move, or delete Services, ensuring your teams can accurately categorize tasks and requests when creating tickets.
Before you begin...
- Requires Hotel Admin User Type access.
- Pre-Configuration: Facilities must be created before Services can be nested within them.
- Non-Retroactive: Edits to a Service only apply to tickets created after the change. Existing tickets will not be updated.
- Access Path: Select your User Initials (upper right) > Admin.
The Steps: Adding a New Service
- Select a Facility from the menu on the left. (Note: Services are nested within Facilities, so choose the one most relevant to the task you are creating).
- Scroll down to the Services section and click +Add.
- Fill in the required fields. (Note: See the "Service Field Definitions" table below for a detailed guide on each field).
- Click +Add to save the new Service. Tip for Sorting: To change the order staff see these in, click Sort, then drag and drop the Services into your preferred order.
The Steps: Editing or Moving a Service
- Navigate to the Services section of the relevant Facility.
- Select the specific Service you wish to modify.
- Click the Actions button to view available options.
- To Edit: Select Edit Service, make your changes to the fields, and click Update Service to save.
- To Move: Select Move to, then select a new destination Facility from the dropdown to relocate the Service.
The Steps: Copying or Deleting a Service
- Select the Service and click the Actions button.
- To Copy: Select Copy. Select the destination (Current Hotel, Another Hotel, or Hotel Group), adjust any details in the copy as needed, and save. (Note: This saves time by duplicating existing configurations).
- To Delete: Select Delete and confirm the deletion. (Warning: Deleting a Service removes it permanently from the active list. If a Service is deleted in error, please contact support@actabl.com immediately).
The Result Success: Once saved, the new Service will immediately appear in the ticket creation dropdowns for the designated staff on both Web and Mobile, ensuring teams can accurately categorize requests.
Reference: Service Field Definitions
Field | Definition |
|---|---|
Name (Required) | The display name in the ticket dropdown. Use clear, concise language (e.g., "Towels"). |
Description | Internal reference for how the service should be used. Does not appear on tickets. |
Guest Disclaimer | Static text included on itineraries and confirmation letters for this specific service. |
Contact | Select a vendor from the Local tab to auto-populate them onto the ticket. |
Override Default Alert | Set a custom alert time (in minutes) specific to this service only. |
Staff Toggles | Enable Guest Request or Internal Request to make the service available for those ticket types. |
Roll Over | If enabled, unclosed tickets move to the next day's list at midnight. |
Default Due Date | Enter minutes after creation (e.g., "10") to automatically set the ticket deadline. |
Include in Itinerary | Automatically flags tickets of this type to appear on guest itineraries. |
Hide Special Instructions | Check this to remove the "Special Instructions" field from the ticket creation screen. |
(Note on Deprecated Fields: Fields such as Price, Trade, Image, and Chat Type are no longer in use or have paused development. These can be skipped during configuration).
Would you like me to pull up the definitions and steps for configuring Service Options, which define the unique ticket fields within these Services?
Comments
0 comments
Article is closed for comments.