Skip to main content

Schedule phone calls according to some criteria

Project description

Beta License: AGPL-3 OCA/crm Translate me on Weblate Try me on Runbot

Use this module to plan a phone calls schedule for your partners, assuming you have specified the ideal time to call them.

Table of contents

Configuration

To use this module, you need to specify your partners’ preferred phone call schedule:

  1. Go to any partner’s form > Phone Calls.

  2. Set the preferred phone calling schedule for the partner.

  3. Repeat above steps for all of your partners.

Usage

Now, to actually generate the phone call planning:

  1. Go to Sales > Phone Calls > Planner.

  2. Fill the fields under Call details. Those fields will be saved literally in the generated phone calls.

  3. Fill the fields under Criteria. Those fields are used to filter the partners and the preexisting calls. The UTM fields will also be saved literally in the generated phone calls.

  4. Fill the fields under Times. See note below.

  5. Fill the fields under Repetition. See note below.

  6. Press Generate planning.

  7. Wait a little bit (this is usually a long process).

  8. You will get to the list of planned phone calls. Start calling!

Note about Times section

The Start and End times behave in a special way:

  • Their date part is used to know the start and end dates for the planning.

  • Their time part is used to know the time at which we will plan calls each day under the date range.

The Call duration field indicates the time spacing you want to leave between one call and the next one.

So, for instance, if you select start on 2017-09-01 09:00:00, end on 2017-09-03 10:00:00 and duration of 1:00, it will try to generate these phone calls:

  • 2017-09-01 09:00:00

  • 2017-09-01 10:00:00

  • 2017-09-02 09:00:00

  • 2017-09-02 10:00:00

  • 2017-09-03 09:00:00

  • 2017-09-03 10:00:00

Note about Repetition section

If you choose not to repeat calls, the planner will try to schedule one single phone call for each criteria combination (Partner + Campaign + Source + Medium) under the specified conditions in the Times section (see note above).

If you choose instead to repeat calls after some amount of days (Days gap), the planner will:

  1. Try to find a partner that matches the criteria combination and has never been called; then schedule a call for him.

  2. If all matching partners have already been called, then search for matching partners that have not been called in the specified Days gap; then schedule a call for the one with least total scheduled calls.

  3. If there is still no match, then schedule nothing and continue.

Known issues / Roadmap

  • Incompatible with crm_phonecall_summary_predefined addon.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Tecnativa

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/crm project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo12_addon_crm_phonecall_planner-12.0.1.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo12_addon_crm_phonecall_planner-12.0.1.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 3fad83c8fe5762204e6f56eb223001c7cf3b1cda2554730d16516eee2a243dab
MD5 a3fbfae8b126b8fb071ba523e77bb59f
BLAKE2b-256 0c29d8cbd9903db2ef41e1f3a8c4b0f658c954fad9d4e64d1ec60cb18176478b

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page