This is PSI Blog, a brand new site by user that's just getting started. Things will be up and running here shortly, but you can subscribe in the meantime if you'd like to stay up to date and receive emails when new content is published!

The updated advance rule donut will allow the creation, edit, audit and delete of Advance rules, business hours rules and after hours rules.  One of it's key new features is the ability to create unconditional forwarding rules very easily. Lets get started on the basics of the tool.

Go to http://advanced-rules.ps.ringcentral.com

Start by putting the in the UID and once it loads click the Filter button.

You can filter by all sorts of options, but the one filter you will mostly likely always want to check is the "Exclude Business and After Hour Rules"  This is because those rules are default on all extensions and you most people want to only see custom rules.  

You can filter by rules that have a specific name, a range of extensions, a site and by extension type.  Extension types are User, Call Queue, Announcement, Digital User, Fax User and Virtual User.

The option to just download the template can be useful if you are just making 24/7 unconditional forwarding rules and don't care to see any existing rules.  

Once you have set your filters by clicking save you will see the filters listed.
If you click the download without setting any filter you will get all rules on the account and the more extensions on the account the longer this will take to download.

The download will consist of a spreadsheet with 3 tabs.

1. Existing Rules - This tab is where you can change existing rules or create new ones (Create/Update Advance Rules).  This is the most advance option, but also gives you all the details and some details form this tab are required to delete rules.
2. 24-7 Forwarding -  This tab is for creating unconditional forwarding rules to a phone number.  You have 3 columns of data here, but you only need the extension and the forwarding number.  If left blank the rule name will be auto generated based on the extension and phone number.   Cloud Connects are working via the platform API and it will accept the format +11 IE: 1113033334444
3. Bulk Delete -  In order to delete a rule you need to know the Rule ID and The Extension ID, both of those values are available from the downloaded details found on the Existing Rules tab.

Once you have made the modifications to the spread sheet tab you can upload the file. Upon the 2nd step of the file upload you will get the option to choose an action. This action directly relates to each tab of the spreadsheet.

The tool will then being the work you have uploaded. The tool will display a status bar and will provide any feed back about any errors that occur as it sends API calls to RC platform to preform the work.


Primary contact for support on this tool is Trevor Kelson, if he is not available please reach out to the Professional Services Development Team.  Enjoy the DOUNT!

This slightly more advance guide will show you how to template holiday schedule rules that will send the calls to the extension's voice mail.   To start with building holiday rules (scheduled rules), what's needed is at least one rule already created inside of service web to use as your template for the other rules.  It is highly recommended that the customer is guided through building the first holiday rule that way the customer can provide and be responsible for those dates.

For the rule that will be used as the template add all the dates, but then make sure the option for call flow is set to send to voice mail. Some other options can be available if the call flow options go to the same place, like the same extension or external number.  If the call flow options need to be unique for each rule, then the details that need to put in to create each rule will need to be put in the spread sheet. Editing unique details for each rule is not going to be covered in this article.

After you have this rule created in Service Web go to the Donut https://advanced-rules.ps.ringcentral.com/advanced-rules  

Put in the UID and then use the filter to only get one rule by using the Extension Range option.  By just putting one extension in the first filed the tool will return only the rules of one extension, so put the extension that has the template rule in that filed. Then select the check box for "Exclude Business..." and click save.

Download the spreadsheet and edit the spread sheet with the additional extensions that will receive this rule.  Put the additional Extensions in the column with the header Extension to Apply Rule To.

Delete all the data after column header "CallHandingAction"  then add to column header Voicemail-Enabled "True" for all rows that have a rule.  

The deleted data is important to remove because that data is specific to the extension that the original rule came from and blank data will default to the corresponding extension's voice mail.  If this is not done all the rules will send the calls to the voice mail of the original rule's extension.

Once the above edit's are done save your spread sheet and upload using the Create/Update Advance Rules action.   This will complete the work and give you a
status as it is working.  

If you need help using more complex options done by the Create/Update Advance Rules Action in this tool please reach out to Trevor Kelson for support.  Enjoy the DOUNT!

In Preparation for the upcoming release I highly recommend you click or paste the following link into your chrome browser's address bar.

