Debunking the top 10 myths about Chatbots
Using Freshservice
Recently active
Hello Freshworks Community!How's it going? Hope you all are having a great week so far!I’m Suvashini, Prinicipal Customer Success Engineer here at Freshworks! I’m also your Community SME and my key product focus areas are Freshservice and Freshservice for Business Teams!I wanted to share some best practices on corporate on-boarding and thought the best way would be through a story! So grab you cuppa coffee or tea and let’s dive right in ☕🍵🤓! ⛈⛈ Rain hammered against the sleek glass windows of Technex Corp HQ, mirroring the storm brewing inside Maya. Her first day as a data analyst, and the only welcome she'd received was a generic automated email with a login and a frowny-faced Slack invite called "Newbie_Hole" "Ugh, where's HR?" Maya sighed, scrolling through the endless channels of a cluttered digital workplace. The "Newbie_Hole" was a firehose of questions and frantic emojis, none of them answered.Suddenly, a notification popped up, a video call request from "TechNexBot_Onboarding
We are in the process of implementing Onboarding and have noticed that FreshService has an odd behavious of auto checking a checkbox when clicking on an item. For example, if the user selects an app and OnClick it will expand the service item and display its description which is great! We want the user to be able to read the info on whether the item is required for them or not but the checkbox is automatically ticked. We dont want this as the user may or may not know if the item is required and merely trying to read the description auto selects the item. I guess is there a way to change this behavious using JS and portal designer?
Is there a way to allow all users within our HR department to see all Onboarding requests ? At the moment, when a HR user logs into the support portal and requests a new employee all of the tickets are created and that request is visible in the support portal under onboarding requests. However, if another HR user logs into the support portal they cannot see that onboarding request and they will occasionally submit another request for the same new employee. If there was a way to allow an entire department see all Onboarding requests, that would be awesome but I can’t find anyway to do that. Am I missing something ?
I’m trying to automate our Onboarding process that our HR teams kick off via a Google Form.With this in mind, is there a way that FreshService could start the OnBoarding process via an email rather than have the user in HR have to manually type in email address, name,etc or is this process still a manual process?
Hello everyone,I’ve been using FreshService Workflows for a little over a year now and have started hitting limitations with processes related to Employee Onboarding and Offboarding. Since we are 100% cloud-based and don’t have an on-prem AD, the AD PowerShell app is not an option for us.I’m facing challenges with tasks that can be easily accomplished through PowerShell modules but are not supported by the current Azure AD orchestrator, such as:Managing shared mailboxes Updating membership for mail-enabled security groups Hiding accounts from the Global Address List (GAL) Other advanced actions available in PowerShell modulesUnfortunately, FreshService’s Azure AD orchestrator falls short, covering only about 50% of our onboarding and offboarding processes. For the remaining tasks, we still have to manually access Exchange Admin and Entra AD, which is far from ideal.I’ve reached out to support to ask if an Azure AD PowerShell orchestrator is in development, but I haven’t had any luck so
How are people handling the Offboarding Form, where it requires a user email, but the user is deactivated? For example, our HR department calls IT with a confidential, or urgent, user offboarding request requiring their account to be deactivated immediately. We deactivate the user in AD, which then deactivates the user in Freshservice through AD integration.Because the user is now deactivated in Freshservice, when HR goes to submit the official Offboarding request, they are unable to enter the user’s email in the required field on the Offboarding form because the user is deactivted.
Onboarding tickets can’t be shared via the “share tickets with department” interface.Onboarding tickets form fields can’t be edited. Despite presenting a similar visual interface to Service Catalog Items, which _can_ be edited after submission.Onboarding tickets can be shared with the new Sharing API, but they won’t show up in Employe Journeys.Onboarding tickets submitted by other users do not show up for Business Agent users with Onboarding Supervisor (or general Admin level) permissions in Employee Journeys. Even though Business users licenses are marketed as a way to integrate HR and other business teams who might need insight into the onboarding process. These accounts can’t see all of the available Onboarding tickets in the Employee Journeys section. The tickets do show up in the tickets module, but look like every other ticket, which renders moot the whole point of the separate Employee Journeys section. Onboarding tickets are limited to (3) stakeholders. Any stakeholders added a
Hi,We will soon be using the Freshservice onboarding process for new employees. Some permissions for our ERP system need to be approved by designated business champions. We use “custom objects” and the “workflow automator” with the “reader function” to select the appropriate approver.So far, so good—the approval is sent to the right person. However, the challenge is that these approvers are not Freshservice agents, just regular requesters. Without agent permissions, they do not receive/reach any information from the onboarding process, such as the planned role in the ERP system. This lack of information prevents the approver from making an informed decision.We created a second “workflow automator” with the following setup: Event: Ticket is updated, Condition: Approval Requested, Action: Share ticket with Approver. Unfortunately, this is not working, and the ticket is not being shared with the approver.Our question is: How can we make the onboarding information available to the approver
We are finding that when requesters are logging into the helpdesk for the first time via the Google Account option, they are being created with a time zone of US rather than UK, yet if we manually create the requester accounts the time zone is set as UK. I have been told this is because their Google accounts are set to a US time zone but having looked at our Admin settings for our Google Workspace, we can confirm that the locale time zone is set to UK. Surely i’m not the only one having this issue?
In our onboarding flow HR enters in a new hire request via the portal. Then an email is sent to the hiring manager to specify the access the new hires needs. For compliance reasons this has to be filled out by the hiring manager or above. We have recently found out that some manager have been forwarding the link to subordinates to fill out. Is there a way to restrict that link so it can only be accessed by the hiring manager?
Hi all, I am currently experiencing an issue with my employee on-boarding form in regards to implementing it in an automation workflow. The issue is documented as follows with the following screenshots.Workflow for this processThe process goes as followsService request is raised Condition node checks to see if the subject is an employee on-boarding request An email is then sent out using placeholder fields, which is the ticket subject, ID and ticket description.However, Body of the email in the action node. Thankfully, the flow works successfully, barring one issue which is the ticket description is not received. Email Upon checking the ticket itself however to see why this might be, I noticed the actual description field was empty. Empty Ticket DescriptionIs there anyway to update the Ticket description field to contain the employee information or get the employee information into the email another way.
I am wondering if anyone else has come across this and has found the solution; when I submit an Onboarding Request via the Freshservice API the Employee Information section is not being populated in the Parent or Child Tickets.This data is present when submitting the Onboarding Request manually:Onboarding Request when manually submittedOnboarding Request when submitted via the Freshservice APIAs the Child Tickets are being generated that suggests to me that the Onboarding Request flow is triggering correctly but the part where it ‘Add Hire’s Information to the Ticket’ is simply not happening on the Parent and Child Tickets:We rely upon automated Onboarding procedures (including automatic ticket generation) so without this information in the tickets, when submitted via the Freshservice API, they are not fit for purpose so I’m eager to get this fixed.
Hello! I’m trying to create our pass at using the Employee Onboarding module within Freshservice. I’d like to create a Microsoft Exchange calendar entry for the event “Date of Joining”, this is captured in a date field on the onboarding form. I want this to serve as a notification on a shared calendar as an All Day Event on the shared calendar for the relevant stakeholdrrs.I am attempting to create this in the workflow automator however, I’ve set the attribute on the Microsoft Exchange Orchestration Node to is_all_day to true; however when testing I get the error “Your request can't be completed. The duration of an event marked as All day must be at least 24 hours.” Does anyone have some guidance on how I can achieve this, or have any potential workarounds?
Hello all, I wanted to see if someone can assist me in addressing a question I have before I sign a contract with a 3rd party integrator (Aquera). The goal is that our ATS (recruiting system- Greenhouse) will automatically send the employee onboarding to Freshservice after the status changes in greenhouse to “hired”.We fully leverage employee onboarding kits in Freshservice, and they work perfectly.The question is, when using the API for onboarding, are the only datapoints required the ones on the first page of onboarding? Currently, when i onboard an employee directly in Freshservice front end, on page 1 i fill in the details that trigger the kits, but page 2 shows me the ouput of the automated kits, and i hit submit on page 2…With the API, i wanted to confirm that i’d only need to enter the datapoints, and that the API would automatically process that onboarding ticket INCLUDING the kits… Has anyone else done this or can confirm/help? Thanks,!!
