Suggestion Box

We think it would be a very good idea to find and identify a platform where we can request specific linguist with specific language combination that we think Cadence lacks. We have been having a steady increase of needs to have more linguists with rarer language combinations, and we had to do custom recruit.

When there are urgent requests where we need to custom request linguists, sometimes there are no TLs online for a long time in certain timezones and it would be very useful and efficient to empower associates to send contracts to linguists to maximize turnaround times as well as the ability to fulfill very urgent requests

Suggestion to include cancellation policies, as outlined in the schedule document typically uploaded on the Schedule of Services page, on the 'Prices & Services'/'About This Schedule' tab. While arguably most cancellation policies are similar across accounts, there are some nuances and differences still, and I think operations team can save time in trying to confirm the cancellation policy for the particular client account, by having it listed on the schedule of services page directly.

Our knowledge base is in Confluence but wouldn't it be great if we can integrate the two and publish these knowledge within Salesforce as well so we don't have to open multiple tabs during desk hours? I found this on the Atlassian Marketplace that allows us to document pages in Confluence but publish them within Salesforce with a single click: https://marketplace.atlassian.com/apps/1223871/publisher-for-confluence-cloud-to-salesforce?tab=overview&hosting=cloud

I have found that actually we can create the google calendar from inside the jira issue using an app that we can integrate in Jira. Example will be like below: https://marketplace.atlassian.com/apps/1220822/jira-and-google-calendar-integration?tab=overview&hosting=cloud I am not sure if you all use google calendar as well for Jira issue, but if yes, I think this can be a great tool.

TD should go through each request to make sure it is actually action needed for the next associate. When snoozing for updates/nudging for GL, SD should pick a reasonable snooze time on front and TD should honor that snooze time respectively. When TD are doing handovers, TD can check the snnoze time in SD inbox and handover the requst to the assoicate on desk at the snooze time. In this way, SD and TD will be more in sync and the handover pipeline will not be jammed with many requests that are waiting for confirmation from the client. However, SD need to be more careful when choosing the snooze time to make sure we don't miss anything urgent or time-sensitive. Additionally, it would be really helpful if the calendar can relfelct who is on what products.

Reports To is an active field being under utilized. For mutual funds where EAs handle admin steps for investors, this can be helpful tracker and easy hints for Operations team in coordination and for AMs in invoicing.

It looks like the page in the desk manual on delivering machine transcripts is outdated. Also, it does not seem like there is anywhere in Confluence that notes the standard machine transcript compensation of .04 which would be good to note for future Caddies to search (and us if we forget).

Recording dial-ins in Toky have historically been problematic, it would be great if we could brainstorm and look for other alternative platforms for recording calls!