Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Does anyone have any Naming Convention "Best Practices"

    Posted 04-23-2025 15:01
    Edited by Tony Morrow 04-23-2025 17:16
    No replies, thread closed.

    Soon we'll be moving our Engage platform to Cloud, and I was wondering if anyone had any naming convention best practices? 

    We'll have many Divisions, and 1000s of Queues, Skills, Groups, etc.  So looking for something to help keep it organized.

    Such as: 

    • Including Division name in Queue name or Skill name, etc.? 
      Just thinking it could quickly help to know which Division it belongs to.
    • Is it helpful to indicate the object type by including something in its name? (i.e.  Customer_Support_Q vs Customer_Support_SK)
      Thinking this could be helpful in various logs
    • Character limit so its name isn't cutoff in various views?
      Usually this is much less than the actual limit.

    • Prompt naming convention to help segregate IVR prompts from Music on Hold, and Outbound prompts, etc.

    Or anything else that you wished you would have done differently?

    Thanks in advance!


    #ArchitectureandDesign
    #PlatformAdministration
    #Routing(ACD/IVR)

    ------------------------------
    Tony Morrow
    Sr. Genesys Engineer
    ------------------------------



  • 2.  RE: Does anyone have any Naming Convention "Best Practices"

    Posted 05-07-2025 11:59
    No replies, thread closed.

    Hi Tony,

    Do you have a naming convention you currently use?  Maybe others in the community can share what naming conventions they use and you could see if that helps



    ------------------------------
    Sam Jillard
    Online Community Manager/Moderator
    Genesys - Employees
    ------------------------------

    Original Message


  • 3.  RE: Does anyone have any Naming Convention "Best Practices"
    Best Answer

    Posted 05-08-2025 02:52
    No replies, thread closed.

    Hi Tony, 

    Regarding configuration objects like queues, schedules, etc., you can filter them by division. Therefore, including the division in the object names doesn't seem necessary.

    Additionally, you can assign permissions to certain users so that they only see the configuration objects relevant to their division. This way, supervisors will not be able to view any objects that don't belong to their division.



    ------------------------------
    Zbynek Melichar
    Genesys technical owner
    ------------------------------

    Original Message


Related Content