Flow Configuration - Visibility in Customer Portal

Flow Configuration - Visibility in Customer Portal

In this article we will see how to configure the elements that will be visible in the Customer Portal in each substate of our sales flows.

Where can I find this option? → Settings Opportunity types and processes
Remember that this option will only be available if you have the permissions activated: Opportunity states Modify opportunity states

Previous concepts

The Customer Portal is the tool that allows us to have digital and automated interactions with our end customers, throughout the sales process. Through it, we can request additional information, share offers and contracts, inform the client about the progress and status of their opportunity, among other functions.
The Client Portal is an interface to which the client will have access and whose content will depend on our configuration. It is made up of screens (or "views"), which we will configure for each of our sales opportunity flows and substates, deciding at each moment which view we want the customer to see.

This article focuses on configuring these views by substate from the Settings → Opportunity Types and Processes page.

Additionally, we must also configure:

- The design and content of the client portal from SettingsClient Portal
- Actions from external sources from Settings → Actions from external sources. This setting allows your opportunity to automatically advance to the status configured in External Source Actions when the customer submits information or completes a step.

To configure the views of the Customer Portal, we must have previously created states and substates.

Customer Portal Visibility by Status - Step by Step

To define the visibility of the status of the opportunity from the Client Portal, we will follow the following steps.
  1. We access the “Settings” section in the left sidebar and enter “Opportunity Types and Processes”.
  2. We select a type of opportunity from those already created, and we enter one of the states. We will see that a menu is enabled on the right in which a tab appears that says “Customer Portal” and in there, “Status information”.
  3. In this section we will enter the name that we want to be visible to clients in their Portal, for this status. Also, optionally, we can include a brief description so that the client knows what this state consists of.
  4. Once configured to our liking, we click on “Edit status” at the top right so that the changes are saved.

Customer Portal Visibility by Substate - Step by Step

To define the content visible to our client through the Client Portal, we will configure its visibility substate by substate.
To do this, we will follow the following steps.
  1. We access the “Settings” section in the left sidebar and enter “Opportunity Types and processes”.
  2. We select a type of opportunity from those already created, and we enter one of the states, to be able to access one of the substates.
  3. We will see that a menu is enabled on the right in which a tab appears that says “Customer Portal”.
  4. We are going to configure the 4 sections that we have. Each of these sections is detailed below.
  5. Once these sections are configured, we click on "Edit status" at the top right to save our configuration.

1) Status information

  • Public name : We define the name that this substate will have for the end customer, in the Customer Portal.
  • Description : We add, optionally, a brief description that will help the client understand what is happening and what is expected of them at this stage of the process.
  • 2) Panel to display

    We choose one of the preconfigured views for the Customer Portal. These views make interaction with the customer easier. If no interaction is needed, it can be left unviewed so in this case, the client does not need to take any action, but is informed about the status of their project. The client will see which substate their project is in (with the public name that we define), and which substates have already been carried out.

    Below is a brief description of the purpose of each view:
    1. Documentation views: These views are used to allow the client to upload relevant information and/or documentation. There are several of these views, to be able to cover different stages in which we ask the client for information. The specific information will be completed using the dynamic fields that we activate (See next section on dynamic fields) .
      1. i nitial-documentation : This view allows the client to upload the necessary documentation to be able to continue with the process (Usually ID, Electric bill, etc.)
      2. offer-documentation : This view allows the client to upload the relevant documentation for the preparation of their offer.
      3. financing-documentation : This view allows the client to upload the relevant documentation for their financing.
      4. contracts-documentation : This view allows the client to upload the relevant documentation for the preparation of their contract.
      5. installation-documentation : This view allows the client to upload the relevant documentation for their installation.
    2. drawing : This view allows the customer to draw their own roof through the Customer Portal.
    3. offer : This view allows you to share the offers corresponding to your project with the client, and let them accept the one that suits them best. When accepting an offer from the client portal, using the "Accept" button, the opportunity will change its Sub-State, and will go to the sub-state defined in Settings → Actions from external sources → Client Portal → "Accept-Budget".
    4. installer-visit . This view informs the client of the details of the installer assigned to their project.
    5. contract Signing: This view allows the client to access their contracts, and upload them once signed (if we have contracted the "Digital Signature" service, this view would not be necessary)
    6. Completion Views: These views serve to maintain a point of contact with the customer at the end of the process.
      1. finalization-success: This view informs the client that their project is finalized. It includes a text, which we define in Settings → Customer Portal → "End of process module"
      2. finalization-failed : This view informs the client that their project is closed without being finalized, and if we configure it like this, it leaves the client the possibility of reactivating their project. A text appears in it, which we define in Settings → Customer Portal → "End of process module" . There you can also activate the button that the client can use to reactivate their project. Specifically, the opportunity will be moved to the substate defined in Settings → Actions from external sources → Customer Portal → "Show flow reactivation"

    3) Dynamic fields of opportunity

    For the documentation views, we have to integrate thedynamic fields that will be used to fill in said information. To add a dynamic field to the view, click on "Select opportunity field", and select the field to add. Once added, we can define this field to be:
    -"Not mandatory" or "required". In the case that it is "required", the client will not be able to move to the next substate without having completed the information for this field.
    - "Read-only" or not. If it is Read-only, the field will only show information to the client, without the possibility of being edited from the client portal. For example, a dynamic field type "File" through which we want to share a document in a specific substate with the client but we only want them to be able to download it and not be able to edit the field.
    We can make the same dynamic field appear in multiple views of the Customer Portal, without necessarily having the same functions. For example, the same dynamic field, such as the customer ID, can be "Required" in the initial-documentation stage, "Not required" in offer-documentation , and "Read-Only" in contracts-documentation.
    In order to configure the available dynamic fields, we must have previously created dynamic fields .

    4) Conditions

    We can add "Privacy Conditions" that the client must accept, from the Client Portal, in order to continue with their sales flow. Conditions are created from Settings Condition Management




      • Related Articles

      • What are opportunity types and what are they used for?

        In this article we will see an introduction to the types of opportunities and discover how to create them on the platform. Where can I find this option? → Settings → Opportunity Types and Processes Remember that this option will only be available if ...
      • Flow Configuration - Trade Simulator Visibility

        In this article we will see how to configure the elements that will be visible in the commercial simulator in each substate of our sales flows. Where can I find this option? → Settings → Types of opportunity and processes Remember that this option ...
      • Flow Settings - Automatic Actions

        In this article we will see how to configure automatic actions linked to sub-statuses of an opportunity type. Where can I find this option? → Settings → Opportunity Types and Processes Remember that this option will only be available if you have ...
      • Flow configuration - Visibility in installer app

        In this article we will see how to configure the elements that will be visible in the installers app in each substate of our sales flows. Where can I find this option? → Settings → Types of opportunities and processes Remember that this option will ...
      • Setting states and substates

        In this article we will see how to configure the statuses and sub-statuses of an opportunity type. Where can I find this option? → Settings → Opportunity Types and Processes Remember that this option will only be available if you have enabled the ...