odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/sales/crm/optimize/utilize_activities.md

@@ -0,0 +1,251 @@
+---
+title: "Utilize activities for sales teams"
+source_url: "https://docs.odoo.sbggai.top/applications/sales/crm/optimize/utilize_activities.html"
+---
+
+==================================
+# Utilize activities for sales teams
+
+*Activities* are follow-up tasks tied to a record in an *Odoo* database. Activities can be scheduled
+on any page of the database that contains a chatter thread, Kanban view, list view, or activities
+view of an application.
+
+.. figure:: utilize_activities/activities-view.png
+   :align: center
+   :alt: The summary view of activities for leads and opportunities in an Odoo database.
+
+   Planned Activities for Leads and Opportunities.
+
+# Activity types
+
+A set of preconfigured activity types is available in the *CRM* app. To view the list of available
+activity types, navigate to the :menuselection:`CRM app --> Configuration --> Activity Types`.
+
+> **note**:
+>    Additional activity types are available within the database, and can be utilized through
+   different applications. To access the complete list of activity types, go to the
+   :menuselection:`Settings app`, then scroll to the :guilabel:`Discuss` section, and click
+   :guilabel:`Activity Types`.
+
+The preconfigured activity types for the *CRM* app are as follows:
+
+ - :guilabel:`Email`: adds a reminder to the chatter that prompts the salesperson to send an email.
+ - :guilabel:`Call`: opens a calendar link where the salesperson can schedule time to call the
+   contact.
+ - :guilabel:`Meeting`: opens a calendar link where the salesperson can schedule time to have a
+   meeting with the contact.
+ - :guilabel:`To Do`: adds a general reminder task to the chatter.
+ - :guilabel:`Upload Document`: adds a link on the activity where an external document can be
+   uploaded. Note that the *Documents* app is **not** required to utilize this activity type.
+
+> **note**:
+>    If other applications are installed, such as *Sales* or *Accounting*, other activity types are
+   made available in the *CRM* app.
+
+.. _crm/create-new-activity-type:
+
+## Create a new activity type
+
+To create a new activity type, click :guilabel:`New` at the top-left of the page to open a blank
+form.
+
+At the top of the form, start by choosing a :guilabel:`Name` for the new activity type.
+
+### Activity settings
+
+Action
+******
+
+The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors
+after an activity is scheduled.
+
+- If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the
+  planned activity in the chatter.
+- If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open
+  their calendar to schedule a time for this activity.
+- If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the
+  chatter that opens a signature request pop-up window.
+
+.. image:: utilize_activities/action-field.png
+   :align: center
+   :alt: The Activity settings on a new activity type with emphasis on the Action field.
+
+> **note**:
+>    The actions available to select on an activity type vary, depending on the applications currently
+   installed in the database.
+
+Default user
+************
+
+To automatically assign this activity to a specific user when this activity type is scheduled,
+choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the
+activity is assigned to the user who creates the activity.
+
+Default summary
+***************
+
+To include notes whenever this activity type is created, enter them into the :guilabel:`Default
+Summary` field.
+
+> **note**:
+>    The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are
+   included when an activity is created. However, they can be altered before the activity is
+   scheduled or saved.
+
+### Next activity
+
+To automatically suggest, or trigger, a new activity after an activity has been marked complete, the
+:guilabel:`Chaining Type` must be set.
+
+Suggest next activity
+*********************
+
+In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the
+field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu
+to select any activities to recommend as follow-up tasks to this activity type.
+
+.. image:: utilize_activities/next-activity.png
+   :align: center
+   :alt: The Next Activity section on a new activity type form.
+
+In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so,
+configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then,
+decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity
+deadline`.
+
+This :guilabel:`Schedule` field information can be altered before the activity is scheduled.
+
+When all configurations are complete, click :guilabel:`Save`.
+
+> **note**:
+>    If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and
+   has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations
+   for activities as next steps.
+
+   .. image:: utilize_activities/suggest-next-activity.png
+      :align: center
+      :alt: A schedule activity pop-up with emphasis on the recommended activities.
+
+Trigger next activity
+*********************
+
+Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the
+next activity once the previous one is completed.
+
+If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field
+beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select
+the activity that should be launched once this activity is completed.
+
+In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so,
+configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then,
+decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity
+deadline`.
+
+This :guilabel:`Schedule` field information can be altered before the activity is scheduled.
+
+When all configurations are complete, click :guilabel:`Save`.
+
+> **note**:
+>    When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`,
+   marking the activity as *Done* immediately launches the next activity listed in the
+   :guilabel:`Trigger` field.
+
+# Activity tracking
+
+To keep the pipeline up to date with the most accurate view of the status of activities, as soon as
+a lead is interacted with, the associated activity should be marked as *Done*. This ensures the next
+activity can be scheduled as needed. It also prevents the pipeline from becoming cluttered with
+past due activities.
+
+The pipeline is most effective when it is kept up-to-date and accurate to the interactions it is
+tracking.
+
+.. _crm/activity-plans:
+
+# Activity plans
+
+*Activity plans* are preconfigured sequences of activities. When an activity plan is launched, every
+activity in the sequence is scheduled automatically.
+
+To create a new plan, navigate to :menuselection:`CRM app --> Configuration --> Activity Plan`.
+Click :guilabel:`New` at the top-left of the page to open a blank :guilabel:`Lead Plans` form.
+
+Enter a name for the new plan in the :guilabel:`Plan Name` field. On the :guilabel:`Activities to
+Create` tab, click :guilabel:`Add a line` to add a new activity.
+
+Select an :guilabel:`Activity Type` from the drop-down menu. Click :guilabel:`Search More` to see a
+complete list of available activity types, or to create a :ref:`new one
+<crm/create-new-activity-type>`.
+
+Next, in the :guilabel:`Summary` field, enter any details to describe the specifics of the activity,
+including instructions for the salesperson or information due upon the completion of the activity.
+The contents of this field are included with the scheduled activity, and can be edited later.
+
+In the :guilabel:`Assignment` field, select one of the following options:
+
+ - :guilabel:`Ask at launch`: activities are assigned to a user when the plan is scheduled.
+ - :guilabel:`Default user`: activities are always assigned to a specific user.
+
+If :guilabel:`Default user` is selected in the :guilabel:`Assignment` field, choose a user in the
+:guilabel:`Assigned to` field.
+
+> **tip**:
+>    Activity plans can feature activities that are assigned to default users and users assigned at
+   the plan launch.
+
+  .. image:: utilize_activities/create-activity-plan.png
+     :align: center
+     :alt: A Lead Plan form with scheduled activities.
+
+Next, configure the timeline for the activity. Activities can be scheduled to occur either before
+the plan date or after. Use the :guilabel:`Interval` and :guilabel:`Units` fields to set the
+deadline for this activity. Lastly, in the :guilabel:`Trigger` field, select whether the activity
+should occur before or after the plan date.
+
+.. example::
+   An activity plan is created to handle high priority leads. Specifically, these leads should be
+   contacted quickly, with a meeting scheduled within two days of the initial contact. The plan is
+   configured with the following activities:
+
+   - Email two days **before** plan date
+   - Meeting zero days **before** plan date
+   - Make quote three days **after** plan date
+   - Upload document three days **after** plan date
+   - Follow-up five days **after** plan date
+
+   This sets the *plan date* as the meeting deadline, which is the objective of the plan. Before
+   that date, there is lead time to contact the customer and prepare for the meeting. After that
+   date, the salesperson has time to create a quote, upload the document, and follow-up.
+
+Repeat these steps for each activity included in the plan.
+
+## Launch an activity plan
+
+To launch an activity plan on a *CRM* opportunity, navigate to :menuselection:`CRM app` and click on
+the Kanban card of an opportunity to open it.
+
+At the top-right of the chatter, click :guilabel:`Activities` to open the :guilabel:`Schedule
+Activity` pop-up window.
+
+In the :guilabel:`Plan` field, select the desired activity plan to launch. This generates a
+:guilabel:`Plan summary`, listing out the activities included in the plan. Select a :guilabel:`Plan
+Date` using the calendar popover. This updates the :guilabel:`Plan summary` with deadlines based on
+the intervals configured on the :ref:`activity plan <crm/activity-plans>`.
+
+Select a user in the :guilabel:`Assigned To` field. This user is assigned to any of the activities
+on the plan were configured with :guilabel:`Ask at launch` in the :guilabel:`Assignment` field.
+
+.. image:: utilize_activities/schedule-activity-plan.png
+   :align: center
+   :alt: The schedule activity pop-up window with an Activity plan selected.
+
+Click :guilabel:`Schedule`.
+
+The details of the plan are added to the chatter, in addition to each of the activities.
+
+.. image:: utilize_activities/activity-plan-chatter.png
+   :align: center
+   :alt: The chatter thread of a CRM opportunity with a launched activity plan.
+
+.. seealso::
+ - :doc:`Activities </applications/essentials/activities>`

package/payload/skills/odoo18-docs/references/docs/applications/sales/crm/optimize.md

@@ -0,0 +1,16 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/sales/crm/optimize.html"
+---
+
+:nosearch:
+# 
+# Optimize your Day-to-Day work
+
+.. toctree::
+   :titlesonly:
+
+   optimize/partner_autocomplete
+   optimize/gamification
+   optimize/utilize_activities
+   optimize/lead_enrichment

package/payload/skills/odoo18-docs/references/docs/applications/sales/crm/performance/expected_revenue_report.md

@@ -0,0 +1,210 @@
+---
+title: "Expected revenue report"
+source_url: "https://docs.odoo.sbggai.top/applications/sales/crm/performance/expected_revenue_report.html"
+---
+
+=======================
+# Expected revenue report
+
+*Expected revenue* is the total cash value of leads that are expected to close by a certain date,
+usually the end of the current month.
+
+An *expected revenue report* compiles all active leads in a sales pipeline that have a set expected
+closing date, and compares how sales teams are performing in a given time frame.
+
+.. image:: expected_revenue_report/expected-revenue-closing.png
+   :align: center
+   :alt: Close up of the expected closing date on a lead in the CRM app.
+
+By pulling a monthly expected revenue report, sales managers can see which team members are reaching
+their goals, and who may need additional assistance to close valuable deals.
+
+# Create an expected revenue report
+
+To create an expected revenue report, first navigate to :menuselection:`CRM app --> Reporting -->
+Pipeline`. This opens the :guilabel:`Pipeline Analysis` dashboard.
+
+> **important**:
+>    The *Pipeline Analysis* dashboard includes several filters in the search bar by default. Remove
+   these before adding any additional custom filters.
+
+On the top-left of the report, click :guilabel:`Measures`, then select :guilabel:`Expected Revenue`
+from the drop-down menu.
+
+At the top of the page, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the
+:guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`,
+:guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click
+:guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window.
+
+.. _expected_revenue_report/custom-filters:
+
+## Add custom filters
+
+In order to generate an expected revenue report, filters need to be created for the following
+conditions:
+
+ - :ref:`Expected closing date <expected_revenue_report/closing-date>`: limits results to only
+   include leads expected to close within a specific time frame.
+ - :ref:`Exclude unassigned leads <expected_revenue_report/unassigned-leads>`: excludes leads
+   without an assigned salesperson.
+ - :ref:`Specific sales teams <expected_revenue_report/sales-team>`: limits results to only include
+   leads assigned to one or more sales teams. This filter is optional and should not be included if
+   the report is intended for the entire company.
+
+.. _expected_revenue_report/closing-date:
+
+### Add filter for expected closing date
+
+On the :guilabel:`Add Custom Filter` pop-up window, click into the first field of the new rule.
+Type `Expected Closing` into the :guilabel:`Search...` bar, or scroll to select it from the list.
+Click in the second field and select :guilabel:`is set`. This limits the results to only include
+leads where an estimated closing date is listed.
+
+Next, click the :guilabel:`➕ (plus)` icon to the right of the rule to duplicate it.
+
+> **tip**:
+>    Using the :guilabel:`➕ (plus)` icon makes it easy to add multiple rules based on the same
+   filter.
+
+In the second field of the new rule, select :guilabel:`is between` from the drop-down menu. This
+creates a set time frame during which the expected closing date must occur for leads to be included
+in the results.
+
+Click in each date field, one at a time, and use the calendar popover window to add both a start and
+end date to the rule. This is usually the beginning and ending of the current month, or fiscal
+quarter.
+
+.. _expected_revenue_report/unassigned-leads:
+
+### Exclude unassigned leads
+
+After filtering for the expected closing date, add a :guilabel:`New Rule`. Then, click into the new
+rule's first field, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll through the
+list to select it. Click in the rule's second field and select :guilabel:`is set` from the drop-down
+menu. This excludes any results without an assigned salesperson.
+
+.. _expected_revenue_report/sales-team:
+
+### Add a filter for sales teams
+
+> **note**:
+>    This filter is optional. To view results for the entire company, do **not** add this filter, and
+   continue to :ref:`View results <expected_revenue_report/view-results>`.
+
+To limit the results of the report to one or more sales teams, click :guilabel:`New Rule`. Next,
+click the first field for the new rule, and type `Sales Team` in the :guilabel:`Search...` bar, or
+scroll to search through the list to locate it.
+
+In the rule's second field, select :guilabel:`is in` from the drop-down menu. Selecting this
+operator limits results to the sales teams indicated in the next field.
+
+Lastly, click into the third field, and either: make a selection from the complete list revealed in
+the popover menu, or type the first few characters of the specific sales team's title to quickly
+find and select it as a parameter.
+
+> **tip**:
+>    Multiple teams can be added to the `Sales Team` rule, where each parameter is treated with an
+   "or" (e.g. "any") operator in the search logic.
+
+.. image:: expected_revenue_report/custom-filters.png
+   :align: center
+   :alt: Add Custom Filters pop-up window with custom filters configured for expected revenue
+         report.
+
+.. _expected_revenue_report/view-results:
+
+# View results
+
+At the top of the :guilabel:`Add Custom Filter` form, there is an option to match :guilabel:`any` or
+:guilabel:`all` of the rules. In order to properly run the report, only records that match **all**
+of the following filters should be included. Before adding the filters, make sure :guilabel:`all` is
+selected in this field.
+
+.. image:: expected_revenue_report/match-all-filters.png
+   :align: center
+   :alt: Emphasis on the match all filters option on the Add Custom Filter pop-up window.
+
+At the bottom of the :guilabel:`Add Custom Filter` form, click :guilabel:`Add`.
+
+## View options
+
+The expected revenue report benefits from utilizing multiple views. The default graph view can be
+used to identify which salespeople are expected to bring in the most revenue, while the list view
+and pivot view provide more detail on specific deals.
+
+.. tabs::
+
+   .. tab:: Graph view
+
+      The *graph view* is used to visualize data, and is beneficial in identifying patterns and
+      trends.
+
+      *Bar charts* are used to show the distribution of data across several categories or among
+      several salespeople.
+
+      *Line charts* are useful to show changing trends over a period of time.
+
+      *Pie charts* are useful to show the distribution, or comparison, of data among a small number
+      of categories or salespeople, specifically how they form the meaningful part of a whole
+      picture.
+
+      The default view for the expected revenue report is the bar chart, stacked. To change to a
+      different graph view, click one of the icons at the top-left of the report. While both the
+      line chart and bar chart are available in stacked view, the pie chart is not.
+
+      .. figure:: expected_revenue_report/graph-view-icons.png
+         :align: center
+         :alt: Close up view of the graph icons on the Pipeline analysis report in the CRM app.
+
+         Graph view icons in order: bar chart, line chart, pie chart, stacked.
+
+   .. tab:: List view
+
+      The *list view* provides a list of all leads that are expected to close by the designated
+      date. Clicking on a lead in list view opens the record for detailed analysis, but many
+      insights can be gleaned from the basic view.
+
+      To switch to the list view, click the :guilabel:`≣ (list)` icon at the top-right of the
+      report.
+
+      .. image:: expected_revenue_report/list-icon.png
+         :align: center
+         :alt: Close up of the list view icon in the CRM app.
+
+      To add additional metrics to the report, click the *additional options menu* indicated by the
+      :guilabel:`toggle` icon at the top-right of the list.
+
+      .. figure:: expected_revenue_report/toggle-icon.png
+         :align: center
+         :alt: Close up of the toggle icon in the CRM app.
+
+         Clicking the toggle icon in *list view* opens the *additional options menu*.
+
+      Select any additional metrics from the drop-down menu to add them to the list view. Some
+      options that may be useful are :guilabel:`Expected Closing` and :guilabel:`Probability`.
+
+   .. tab:: Pivot view
+
+      The *pivot view* arranges all leads that are expected to close by the designated date into a
+      dynamic table.
+
+      To switch to the pivot view, click the :guilabel:`Pivot` icon at the top-right of the report.
+
+      .. image:: expected_revenue_report/pivot-view-icon.png
+         :align: center
+         :alt: Close up of the pivot view icon in the CRM app.
+
+      When the pivot view is selected for this report, the X-axis lists the stages in
+      the pipeline, while the Y-axis defaults to group the results by their creation date. To switch
+      these groupings, click the flip access icon (:guilabel:`⇄`) at the top of the report.
+
+      To add additional measures to the report, click the :guilabel:`Measures` button at the
+      top-left of the report. Select any additional metrics from the drop-down menu.
+
+      To add a group to a row or column to the pivot view, click the :guilabel:`➕ (plus sign)` next
+      to :guilabel:`Total`, and then select one of the groups. To remove one, click the
+      :guilabel:`➖ (minus sign)` and de-select the appropriate option.
+
+      Click :guilabel:`Insert in Spreadsheet` to add the pivot view into an editable spreadsheet
+      format within the *Dashboards* app. If the Odoo *Documents* app is installed, the report can
+      be inserted into a blank or existing spreadsheet, and exported.

