All Collections
Templates, Apps & Media
App Guides
Fugo - Share To Screens Bot Guide For Microsoft Teams
Fugo - Share To Screens Bot Guide For Microsoft Teams

How to easily create posts for your digital signage screens from within Microsoft teams with the Fugo - Share To Screens bot.

Sarah avatar
Written by Sarah
Updated over a week ago

Table of Contents


What's the Fugo - Share To Screens bot?

As organizations embrace digital signage in their internal communication strategies, they encounter familiar challenges:

  • Software admins need a quicker way to display content without navigating complex playlists and schedules.

  • Colleagues resist adopting another platform.

  • Designers and People teams lack time for consistent content creation.

  • Audience engagement with digital signage remains a struggle.

Enter the Fugo - Share To Screens bot, integrated into the Microsoft Teams store, offering a practical solution for streamlining your digital signage communication.

It serves as your personal assistant for bridging your Microsoft Teams account with your Fugo-connected digital signage screens. It lets you easily & quickly share Microsoft Teams posts to your screens without any additional configuration or scheduling.

Use it to

  • Quickly push content onto your digital signage screens

  • Share stand-out posts from your Microsoft Teams channels as digital signage content

  • Shout out & celebrate important milestones & achievements in real time

  • Get your colleagues involved in the creation of your digital signage content

Key features

  • Create posts with text only

  • Create posts with media only

  • Create posts with text & media

  • Add audio to your posts

  • Publish your post immediately or add it your Fugo content rotation
    ​

πŸ’‘ Note: To use the Microsoft Teams bot, you will need to have a screen paired to an active Fugo account. Learn more about how to get started here, or sign up for a free Fugo trial here.



How to send Microsoft Teams posts to your screens

Pair a screen to Fugo

In order for your Teams posts to have somewhere to go when you publish them, you'll need to have a screen paired to a Fugo account.

Fugo is a web based player application that will run on any consumer or professional display or media player device.

You can follow the set up & pairing instructions for your particular device platform in our hardware help center or get there quickly with these links πŸ‘‡

We've already paired the browser player to Fugo, and will be using that for our demo.

Once your screen is paired, you're ready to start using the bot!


Create your posts with the Fugo - Share to Screens bot

After installing the Fugo bot, you'll need to add it to your private chat.

From there, you can get started from the suggestion box.

1. Click βž• Create Post to start composing your message.

2. You'll be asked to sign into your Fugo account. Click Sign In and follow the prompt in a new tab to log in & access your Fugo account.

3. Back in Microsoft Teams, you're ready to create your post.

4. Create & style your post using the message composer & click the Send button when you're done to submit your post to Fugo.

Your posts can contain:

  • Text (formatted with the composer tools)

  • Uploaded media

  • Gifs

  • Stickers

You'll get a notification when your post was successfully uploaded to Fugo.

5. You'll be asked to choose which Space you want to publish it to.

If you only have one Space in your account, you will not be prompted to choose.

6. You'll be asked to choose which Screen or Screen Group you want to publish to.

We'll publish our post to the Chrome browser player named "Test Screen" we paired in the section above.

Click Submit after you've chosen.

7. Then, you'll be asked how you'd like to play this post. You have two options:

πŸ”‚ Play Once: This will push your post to your screen immediately, overriding any content currently playing on screen. It will be played one time only.

πŸ” Publish Playlist: This will add your post as a new playlist within the playlist queue in your account. It will be played until you un-publish it.

By default, each post will have a duration of 30 seconds on screen.

8. You'll get a notification that your post was successfully published.

9. If you published your post to Play Once, you should see it appear on your screen within a few seconds.

If you published your post as a new playlist, it will be displayed once it's reached within the playlist queue.

⏳ The default duration for a post is set to 50 seconds. In cases where multiple images are uploaded in a carousel format, the total duration remains 50 seconds, with each image being displayed for an equal amount of time.
​
❗️It's important to note that if audio or video content exceeding 50 seconds in length is uploaded, the overall post duration will automatically extend to match the length of the audio or video. This adjustment can lead to unpredictable playback experiences. As such, we advise you to use audio files that are no longer than 50 seconds, and videos that are 50 seconds or shorter. This is especially crucial when the video is part of a carousel, as it shares playback time with other images or videos in the post.

Fugo will automatically convert each post to a digital signage format. You can view the outcome in your Studio content in Fugo CMS:

πŸ’‘ Note: If you added multiple media files to your post, they'll be displayed as an image carousel, which you can view beneath your Studio canvas:
​

10. You'll find your new playlist listed on your Playlists page in the CMS.

You can remove it by clicking Unpublish.

11. You can return to your Teams chat with the bot any time to create a new post for your screen:



Need help?

If you need help getting the Fugo - Share To Screens bot set up in your Teams account, you can reach out to our support team at support@fugo.ai or send us a message via the handy chat box in the CMS.

Want to learn more about how Fugo can help you with displays in your organization? Book in a free demo to see the platform in action & chat with our team about your project!

Did this answer your question?