-
Notifications
You must be signed in to change notification settings - Fork 9.4k
[ADD] VoIP: Support Agent Workflow #12933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. W 8000 e’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
120 changes: 120 additions & 0 deletions
120
content/applications/productivity/voip/support_calls.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,120 @@ | ||
======================= | ||
Support calls with VoIP | ||
======================= | ||
|
||
.. |VOIP| replace:: :abbr:`VoIP (Voice over Internet Protocol)` | ||
|
||
A useful tool for support teams, Odoo |VOIP| is used as a way to get in contact with customers that | ||
need some help. Using |VOIP| can help improve customer satisfaction, reduce support costs, and | ||
allows support agents to navigate an Odoo database while on a call. | ||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Instead of being tied to their desks, support agents can take calls from anywhere they have access | ||
to Odoo :doc:`VoIP <../voip>`. | ||
|
||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
.. important:: | ||
This feature requires at least one :doc:`call queue <axivox/call_queues>` to be configured. | ||
|
||
.. seealso:: | ||
`Odoo Tutorial: Working as a Support Agent | ||
<https://www.odoo.com/slides/slide/working-as-a-support-agent-odoo-voip-4617>`_ | ||
|
||
Log into a support queue | ||
======================== | ||
|
||
If :doc:`call queues <axivox/call_queues>` are set up, begin a support shift by logging into a call | ||
queue. | ||
|
||
Begin by clicking :icon:`oi-voip` :guilabel:`(VoIP)` in the top-right corner of the Odoo database. | ||
From there, click :icon:`fa-keyboard-o` :guilabel:`(keyboard)`, then dial the *agent connection* | ||
number and click :icon:`fa-phone` :guilabel:`(phone)`. | ||
|
||
Once the support agent calls their *agent connection code*, they'll hear a short message letting | ||
them know they are logged into the queue. From here, the agent receives support calls according to | ||
the administrator's :doc:`call queue strategy <axivox/call_queues>`. When a support agent receives a | ||
call, the Odoo |VOIP| widget appears in the bottom-right corner of their screen with the caller's | ||
phone number, as well as their name if the number is tied to a customer profile. | ||
|
||
.. note:: | ||
When support staff are added as :doc:`static agents <axivox/call_queues>` to a call queue, they | ||
do not need to log into the queue to receive calls from that queue. | ||
|
||
Call a customer from a support ticket | ||
===================================== | ||
|
||
As part of a support agent's daily tasks, they might be asked to call customers with open support | ||
tickets. With Odoo |VOIP|, the support agent can stay in the Odoo database throughout the entire | ||
workflow. | ||
|
||
From the database's home page, click the **Helpdesk** app, click into a helpdesk, and then open a | ||
ticket. If the ticket does not already have a call activity scheduled, click :guilabel:`Activities` | ||
in the ticket's chatter, then set the activity's :guilabel:`Activity Type` to :guilabel:`Call`, and | ||
then fill out the rest of the activity form, and finally click :guilabel:`Schedule`. | ||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
.. image:: support_calls/create-call-activity.png | ||
:alt: Scheduling a call activity for a support ticket. | ||
|
||
From here, the agent has three ways to make a call: | ||
|
||
- Hover over the :guilabel:`Phone` field in the ticket, then click :icon:`fa-phone` | ||
:guilabel:`Call`. | ||
- In the ticket's chatter, click the customer's phone number. | ||
- In the upper-right corner, click the :icon:`oi-voip` :guilabel:`(VoIP)` icon to open the |VOIP| | ||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
widget. From the :guilabel:`Next Activities` tab, select the call, and finally click the | ||
:icon:`fa-phone` :guilabel:`(phone)` icon near the bottom of the widget. | ||
|
||
Work during a call | ||
------------------ | ||
|
||
Once the call with the customer begins, the support agent can still move about the Odoo database. | ||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
Also, there are shortcut icons in the |VOIP| widget that the support agent can use to access common | ||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
actions, like sending an email to the customer, or pulling up their profile. Learn more about | ||
:doc:`the documents a support agnet can access <voip_widget>` during a call. | ||
|
||
The support agent can also take some actions during the call: | ||
|
||
- :icon:`fa-arrows-h` :guilabel:`(transfer)`: Transfer a call to another team member. | ||
- :icon:`fa-microphone` :guilabel:`(microphone)`: The support agent can mute themselves during a | ||
call. | ||
- :icon:`fa-pause` :guilabel:`(pause)`: Place the caller on hold. | ||
|
||
Handle call follow-ups | ||
---------------------- | ||
|
||
The |VOIP| widget can handle some common follow-up tasks, but support agents can still navigate Odoo | ||
for tasks not available in the widget. | ||
|
||
Here are some of the common follow-up tasks that can be managed from the |VOIP| widget: | ||
|
||
- Send a follow-up email sharing troubleshooting steps with the customer using the | ||
:icon:`fa-envelope` :guilabel:`(envelope)` icon. | ||
- Update the customer's mailing address by clicking on the :icon:`fa-user` :guilabel:`(user)` icon, | ||
which opens their profile. | ||
- Schedule a second call with the customer by clicking the :icon:`fa-clock-o` :guilabel:`(clock)` | ||
icon, setting the :guilabel:`Activity Type` field to :guilabel:`Call`, and then filling out the | ||
rest of the form. | ||
|
||
End the support call | ||
-------------------- | ||
|
||
When it is time to end the call, the support agent clicks the red :icon:`fa-phone` | ||
:guilabel:`(phone)` icon in the lower-right corner of the |VOIP| widget. When they do, the call is | ||
logged in the ticket's chatter. | ||
|
||
If they have not done so already, the support agent then marks the phone call activity as done. To | ||
do so, navigate to the ticket's chatter and find the :guilabel:`Planned Activities` section, then | ||
click :icon:`fa-check` :guilabel:`Mark Done` on the planned call to remove it from the | ||
:guilabel:`Next Activities` tab in the |VOIP| widget. | ||
|
||
Log out of a support queue | ||
========================== | ||
|
||
Once the agent's shift ends, or if they are taking a break, they can log out of the support call | ||
queue. | ||
|
||
Begin by clicking :icon:`oi-voip` :guilabel:`(VoIP)` in the top-right corner of the Odoo database. | ||
From there, click :icon:`fa-keyboard-o` :guilabel:`(keyboard)`, then dial the *agent disconnection* | ||
number and click :icon:`fa-phone` :guilabel:`phone`. | ||
|
||
Once the support agent calls their *agent disconnection code*, they'll hear a short message letting | ||
jero-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
them know they are logged out of the queue. From here, the agent will no longer receive support | ||
calls until they log back in. |
Binary file added
BIN
+29.2 KB
content/applications/productivity/voip/support_calls/create-call-activity.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.