chrome://settings/cookies?search=clear+cookies

You should get something like this image.

Like the image shows: Add to "Always Clear Cookies when windows are closed"  

conductor.ps.ringcentral.com     <copy and paste

Enjoy the release!

Conductor release 225, or Sprint 22, brings some major enhancements to the numbers and porting sections, as well as other additions and fixes.

Porting in Conductor has been continually improving and with this latest release, you can now 100% port map a new account; even the existing items in Service Web! This allows you to port map the super admin, existing sites, and users created before the account arrived in PS implementation. Pretty cool!

See all the details about Sprint 22, and previous sprints, in the Conductor Changelog.

As usual, if you have any questions or comments please reach out to us via the Conductor Glip teams or ping someone on the PSi development team.

Scheduled release is Tuesday, August 3rd at 6:00pm MST.

What's new:

• Assign port-in numbers to existing items created in Service Web (Super admin etc...)
• Added CSR upload field to Groups details so all details can be provided via Conductor (max file size 5MB).
• When submitting a port from Conductor, a ZIP file will now be attached to the Salesforce port case that contains all relevant files.
• CSR file and Telecom bill file added to the ZIP file that is attached to the SalesForce case when submitting a port.
• You can now rename user-created Carrier Groups for easier management.
• New error state, 'this number is already taken' when assigning temporary numbers in Numbers section.
• The Bulk uploader will catch character limits for all fields when uploading, rather than the erroring in the sync pre-flight.
• Various issues, minor fixes and small improvements.
• See all the details about Sprint 22 in the Conductor Changelog.

Development Of New and Useful Tools

*Click the name of each donut below for more details and a "how to" guide for each specific tool.*

Extension Activator (Updated!)

https://extension-activator.ps.ringcentral.com/
This tool lets you activate and/or update multiple limited extensions or user extensions on an account with a simple excel file.

Phone Number and Extension Reassigner + Phone Number Naming -(Updated!)

https://phone-and-extension-assigner.ps.ringcentral.com/
This tool allows you to assign phone numbers to extensions and add names to numbers in bulk- pre and post port.

Caller ID & Audit Tool - (Updated!)

https://caller-id.ps.ringcentral.com
Audit and view all the Caller ID's on an account + download an Excel file so you can filter, sort, and manipulate the records. In addition, you can still set the Caller ID as the direct number for all the extensions and devices on an account.

SIP Provisioning Info - Microsoft Teams Formatting + Audio Codes (Updated!)

https://sip-provisioning.ps.ringcentral.com/sip-viewer
The SIP tool allows you to view manual provisioning information, including information about the device and the assigned extension.

It also allows Microsoft Teams formatting - selecting the MS Teams box provides the format needed to upload directly into the admin cloud pbx portal which is the portal that handles our MS Teams direct routing integration.

Advanced Rules - (Updated!)

http://advanced-rules.ps.ringcentral.com
The updated advance rule donut will allow the creation, edit, audit and delete of Advance rules, business hours rules and after hours rules. One of it's key new features is the ability to create unconditional forwarding rules very easily.

CCRNs

https://ccrns.ps.ringcentral.com/
Cloud Connect extensions made easy

ERL - Emergency Response Locations

https://erl.ps.ringcentral.com/
New Donut for adding ERL's to an account in Bulk.

Flakey Buttery Croissant Goodness

https://croissant.ps.ringcentral.com/
A tool made by DQ Griffin that allows you to import BRD and Lucid Charts to get the call flows in to an XML format for Ring Central Platform. You can also take an XML export from service web of the call flows and use this to get a CSV formated file for easy editing.

Conductor release 216, or Sprint 21, is the first sprint that can be truly called a 'sprint'. This is the first wave of faster deployment cycles with shorter but more critical items in each sprint. This shorter and focused delivery should help us make Conductor faster and much more useable.

Sprint 21 is really about increasing efficiencies and delivering a more reliable experience in the areas Conductor already excels at. Increasing bulk upload efficiency and usability, creating users with geo info set automatically, and improving the port package data formats are just a few areas that are now enhanced and modified.

See all the details about Sprint 21, and previous sprints, in the Conductor Changelog.

