Table of Contents

Featured Solution: Ticket Briefing

Niamh Ferns Updated by Niamh Ferns

Ticket Briefing

Add automated briefing and debriefing notes for specific customer tickets with our Power Automate Solution template.

  • Briefing notes are automatically added when the ticket is created
  • Debriefing notes are automatically added when the ticket is closed
  • TechBriefing notes are internal
  • ClientBriefing notes are public
Example Configuration

CompanyId

CompanyName

TechBriefing

ContactBriefing

TechDebriefing

ContactDebriefing

0

Aaron PowerPlay Onboarding

This is a TechBriefing note on ticket creation

This is a ContactBriefing note on ticket creation

This is a TechBriefing note on ticket closure

This is a ContactBriefing note on ticket closure

Prerequisites

Video Guide

Step-by-step guide in video form. No audio.

Step-by-Step Guide

  1. Upload the Excel file into a document library in one of the supported locations as specified by the Excel (Business) connector: OneDrive for Business, SharePoint Sites, Office 365 Groups. We are using SharePoint in this demo.
  2. Populate the Excel file with content that will be posted as notes in the ticket. DeskDirector notes support markdown syntax. It does not support HTML. CompanyId can be found in the DeskDirector company profile page URL.
    Example markdown content:

    //TechBriefing
    ### Deed and Viper
    * They have been with us for **5 years**
    * Expect quick responses as they do time sensitive work

    //ContactBriefing
    Thank you for logging a ticket.
    We aim to provide an update to your ticket within **1 hour**

    //TechDebriefing
    Remember to send survey.
  3. Set up required connections in Power Automate, if you don't have these already.
    1. DeskDirector
    2. Microsoft Excel (Business). The account used for the connection needs to have access to the SharePoint file from the previous step.
    3. Microsoft Dataverse
  4. Import the Solution into Power Automate.
    1. Import the source zip
    2. Map your connections from the previous step.
  5. Configure Solution
    1. Open the Config cloud flow
      1. Open the 'Things to configure' scope
      2. 'List rows present in a table' action
        • Location: Group/SharePoint/OneDrive location
        • Document Library: container inside the location where you saved the file
        • File: ticket-briefing-detai.xlsx
        • Table: BriefingTable
      3. Save.
      4. Execute the flow via test run or live run. This will save your configurations. If at any point you want to update any of the configurations, simply update and run the flow again.
    2. Return to Solution overview (previous tab). Make sure the flows are enabled. Other components, like connection references, may say 'Off', but this is fine.
    3. Check that your configs have been saved.
      1. Open the Config Dataverse table.
      2. Select the Data tab, then view Custom columns in the dropdown.
  6. Test the Solution
    1. Create a ticket under a company that has an entry in the briefing table populated earlier.
    2. On ticket creation, briefing notes will appear if any are available
    3. On ticket close, debriefing notes will appear, if any

Further

  • Add filters to the ticket created/closed triggers so that notification-type tickets don't trigger it.
  • If you don't want a particular aspect, e.g, contact briefing/debriefing, you can delete the briefing table columns and flow logic.

How did we do?

Power Automate Template Gallery

Contact