package/payload/skills/odoo18-docs/references/docs/applications/sales/crm/performance/forecast_report.md

@@ -0,0 +1,108 @@
+---
+title: "Forecast report"
+source_url: "https://docs.odoo.sbggai.top/applications/sales/crm/performance/forecast_report.html"
+---
+
+===============
+# Forecast report
+
+.. |caret| replace:: :icon:`fa-caret-down` :guilabel:`(down)` icon
+.. |pivot| replace:: :icon:`oi-view-pivot` :guilabel:`(pivot)` icon
+.. |list| replace:: :icon:`oi-view-list` :guilabel:`(list)` icon
+
+The *Forecast* report in the *CRM* app allows users to view upcoming opportunities and build a
+forecast of potential sales. Opportunities are grouped by the month of their expected closing date,
+and can be dragged-and-dropped to adjust the deadline.
+
+To access the *Forecast* report, navigate to :menuselection:`CRM app --> Reporting --> Forecast`.
+
+# Navigate the forecast report
+
+The default :guilabel:`Forecast` report includes opportunities assigned to the current user's
+pipeline, and are expected to close within four months. It also shows opportunities without an
+assigned expected closing date. The opportunities are grouped by month in a :icon:`oi-view-kanban`
+:guilabel:`(Kanban)` view.
+
+.. image:: forecast_report/sample-report.png
+   :align: center
+   :alt: A sample version of the Forecast report in the CRM app.
+
+## Expected closing date
+
+Opportunities are grouped by the date assigned in the *Expected Closing* field on an opportunity
+form. To change this date directly from the :guilabel:`Forecast` page, select the Kanban card for
+the desired opportunity, then click and drag the card to the desired column.
+
+> **note**:
+>    The default time frame for the forecast is *month*. This can be changed by clicking the |caret|
+   next to the :guilabel:`Search...` bar at the top of the report. Under the :guilabel:`Group By`
+   heading in the resulting drop-down menu, click :guilabel:`Expected Closing` to expand the list of
+   available options, and select a desired amount of time from the list.
+
+After an opportunity is added to a new month, the *Expected Closing* field on the opportunity form
+is updated to the *last* date of the new month.
+
+> **tip**:
+>    The *Expected Closing* field can also be manually updated on the opportunity card. To do that,
+   click on the Kanban card for an opportunity on the :guilabel:`Forecast` page to open the
+   opportunity's detail form. Click in the :guilabel:`Expected Closing` field, and use the calendar
+   popover to select a new closing date.
+
+## Prorated revenue
+
+At the top of the column for each month on the :guilabel:`Forecast` reporting page, to the right of
+the progress bar, is a sum of the prorated revenue for that time frame.
+
+The prorated revenue is calculated using the formula below:
+
+.. math::
+
+   \text{Expected Revenue} \times \text{Probability} = \text{Prorated Revenue}
+
+As opportunities are moved from one column to another, the column's revenue is automatically updated
+to reflect the change.
+
+.. example::
+   A forecast report for June includes two opportunities:
+
+   The first opportunity, `Global Solutions`, has an expected revenue of `$3,800`, and a probability
+   of `90%`. This results in a prorated revenue of `$3,420`.
+
+   The second opportunity, `Quote for 600 Chairs`, has an expected revenue of `$22,500`, and a
+   probability of `20%`. This results in a prorated revenue of `$4,500`.
+
+   The combined prorated revenue of the opportunities is `$7,920`, which is listed at the top of the
+   column for the month.
+
+   .. image:: forecast_report/example-revenue.png
+      :align: center
+      :alt: An example of the prorated revenue for one month of the forecast report.
+
+.. seealso::
+   For more information on how probability is assigned to opportunities, see
+   :doc:`../track_leads/lead_scoring`
+
+# View results
+
+Click the :icon:`fa-area-chart` :guilabel:`(area chart)` icon to change to graph view. Then, click
+the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar
+chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie
+chart)`.
+
+.. image:: forecast_report/pie-chart-view.png
+   :align: center
+   :alt: A pie chart view of the Forecast report.
+
+Click the |pivot| to change to the pivot view, or the |list| to change to the list view.
+
+> **tip**:
+>    The :ref:`pivot view <reporting/using-pivot>` can be used to view and analyze data in a more
+   in-depth manner. Multiple measures can be selected, and data can be viewed by month, and by
+   opportunity stage.
+
+   .. image:: forecast_report/pivot-view.png
+      :align: center
+      :alt: A sample of the forecast report in the pivot view.
+
+.. seealso::
+   To save this report as a *favorite*, see :ref:`search/favorites`.