As usual, if you have any questions or comments please reach out to us via the Conductor Glip teams or ping someone on the PSi development team.

What's new:

• Deliver port package data within the standardized project port list spreadsheet.
• When submitting port packages, deliver the standardized port list spreadsheet in SFDC as a downloadable file.
• Changed the User Address modal to User Number Assignment. All address info removed and only affects the desired number the user shall receive once synced with Service Web.
• When syncing users, if you have no User Number Assignment, the user will default to unassigned number selections that match the country code of the site they are assigned to.
• Ignore Roles for Limited Extension users when bulk uploaded with Conductor.
• The Bulk uploader will accept all variations for boolean ("Y" or "N") required fields so it's easier to bulk upload data.. Examples are: Yes, No, True, False, T, F, Y, N etc...
• Removed all posts from the CUST (customer) Glip group. The only posts that will be seen are actions the customer performs or when a member makes a post in CUST Glip group.
• See all the details about Sprint 20 in the Conductor Changelog.

A quick glance at the status of all PSi Projects. (Airtable license required to view)

Internal Team Projects

Internal and custom application development projects.

Cloud Relay Projects

Cloud relay ONLY development projects.

Well. Someone brought up a good point.

TL;DR

If you're using the old faithful email hack to stop customers getting email, where you put an 'x' at the end of the customer email domain like john.celoria@oraclex.org, don't do that anymore. Instead, put ps.ringcentral.com at the end of the whole email, like john.celoria@oracle.org.ps.ringcentral.com

Long Version

The background

Long time ago. I mean long time ago. We brought up to the product team that not all customers want to have their users get activation emails when we set them up in RingCentral. Simple request. Product tried to implement this, and did in fact stop welcome emails, but that didn't stop other emails. Like here's how you log into the new RC Desktop app, or here's a great way to put in your forwarding setup blah blah.

So to stop customers from getting any emails at all, we instead started putting an 'x' on the end of those emails. Invalid address, didn't go anywhere, customers were happy, we didn't get yelled at, nice.

Eventually we made a cool Donut for activating users, etc. That worked really great, but the platform APIs that it uses required a valid top level domain (.com, .net, .org, etc). So, john.celoria@ringcentral.comX was no longer going to work. Quick solution was to just move the 'x' in front of the top level domain, making the address john.celoria@ringcentralX.com. We started doing that, and it worked great.

The problem

Wellllllll, someone recently pointed out that someone could actually own that web domain. Like, let's say our customer is Oracle. They're pretty popular, and somebody out there can go out on the internet and buy oraclex.com and then it's theirs. This actually happens a lot, because if Oracle ever decided that they wanted to buy that domain, and use it for some cool Oracle project, they would now have to buy it from the person that already owns it. Probably at a huge markup.

Here's a fun story of a guy who did this to Google. They let their ownership of the domain google.com lapse for just a few moments, and the guy bought it. They paid him to get it back. Cause ya know. Capitalism.

The security breach for us would be, if we send a few thousand welcome emails to @oraclex.com and the person that owns it starts paying attention, we could giving them access to setup the users on our customer accounts! Even make outbound phone calls using the caller ID for Oracle! That's super bad.

The solution

We're really hoping that one day we will never have to think about this non-sense again. Actively trying to find a way to never have to worry about this email stuff, and we can just magically stop sending emails, the way we've always dreamed.

In the meantime though, so that we keep our customers safe, if you need to use this, don't put an X before the domain anymore. Instead, keep the customer's whole email address, and add "ps.ringcentral.com" to the tail end of it. Then that whole thing gets removed, instead of just removing an 'x'.

So, if I'm John Celoria, a user from Oracle, who has an email with Oracle that is "john.celoria@oracle.com", that would now be "john.celoria@oracle.com.ps.ringcentral.com"

When the emails go out, they come all the way back to RingCentral and get safely ignored. Then later on, you change the email, send users welcome emails, the customer is happy, and no one has caused a security breach!

This works with any domain too. Say it was something like "john.celoria@bostoncollege.edu", you change that "john.celoria@bostoncollege.edu.ps.ringcentral.com" and we're all good to go!