Marketplace Request Details
complete
C
Chris
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.
Peter Farmer
complete