Feature Requests

Add Account team to customers portal accounts so they know who to contact within PacketFabric.

Change Title of field for GCP hosted ordering. Currently says "Destination region". This is not correct verbiage. What is showing are OnRamps. These are two different things. Note: "OnRamps" is an accurate but generic industry term. Different providers use different terms to mean "OnRamps". Azure uses :"Peering Location". GCP appears to use "Colocation Facilities" ( https://cloud.google.com/network-connectivity/docs/interconnect/concepts/choosing-colocation-facilities ), which may not be the most descriptive term. I would probably stick with "OnRamps". Up to you though. But "Destination Region" definitely refers to something else.

Large customers need to be able to assign a PO number to an order and have that PO number come through on the invoice. This is currently achieved within the circuit description and some manual off-line work on the part of account management and also the customer.

Send notifications to the reseller when a reseller's customer makes a billing impacting change

Would like to know if we have Terraform available for provisioning if the customer wanted to set up that way?

In Portal and API, return peering location when customer validates the Service Key, and use peering location to display correct price. Currently only returns valid/invalid, however Azure also returns peering location. This is critical for accurate pricing PRIOR to the customer submitting the order.

Currently in the Marketplace a provider/customer that advertises on it shows as a rectangle with the Logo and description. This rectangle is a single clickable object that when clicked starts a provisioning workflow, there is no ability to click a url within the description. Providers are looking for the ability to add verbiage and links to where a customer can go to subscribe to the providers service. This could be a web url, a mail to url and/or phone number that's clickable. Instead of the single clickable object to kickoff of the provisioning workflow, only the logo and company name are clickable for provision workflow, or a "connect to" button and additional services button for those that are offering more than one service. There is also an issue with the company description, in the "admin" section it limits one to 500 characters, the issue is in the marketplace 500 characters can be too much depending on screen resolution of an end user. Since the rectangles aren't scrollable an end user with a low screen resolution can't get the rectangle big enough to read all the text.

It would be great to be able to set the MED, LocalPref, prepending on a prefix-by-prefix basis instead of for all prefixes recvd/sent to a peer.

When a provider receives an email indicating a request for a connection has been made by and end user, the details about the connection request don't provide enough information for a provider to understand the request. This becomes more evident when a provider offers multiple services, the request doesn't indicate what service the customer wants a connection to. Providers are looking for Customer name, customer contact, customer email, customer phone number, not sure if these can't be provided due to privacy reasons. For the connection they're looking for, speed of the VC request, A and Z end, connection to what service, a connection request ID that both the end user and provider can see. The connection request ID is critical for a provider to marry the customer to the connection request and their existing account or new account for the service. Currently this ID is visible to the provider but the customer is unable to see this ID, thus the two parties can't confirm the request. Providers would also like to see all this information in the request email in the connection request details within the portal. Currently all a provider sees is the request with no details and they can only accept or deny the request. Accepting the request doesn't provide anymore details just the provisioning workflow for the providers side of the VC.

We currently send our Marketplace partners (such as T-Mobile) an email with the details of a circuit request. We now need to likewise send them an email notification if/when the customer DELETEs that circuit.