AllisonLeahy
Executive
Joined 12 years ago
User Profile
User Widgets
Contributions
Re: Secure Verification & Khoros care
Climbing on the bandwagon here. I'd be interested in hearing how others are using (or planning to use) this functionality. We're considering implementing this verification flow (or a more rigorous account authentication process) to improve ratio of known-to-anonymous customers served in channel and fill in our CS datasets.Re: Monthly Billable API Calls (BAC)
Great. Thank you both. Looks like we're well within our margins. We recently completed some optimization work that eliminated a login request and thus wiped nearly 50% of our calls. Optimizations beyond that would be like splitting hairs at the current consumption rate. I've noted some spikes in LSW-related activity, which I'd be interested to learn more about. We make less than a thousand Community posts through LSW every month and otherwise leverage the integration for keyword monitoring and alerts.Monthly Billable API Calls (BAC)
How do I find out how many Billable API Calls (BAC) I've used for the month, and what those calls were attributed to? I understand we're contracted to a certain amount of BAC monthly and will want to keep tabs on this now that we've recently started extending our community and leveraging both the Bulk Data API and Community APIs V1 andV2. Anyone know where I can find this info?Re: Single forum - multi lingual
Wendy_SHaha! No shame, no shame. Hope your badge rollout is going well. Never ceases to surprise me how effective badges can be, thanks to that little feeling of delight and accomplishment you feel after receiving a badge. Not to derail the conversation, but how many badges are you starting with? And how are you planning to measure success for this initiative? Whenever you shift your focus, I'd be happy to hop on a call or answer any more specific questions you may have about UX of multiple languages on one Lithium instance.Re: Single forum - multi lingual
Wendy_SAs Claudiusrightly suggested, we dorun our communities on the same instance. Currently we're managing 8 different languages. There are some complications due to the redirects we had to setup to ensure users made it to their appropriate communities, but we made the decision to build on one instance to a) increase opportunities for integration with Fitbit.com and b) increase moderator collaboration. How it works: We pass a member's language settings SSO. That member then lands on the community appropriate for their language. This defaults to English if we do not have a specific language community for that individual. It is possible to navigate to all our communities by selecting another language in the dropdown in the bottom-right. Annoyances: Due to the redirects, if I receive a notification from a Topic I'm following on the Spanish Community, but I'm logged into the English Community, the first click will land me on the main page for the Spanish forums and the second click of the link will land me on the specific discussion. Annoying, but only to those who frequent multiple language communities. If I'm currently logged into the English Community and I click on the profile page of a user who is active on the German Community, for example, I would not be able to see Recent Topics for that user until I switched my language to German. I could still see the Total Messages Posted metric, however. Community Notifications will send from one email address, so if you plan on responding to users who reply to this email address you will have to have someone triage and route the messages to the proper teams. Localization: It took us a while, but we were able to develop a system to maintain our localized strings that works well for us, but I don't think this is any more challenging than it would be to localize different communities. Essentially, we have one master doc with all the strings on the left and columns with each localized version. Our English Community gets the lion's share of the traffic and activity--around 97% down from 99% at launch. For top-level metrics, we often look at the Community as a whole, but we also report out international community metrics on a monthly basis. It would be nice to have the top-level metrics available by Category, but this isn't too much of an issue for us at this point. P.S. Welcome to the Fitbit Community! Would love to hear any feedback you may have on your experience. I'm getting excited to ramp up some new onboarding initiatives, so any recommendations you have in this area would be especially welcome.
